Skip to main content

Overview

Proper error handling is crucial for building reliable document processing applications. This guide covers all Pulse API error codes, retry strategies, and best practices for graceful error recovery.

Error Response Format

All errors follow a consistent JSON structure:

Error Categories

Authentication

AUTH_XXX - API key issues

Request

REQ_XXX - Invalid parameters

File

FILE_XXX - File format/size issues

Schema

SCHEMA_XXX - Schema validation

Billing

BILLING_XXX - Usage limit issues

Processing

PROC_XXX - Processing failures

Job

JOB_XXX - Async job issues

Storage

STORAGE_XXX - Storage issues

General

GENERAL_XXX - Server errors

Complete Error Code Reference

Authentication Errors (AUTH_XXX)

Request Errors (REQ_XXX)

File Errors (FILE_XXX)

Schema Errors (SCHEMA_XXX)

Billing Errors (BILLING_XXX)

Processing Errors (PROC_XXX)

Job Errors (JOB_XXX)

Storage Errors (STORAGE_XXX)

General Errors (GENERAL_XXX)

Handling Errors in Code

Basic Error Handling

Comprehensive Error Handler

Retry Strategies

Exponential Backoff

Circuit Breaker Pattern

Intelligent Retry Logic

Error Recovery Patterns

Graceful Degradation

Partial Success Handling

Best Practices

  • Never assume API calls will succeed
  • Catch and handle specific error codes
  • Provide meaningful error messages to users
  • Log errors for debugging
  • Use exponential backoff for transient errors
  • Set reasonable retry limits
  • Only retry retryable errors
  • Add jitter to prevent thundering herd
  • Track error frequencies
  • Alert on error spikes
  • Analyze patterns for optimization
  • Review logs regularly
  • Have fallback strategies
  • Accept partial success
  • Inform users of degraded functionality
  • Queue for later retry if appropriate

Common Error Scenarios

Scenario 1: File Upload Issues

Scenario 2: Async Job Management

Next Steps

API Reference

See endpoint details