gitlabEdit

โŒCommon Errors

Complete reference for HTTP errors, error codes, and solutions in Docs-Dispatcher.

Overview

This guide covers:

  • HTTP status codes (400-503)

  • Error response structure

  • Provider-specific errors

  • Template errors

  • Authentication errors

  • Validation errors

  • Solutions with code examples

Error Response Structure

All errors follow a consistent format:

{
  "error": "error_code",
  "message": "Human-readable error description",
  "details": {
    "field": "specific.field.path",
    "value": "actual_value",
    "expected": "expected_value"
  },
  "timestamp": "2026-02-13T10:30:00Z",
  "path": "/api/invoicing",
  "requestId": "req_abc123xyz"
}
Field
Description

error

Machine-readable error code

message

Human-readable description

details

Additional context (optional)

timestamp

When error occurred

path

API endpoint that failed

requestId

For support tracking

HTTP Status Codes

400 Bad Request

Meaning: Request is malformed or invalid.

Common Causes

1. Missing Required Field

Solution:

2. Invalid Field Type

Solution:

3. Invalid Enum Value

Solution:

4. Provider Not Configured

Solution:

5. Invalid Provider for Service

Solution:

401 Unauthorized

Meaning: Authentication failed or missing.

Common Causes

1. Missing JWT Token

Solution:

2. Expired JWT Token

Solution:

3. Invalid Token Format

Solution:

403 Forbidden

Meaning: Authenticated but not authorized for this resource.

Common Causes

1. Insufficient Permissions

Solution:

2. Template Access Denied

Solution:

404 Not Found

Meaning: Resource does not exist.

Common Causes

1. Template Not Found

Solution:

2. Endpoint Not Found

Solution:

409 Conflict

Meaning: Request conflicts with existing resource.

Common Causes

1. Duplicate Invoice Number

Solution:

415 Unsupported Media Type

Meaning: Content-Type header is incorrect.

Solution:

417 Expectation Failed

Meaning: Provider-specific requirement not met.

Solution:

422 Unprocessable Entity

Meaning: Request syntax valid but semantically incorrect.

Common Causes

1. Validation Errors

Solution:

2. Template Schema Mismatch

Solution:

429 Too Many Requests

Meaning: Rate limit exceeded.

Solution:

500 Internal Server Error

Meaning: Server-side error occurred.

Solution:

501 Not Implemented

Meaning: Feature not yet implemented.

503 Service Unavailable

Meaning: Service temporarily unavailable (maintenance, overload).

Solution:

Error Code Reference

Quick lookup table for all error codes:

Code
Status
Category
Common Cause

missing_required_field

400

Validation

Missing field in request

invalid_field_type

400

Validation

Wrong data type

invalid_enum_value

400

Validation

Invalid enum value

provider_not_configured

400

Configuration

Provider not set up

invalid_provider

400

Configuration

Wrong provider for service

authentication_required

401

Auth

Missing JWT token

token_expired

401

Auth

JWT expired

invalid_token

401

Auth

Malformed JWT

insufficient_permissions

403

Authorization

User lacks permission

template_access_denied

403

Authorization

Template not accessible

template_not_found

404

Resource

Template doesn't exist

not_found

404

Resource

Endpoint doesn't exist

duplicate_invoice

409

Conflict

Invoice number exists

unsupported_media_type

415

Headers

Wrong Content-Type

provider_validation_failed

417

Provider

Provider rejected

validation_failed

422

Validation

Business rule violation

template_schema_mismatch

422

Validation

Data doesn't match schema

rate_limit_exceeded

429

Rate Limit

Too many requests

internal_error

500

Server

Server-side error

not_implemented

501

Feature

Feature not available

service_unavailable

503

Availability

Temporary outage

Provider-Specific Errors

Qonto

Duplicate Invoice:

Invalid Organization:

PennyLane

Missing SIRET:

Brevo (SMS)

Invalid Phone Number:

Universign (eSign)

Invalid Signer:

Debugging Workflow

When you encounter an error:

  1. Check HTTP status code - Identifies error category

  2. Read error.message - Human-readable description

  3. Examine error.details - Specific context

  4. Look up error code - Find solution in this guide

  5. Check requestId - For support tickets

  6. Review request data - Find what's wrong

  7. Validate before retry - Use /validate endpoint

Summary

Key takeaways:

  • All errors follow consistent structure with error, message, details

  • HTTP status codes indicate error category (400s = client, 500s = server)

  • Always validate requests before dispatch to catch errors early

  • Implement proper error handling with retries and logging

  • Use requestId when contacting support

  • Check provider-specific requirements for 417/422 errors

  • Implement exponential backoff for 429 rate limits

  • Refresh JWT tokens proactively to avoid 401 errors

When stuck: Copy the error code and requestId, search this guide, and include both in support requests.

Last updated