Rexpondo API

REST API reference for Rexpondo — the web-based ticketing system for service organisations.

Getting Started

The Rexpondo REST API allows you to interact programmatically with the ticketing system. All endpoints are prefixed with /rexpondo/api/.

Authentication

All API requests require authentication via the Authorization header using a Bearer token.

Tokens can be generated directly from the agent interface, under the personal preferences section. Each agent can create and manage their own API tokens.

GET /rexpondo/api/ticket/123
Authorization: Bearer <your-api-token>

Note: tokens are personal and tied to the agent who generated them. Treat them as credentials and do not share them.

Acting on Behalf of Another User

Administrators can perform operations on behalf of another agent using the X-On-Behalf-Of header. This is useful for integrations that need to create or modify tickets as a specific user.

POST /rexpondo/api/ticket
Authorization: Bearer <admin-api-token>
X-On-Behalf-Of: <target-user-id>
Content-Type: application/json

{
    "Title": "Ticket created on behalf of another user",
    "QueueID": 1
}

Requirements:

• The authenticated user must have admin group permissions (rw)
• The value must be a valid User ID of an existing agent
• If omitted, the request is executed as the authenticated user

Common Headers

Header	Required	Description
Authorization	Yes	Bearer token. Format: Bearer <token>
Content-Type	POST/PATCH	Must be application/json
X-On-Behalf-Of	No	User ID to impersonate (requires admin)
X-Pagination-Current-Page	No	Page number (1-based)
X-Pagination-Per-Page	No	Items per page

Response Format

All responses are JSON. Successful responses return the requested data directly; errors return an object with an error field.

// Success
{ "TicketID": 1, "Title": "My Ticket", ... }

// Error
{ "error": "Need TicketID" }