Lol, I can’t even get an OAUTH token from the sandbox now… again live remains fine… it returns 401 despite being supplied the correct id/secret… is everything okay over there?
Thank you Luis,
I am also able to reproduce the error now and raising the problem internally. I will come back to you as soon as I have more information.
The ETA is based on the fleet availability depending on the area, unfortunately it seems that the way that our driver bots are spawned may be contributing to the fact that no drivers appear to be available when calling the ETA endpoint.
It is possible to still create a job even if the eta endpoint indicates that there are no drivers available (even in Production) since the state of the fleet is ever changing and jobs can also be scheduled into the future. Feel free to go ahead and try creating jobs, they should still get assigned.
We are looking into this issue with this Sandbox ETA endpoint showing ‘NO_DRIVER_AVAILABLE’ and apologise again for the inconvenience. We will keep you posted on any updates.
–
On the credit card issue, I have set your account to no longer require the credit card for this Sandbox account. You shouldn’t receive any errors related to this now.
Is this error referring to your Sandbox or Production account?
You can find more details on adding credit card details to a Sandbox account here including some mock credentials, note to not use American Express. Example credentials that should work are `4111111111111111, 11/12, 123, tester’