Response Codes and Errors

Response Codes and Errors

All APIs may respond with one of the following response codes:

200 OK:
The request was successful and the response body contains the representation requested.

204 No Response:
The request was successful, but there is no information to send back (usually returned by successful non-GET operations).

302 Found:
A common redirect response; you can GET the representation at the URI in the Location response header.

400 Bad Request:
The data given in the request failed validation. Inspect the response body for details (see Error data structure for details).

401 Unauthorized:
The supplied credentials, if any, are not sufficient to access the resource.

404 Not Found:
Resource is not available under requested URL.

500 Server Error:
This usually means there was a problem on Duda's end. Double check to make sure your data sent is correct then reach out to Duda for help.

The applicative validations and errors are returned with 400 (Bad Request) HTTP response code accompanied with the following Error structure in JSON:

PROPERTY TYPE DESCRIPTION
error_code String Code of the error, i.e. ResourceNotExist InvalidInput InternalError.
message String Detailed error message
×

Priority Phone Support

English phone support is available 18 hours a day,
Monday through Friday, 3am to 9pm (EST).

United States +1 866-776-1550 3am to 9pm (Eastern)
United Kingdom +44 (0)800-011-9071 8am to 2am (London)
France +33 (0)9-75-18-84-74 9am to 3am (Paris)
Israel +972 (0)3-720-8922 10am to 4am (Jerusalem)
Australia +61 (0)2-8880-9166 7pm to 1pm (Sydney)
To schedule a call in French, Portuguese, Hebrew or Russian, please email us at prioritysupport@dudamobile.com
×

Please Log in as a DudaPro

Priority Phone Support is available exclusively to DudaPros. Log in to your DudaPro account now to see our international support numbers.

Log In
Not a DudaPro? Start a free trial now!