Timeout
The request ran past 30 seconds and was stopped.
- Status
504Gateway Timeout- Type
https://developers.checkmystreet.co.uk/errors/timeout- Charged
- At most once. Retry with the same key and you are never charged twice.
- Retry
- Yes, with the same key.
Example
{
"type": "https://developers.checkmystreet.co.uk/errors/timeout",
"title": "Timeout",
"status": 504,
"detail": "The request took longer than 30 seconds. Retry with the same Idempotency-Key."
}
What to do
- Retry with the same
Idempotency-Key. If the first attempt finished after we stopped waiting, the retry returns its result at no extra charge. - Set your HTTP client's timeout a little above 30 seconds, for example 35, so you receive this response rather than your own timeout.
- The first call after a quiet period can be slower than the rest.
Test it
In test mode, the postcode ZZ1 7AA returns this error:
curl -X POST https://api.checkmystreet.co.uk/partners/v1/valuations \
-H "Authorization: Bearer $TOKEN" \
-H "Idempotency-Key: 9d41e7a2-6c3b-4f18-8e5a-0b7c2d9f4a61" \
-H "Content-Type: application/json" \
-d '{ "postcode": "ZZ1 7AA", "propertyType": "flat", "bedrooms": 2 }'
Related
data-unavailable: a data source was down; never charged.request-in-progress: you retried while the first attempt was still running.- All errors