Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.proxyjam.com/llms.txt

Use this file to discover all available pages before exploring further.

ProxyJam uses standard HTTP status codes and returns a consistent error body.

​
Error response format

{
  "detail": "Human-readable description of the error."
}
Some validation errors return a structured list of fields: 
{
  "detail": [
    {
      "loc": ["body", "email"],
      "msg": "value is not a valid email address",
      "type": "value_error.email"
    }
  ]
}

​
HTTP status codes

CodeMeaning
200Success
201Resource created
400Bad request — invalid input or validation error
401Unauthorized — missing or expired token
403Forbidden — authenticated but not allowed
404Resource not found
409Conflict — duplicate or already exists
422Unprocessable entity — request body fails schema validation
429Too many requests — rate limit exceeded
500Internal server error

​
Common errors

Your access_token is missing, expired, or malformed. Refresh it using POST /users/refresh.
Your account exists but does not have permission to access this resource. This can happen if the resource belongs to another user.
Returned when you try to create a resource that already exists, such as registering with an email that is already in use.
The request body is valid JSON but fails field-level validation. Check the detail array for which fields are invalid.
The API enforces a global rate limit of 100 requests per minute. Slow down and retry after a short delay.