${user.secondaryemail} not resolving in API call

[AS5278]

Hi All,

I have passed the users seondary email in the request body for a POST API call. I can see in the logs that ${user.secondaryemail} is not getting resolved. Everything else is getting resolved.

Request JSON:

"{\"FirstName\": \"${user.firstname}\",\"LastName\": \"${user.lastname}\",\"BusinessUnit\": \"United States BU\",\"LegalEntity\":\"XXXXX Corporation\", \"PersonType\": \"EMP\", \"ResourceEmail\": \"${user.secondaryemail}\", \"ResourceEndDate\": \"4712-12-31\", \"ResourceParentOrganizationName\": \"XXXX\", \"ResourceOrganizationName\": \"XXXX\", \"ResourceOrgRoleCode\": \"SERVICE_ADMINISTRATOR\"}"

In Logs:

Calling Webservice Url - https://api.xxxx.com/rs/v1/fusion/users/resourceUsers with httpParams - [FirstName:Andrew, LastName:Kane, BusinessUnit:United States BU, LegalEntity:XXXX Corporation, PersonType:EMP, ResourceEmail:${user.secondaryemail}, ResourceEndDate:4712-12-31, ResourceParentOrganizationName:XXXX Organization, ResourceOrganizationName:XXXX Organization, ResourceOrgRoleCode:SERVICE_ADMINISTRATOR]

As we can see that everything except user.secondaryemail is getting resolved. An I doing something wrong?.

Should it be ${user.secondaryEmail} and not ${user.secondaryemail}  i.e 'E' should be in capital in Email?.

Please advice.

Thanks.

[sudeshjaiswal · Accepted solution]

Hello @AS5278 ,

Please use 

"${user.secondaryEmail}",

Thanks.

[Vedanth-BK · Accepted solution]

Hi @AS5278 
Check out the REST developer's handbook for binding variables

[NM · Accepted solution]

@AS5278 try secondaryEmail