Skip to main content
The V1 API is deprecated. Starting November 1st 2025, no support will be provided for the V1 API and it will be removed by April 2026. No new features nor functionality will be added to the V1 API. Please use the V2 Verify API instead. For more information refer to the V2 Migration Guide.
Prelude uses conventional HTTP statuses to indicate the success or failure of a request:
  • Codes in the 2xx range indicate success.
  • Codes in the 4xx range indicate an error that failed given the information provided (e.g. required parameter was omitted or an authentication failed).
  • Codes in the 5xx range indicate an error with Prelude’s servers (these are rare).

​
Codes

Below is a list of possible error codes, along with additional information about how to resolve them.
​
code
enum<string>

A machine-readable code that describes the error.

Available options:
account_invalid,
app_realm_require_device_type,
bad_request,
blocked_number,
internal_server_error,
invalid_app_realm,
invalid_app_version,
invalid_auth_uuid,
invalid_device_id,
invalid_device_model,
invalid_line,
invalid_os_version,
invalid_phone_number,
invalid_sender_id,
invalid_template_id,
negative_balance,
no_associated_auth_found,
suspended_account,
unauthorized_sender_id,
unsupported_app_realm_device_type,
unsupported_region
Example:

"invalid_phone_number"

​
message
string

A human-readable message that describes the error.

Example:

"+0 is not a valid phone number"

​
doc_url
string

A link to the documentation that describes the error.

Example:

"https://docs.prelude.so/verify/v1/documentation/errors#invalid_phone_number"