| Error Payload | Resolution |
|---|---|
| { "code": "gateway.access.failure", "message": "Preconditions not met. The security conditions for gateway access were not met", "trackingId": " ", "transient": false, "errors": [] } |
Your IP address may be invalid - please check that you are coming from an IP whitelisted by SEI. If not, please reach out to SEI. |
| { "code": "gateway.access.failure", "message": "Preconditions not met. The security conditions for gateway access were not met", "trackingId": " ", "transient": false, "errors": [ { "reason": "Authorization Failed." } ] } |
The username used to obtain an OAuth Token and the CN on the client certificate must match. Please ensure you are making the API call with the expected values. |
| { "code": "gateway.access.failure", "message": "Preconditions not met. The security conditions for gateway access were not met", "trackingId": " ", "transient": false, "errors": [ { "reason": "The incoming traffic pattern is invalid." } ] } |
For Client/Server applications, the MTLS API host must be used. This is essential in order for the client server making API calls to establish a successful Two-Way SSL communication with SEI. Please use the MTLS host defined in the documentation. |
| Error Payload | Resolution |
|---|---|
|
{ |
Please first call for a new OAuth token and then retry making the respective API call. |
| { "code": "gateway.authentication.failure", "message": "Invalid ApiKey for given resource", "trackingId": null, "transient": false, "errors": [] } |
You may receive this error if your application does not have access to the API or the API Environment. Please check that your application was approved and that you have access to the API product by navigating to "My Apps" in the SEI Developer Portal. |
| { "code": "gateway.authentication.failure", "message": "Invalid ApiKey", "trackingId": null, "transient": false, "errors": [] } |
You may receive this error if you did not provide an API Key or provided an incorrect API Key. Please provide the correct key which can be obtained from the SEI Developer Portal in "MyApps". |
| { "code": "gateway.authentication.failure", "message": "Client credentials are invalid", "trackingId": " ", "transient": false, "errors": [] } |
You may receive this error if you provided an incorrect API Secret. Please provide the correct key which can be obtained from the SEI Developer Portal in "MyApps". |
| { "code": "gateway.authentication.failure", "message": "User authentication failed. Please submit with correct credentials", "trackingId": " ", "transient": false, "errors": [] } |
Ensure you are using the username and password provided to you through email. If you confirm that and are still not successful, please reach out to SEI as the password may have become locked. |
| Error Payload | Resolution |
|---|---|
| { "code": "gateway.authentication.failure", "message": "Unsupported Grant Type", "trackingId": null, "transient": false, "errors": [] } |
If your type of application is Client/Server, please include the grant_type as client_credentials. Refer to the OAuth token documentation for more information. |
| { "code": "gateway.authentication.failure", "message": "Missing Authorization Header", "trackingId": null, "transient": false, "errors": [] } |
The AppKey and AppSecret need to be encoded into a Base 64 format and provided as an "Authorization" header during the OAuth API call. |
| Error Payload | Resolution |
|---|---|
|
{ *Example. Your specific URL may differ. |
Please verify that you are using the correct host URL by referring to the SEI Developer Portal documentation. |
Please click HERE to obtain contact information for any type of support.