Rapid account: PostalNinja

PostalNinja / PostalNinja

Discussions

5
Title
Created at (Click to sort ascending)
A
1
Hello, I didn't see any errors except legit in your request log on RapidAPI website. If it works from RapidAPI playground but returns such errors for POST request in your scripts - I think this is due to malformed requests you are trying to submit. Don't know reason as RapidAPI doesn't show invalid requests in the log. But it's either invalid request headers or malformed request body (e.g. you are sending POST data as json instead of url-encoded form). Hard to guess without seeing your code. lun. 8:12 13/11/23
A
1
Hello, Getting fresh data from postal services takes some time. Usually from 10-20 seconds up to 60 seconds and even more for "slow" providers. So to get refreshed data after 1st createTrack/refreshTrack request you should: - either wait some time before submitting getTrack request with await=false parameter - or set await=true for your getTrack request (but with proper timeout - at least 60 seconds). ven. 6:36 28/7/23
A
1
Hello. Doesn't see any 4XX or 5XX errors in logs. Probably this is some kind of rate limiting on RapidAPI side. mer. 9:02 19/7/23
A
1
Hello. For such generic digits-only tracking numbers you should either provide exact carrier id (ds parameter for createTrack call) or at least country code (destCountry parameter). That's because there are too many different local carriers with such digits-only numbers. When you track such numbers on the website we guess that visitor from certain country most likely has tracking number from some local carrier from his country. For API calls we can't use such heuristic. So API users should use one or both parameters mentioned above. ven. 8:19 9/6/23
A
1
Hello. Not sure is this issue on the RapidAPI or our side as I don't see any errors in logs. Could you please try again and check if this error still persist? mar. 12:38 9/5/23