A week ago I built an integration with this API and was testing with my home address in Brisbane with the validate and serviced-by endpoints with no problems. But today I was doing some testing as we are planning to deploy this integration on Monday and when I tested my home address with the validate endpoint I received some response information. But when checking the serviced-by endpoint with the data:
endpoint: https://api.myfastway.com.au/api/addresses/serviced-by
My auth token was obtained from: https://identity.fastway.org/connect/token
I received a response with an error saying that "we don't appear to have that postcode in our records"
{
"errors": [
{
"code": "PSC_PC_NF",
"path": null,
"message": "Sorry, we don't appear to have that postcode in our records (QLD 4066)",
"suggestedValues": null,
"logLevel": 0
}
],
"type": 2
}
I know for a fact this location should not fail like this. Any information on what I could be doing wrong or if there has been a change in the API that I am not aware of? I also tried with some new API keys as I read in another issue something that might work but still had the same error message.
Edit: I also tried to obtain an auth token from this end point https://identity.aramexconnect.com.au/connect/token with the scope code set as ac-api-au. I received a token and then tested the same serviced-by request and had the same issues. I even tested requesting with this url https://api.aramexconnect.com.au/api/addresses/serviced-by with my new auth token.
I re-read the docs and noticed the req body for this request locality changed from state to suburb. I adjusted these values and everything is working now.
A week ago I built an integration with this API and was testing with my home address in Brisbane with the
validate
andserviced-by
endpoints with no problems. But today I was doing some testing as we are planning to deploy this integration on Monday and when I tested my home address with thevalidate
endpoint I received some response information. But when checking theserviced-by
endpoint with the data: endpoint:https://api.myfastway.com.au/api/addresses/serviced-by
My auth token was obtained from:
https://identity.fastway.org/connect/token
I received a response with an error saying that "we don't appear to have that postcode in our records"I know for a fact this location should not fail like this. Any information on what I could be doing wrong or if there has been a change in the API that I am not aware of? I also tried with some new API keys as I read in another issue something that might work but still had the same error message.
Edit: I also tried to obtain an auth token from this end point
https://identity.aramexconnect.com.au/connect/token
with the scope code set asac-api-au
. I received a token and then tested the sameserviced-by
request and had the same issues. I even tested requesting with this urlhttps://api.aramexconnect.com.au/api/addresses/serviced-by
with my new auth token.