Thank you for the reply @Sergi , the issue was resolved now without any code change. Is there anything we can do to check/investigate further to prevent this from happening?
EDIT: On the same point, the same exact address for pickup and drop off that we are using are now working without any code change.
Thank you for the reply @Sergi , just today I got this error "{\"error\":\"RECORD_INVALID\",\"message\":\"Unable to save record\",\"data\":{\"job.pickup_at\":[\"can not schedule a pickup at this time\",\"is not valid\"]}}"
Thank you for the details of the error you get, yes this makes sense, so this error is to do with operating hours. Each zone is configured to have a certain opening and closing time and if a pickup time is requested to be outside of those hours (let’s say 3am), the request will fail. Currently these hours are 7am - midnight local time as a general rule.
This is also true for the validate endpoints. So in order to validate requests or get a pricing, you’d need to specify a pickup time that is within the opening hours range for that zone. If you’d like to double check a specific zone’s opening hours I’d be happy to verify that for you - is this in our Sandbox or our Production environment by the way?