FAQ
Refer to the following Frequently Asked Questions to get clarity on the Network Loyalty APIs.
Yes.
Standard error codes can be located under the Common Error Codes section in the American Express Developers documentation.
No. The Sandbox environment does not support custom configuration. The environment is a default, embedded configuration located in an API’s specification document. It is designed to allow you to sample our products before moving into a formal testing environment which provides a limited, but meaningful, data set which anyone can use. For more details on the Sandbox:
- Go to My Keys.
- On the right side of the screen under Documentation, click Specifications.
- Click the Sandbox link in the upper left navigation section of the page.
NOTE: The Sandbox environment will allow you to perform a full E2E testing in our APIs.
It is not accessible until both Internet connectivity is established, and encryption algorithm is in place with both parties. Before then, R42 provides a sandbox which allows you to send dummy data and see what the response may look like, to check your development.
R42 APIs are published through the API Gateway. The API Gateway publishes the API endpoints with Mutual Transport Layer Security (MTLS) and Hash-based Message Authentication Code (HMAC) Authorization.
To begin the onboarding process, the Secure Sockets Layer (SSL) public key would be used for MTLS authentication. The Key, Secret, and the KeyName that you’ll need for the HMAC token generation will be provided. The KeyName is used for encryption.
AESGCM encryption needs to be used to encrypt the entire request body. The response must also be encrypted, using the same AESGCM algorithm. A path is provided to obtain a key that is used before the HMAC token is generated for the API Gateway.
The certifications used for MTLS authentication should be SSL public certificates.