HTTP Response Codes

Code	Message	Notes
200	OK	Request successfully processed
400	Bad Request	Improperly formatted request, review request and try again
500	Internal Server Error	Unexpected error while processing request, try again later
503	Service Unavailable	Cannot reach service, try again later

Here's an example of retries and responses after receiving a 4xx or 5xx HTTP response with resolved tokens.

• First error: client retries after five seconds
• Second error: client retries after 30 seconds
• Third error: client retries after 60 seconds
• Fourth error: client retries after 120 seconds.

The client resets after receiving a successful response.

Tokenized sending can return attributes with resolved email addresses or mobile phone numbers. The process overwrites existing profile attributes with the same name as the resolved attribute with the resolved value at send time. You can overwrite null or empty profile attributes. For example, you could reference a profile attribute called SecureValue via AMPscript in the message. If the tokenized response contains a valid SecureValue value at send time, the message includes that value when sent. The value is not written into the database.