3 posts / 0 new
Last post
harleysunderlin5618
Sandbox Tokenize Credit Cards POST Method not returning correctly formatted json data for Invalid Api Key

Results copied from the Docs & Sandbox Tokenize Credit Cards POST Method. All POST methods that return a "Invalid Api Key" error message seem to have the same issue.

HTTP/1.1 401 Unauthorized

Connection: keep-alive
Content-Length: 34
Content-Type: application/json
Date: Wed, 14 Oct 2015 15:26:10 GMT
Server: Apigee Router

"401", "message":"Invalid Api Key"


harleysunderlin5618
Re: Sandbox Tokenize Credit Cards POST Method not returning...

Other strange json formatting listed below for HMAC validation error response and the second is error response is for a invalid merchant token. I noticed the merchant token seems to return correctly formatted. However the HMAC error returns formatted as a json object, but it does not seem formatted the same as the invalid merchant token json error. Are all error messages formatted the same?

'Incorrect ApiSecret error response or any issue that causes HMAC error
HTTP/1.1 403 Forbidden

Connection: keep-alive
Content-Length: 51
Content-Type: application/json
Date: Wed, 14 Oct 2015 16:12:02 GMT
Server: Apigee Router

{
"code": "403",
"message": "HMAC validation Failure"
}

------------------------------------------

'Incorrect Merchant Token error response
HTTP/1.1 401 Unauthorized

Connection: keep-alive
Content-Language: en-US
Content-Length: 106
Content-Type: application/json
correlation_id: 228.1444839243217
Date: Wed, 14 Oct 2015 16:14:03 GMT
OPTR_CXT:01000100008cda35fc-8e67-4e35-9552-17d83e173bb300000000-0000-0000-0000-000000000000-1 HTTP ;
Server: Apigee Router
X-Archived-Client-IP: 10.180.205.250
X-Backside-Transport: FAIL FAIL
X-Client-IP: 10.180.205.250
X-Powered-By: Servlet/3.0

{
"correlation_id": "228.1444839243217",
"Error": {
"messages": [
{
"code": "401",
"description": "Access denied"
}
]
}
}


rohitrajagopal3538
Re: Sandbox Tokenize Credit Cards POST Method not returning...

Hello Harley,

Thank you for reporting the issues to us. We will work on resolving it. All the errors should be formatted the same.

On a different note, I recommend that you use the HTTP GET method for tokenization rather than POST. We will be deprecating the POST method early next year. The HTTP GET method has all the same functionality.

Regards,

Rohit