Errors

SuprSend uses standard HTTP response codes to indicate the success or failure of your API requests. This page covers common error codes and how to handle them.

Success Codes

Code	Description
`200`	OK - Request succeeded
`201`	Created - Resource was successfully created
`204`	No Content - Request succeeded but no content returned

Error Codes

Code	Description
`400`	Bad Request - Invalid request syntax or parameters
`401`	Unauthorized - Authentication required or failed
`404`	Not Found - Resource not found
`409`	Conflict - No uncommitted changes to commit, or duplicate entry
`5xx`	Internal Server Error - Unexpected server error

Error Response Format

All error responses follow a consistent format:

{
  "code": 400,
  "error_code": "error",
  "type": "ValidationError",
  "message": "{\"name\": [\"This field is required.\"]}",
  "detail": {
    "name": ["This field is required."]
  }
}

Field	Type	Description
`code`	integer	HTTP status code
`error_code`	string	Machine-readable error identifier (e.g. `authentication_failed`, `not_authenticated`, `not_found`, `invalid`, `error`, `no_changes_to_commit`)
`type`	string	Error type classification
`message`	string	Human-readable error message. When `detail` is an array or object, this is the JSON-encoded `detail` value
`detail`	string, array, or object	Additional error details. A string for simple errors, an array of messages for non-field validation errors, or an object keyed by field name for field validation errors

Common Error Codes and their solutions

401 Unauthorized - `authentication_failed` / `not_authenticated`

Causes:

Missing Authorization header, or a scheme other than ServiceToken (not_authenticated)
Invalid service token (authentication_failed)
Disabled (revoked) service token (authentication_failed)
Using environment API key instead of service token

Correct Syntax to authorize Management API:

# Ensure you're using a valid service token
curl -H "Authorization: ServiceToken YOUR_SERVICE_TOKEN" \
     https://management-api.suprsend.com/v1/<WORKSPACE_SLUG>/workflow/

400 Bad Request - `error` / `invalid`

Common Causes:

Missing required fields
Invalid field formats
Invalid enum values

Example:

{
  "code": 400,
  "error_code": "error",
  "type": "ValidationError",
  "message": "{\"name\": [\"This field is required.\"]}",
  "detail": {
    "name": ["This field is required."]
  }
}

404 Not Found

Common Causes:

Given entity in the request is not found

Example:

{
  "code": 404,
  "error_code": "not_found",
  "type": "NotFound",
  "message": "workflow (slug: 'welcome-sequence') not found",
  "detail": "workflow (slug: 'welcome-sequence') not found"
}

409 Conflict - `no_changes_to_commit`

Common Causes:

Calling a commit endpoint when the draft is identical to the live version

Example:

{
  "code": 409,
  "error_code": "no_changes_to_commit",
  "type": "NoChangesToCommitError",
  "message": "no uncommitted changes detected in workflow",
  "detail": "no uncommitted changes detected in workflow"
}

API Reference

WORKSPACE & AUTH KEYS

WORKFLOWS

SCHEMAS

EVENTS

CATEGORIES

TRANSLATIONS

TEMPLATES

Success Codes

Error Codes

Error Response Format

Common Error Codes and their solutions

401 Unauthorized - `authentication_failed` / `not_authenticated`

400 Bad Request - `error` / `invalid`

404 Not Found

409 Conflict - `no_changes_to_commit`

​Success Codes

​Error Codes

​Error Response Format

​Common Error Codes and their solutions

​401 Unauthorized - authentication_failed / not_authenticated

​400 Bad Request - error / invalid

​404 Not Found

​409 Conflict - no_changes_to_commit

Success Codes

Error Codes

Error Response Format

Common Error Codes and their solutions

401 Unauthorized - `authentication_failed` / `not_authenticated`

400 Bad Request - `error` / `invalid`

404 Not Found

409 Conflict - `no_changes_to_commit`