Error Handling

The PostSyncer API uses standard HTTP status codes and returns detailed error messages to help you debug issues quickly.

HTTP Status Codes

Status Code	Description
`200`	Success - Request completed successfully
`201`	Created - Resource created successfully
`400`	Bad Request - Invalid request parameters
`401`	Unauthorized - Invalid or missing API key
`403`	Forbidden - Insufficient permissions
`404`	Not Found - Resource doesn’t exist
`422`	Unprocessable Entity - Validation errors
`429`	Too Many Requests - Rate limit exceeded
`500`	Internal Server Error - Server error

Error Response Format

All error responses follow this format:

{
  "message": "Human-readable error message",
  "errors": {}
}

Common Error Codes

Authentication Errors

{
  "message": "Unauthenticated"
}

Validation Errors

{
    "message": "The workspace id field is required.",
    "errors": {
        "workspace_id": [
            "The workspace id field is required."
        ]
    }
}

Rate Limit Errors

{
  "message": "Too Many Attempts."
}

Best Practices

Check Status Codes

Always check HTTP status codes before processing responses

Handle Rate Limits

Implement retry logic for 429 responses with exponential backoff

Log Errors

Log detailed error information for debugging

Validate Input

Validate data before sending to avoid 422 errors

Authentication

OAuth Delegation

Start here

Guides

MCP

API reference

Error Handling

Error Handling

HTTP Status Codes

Error Response Format

Common Error Codes

Authentication Errors

Validation Errors

Rate Limit Errors

Best Practices

Check Status Codes

Handle Rate Limits

Log Errors

Validate Input

​Error Handling

​HTTP Status Codes

​Error Response Format

​Common Error Codes

​Authentication Errors

​Validation Errors

​Rate Limit Errors

​Best Practices

Check Status Codes

Handle Rate Limits

Log Errors

Validate Input

Error Handling

HTTP Status Codes

Error Response Format

Common Error Codes

Authentication Errors

Validation Errors

Rate Limit Errors

Best Practices