Introduction - PREXSELL API

The PREXSELL REST API exposes a Distribution API for agents and PREXSELL’s own client applications.

Client types

Distribution API

For agents (third-party resellers), the PREXSELL website, and the PREXSELL app. Authenticated with a long-lived API key sent in the x-api-key header. Use this for booking flows, catalog reads, and any integration that runs outside the PREXSELL backoffice.

Distribution catalog endpoints (cities, stops) are read-only reference data.

Base URL

https://api.prexsell.com

https://staging.api.prexsell.com

All endpoints in this reference are versioned under /v2.

Authentication

Distribution API — API key

Distribution endpoints are authenticated with an API key passed in the x-api-key header:

curl https://api.prexsell.com/v2/cities \
  -H "x-api-key: <your-api-key>"

API keys are issued from the PREXSELL backoffice. Register as a PREXSELL partner at backoffice.prexsell.com (or staging.backoffice.prexsell.com for staging) to obtain one, and contact support if you need help. Keys are scoped to a single environment (staging vs production), so register in the environment you’ll integrate against. Treat them as secrets — keep them on the server side, never ship them in browser or mobile bundles.

API-key enforcement is being rolled out across the v2 Distribution surface. Read-only catalog endpoints (cities, stops) are currently open while partner provisioning is finalized; pass the x-api-key header anyway so your client keeps working once enforcement turns on.

Quick start

# List cities — Distribution endpoint, API-key authenticated
curl https://staging.api.prexsell.com/v2/cities \
  -H "x-api-key: <your-api-key>"

Response envelope

Successful responses are wrapped in a data object:

{
  "data": { "...": "..." }
}

List endpoints additionally include a total counter for the unpaginated result set and accept take (max 100, default 50) and skip (default 0) query parameters.

Errors

Errors are returned with an appropriate HTTP status and an errors array describing what went wrong:

{
  "errors": [
    {
      "code": "UNAUTHORIZED",
      "message": "Missing or invalid credentials."
    }
  ]
}

Common status codes:

Status	Meaning
`200`	Success.
`201`	Resource created.
`204`	Success, no response body.
`400`	Validation error — check the request shape.
`401`	Missing or invalid API key / access token.
`403`	Authenticated, but not allowed to do this.
`404`	Resource not found.
`409`	Conflict — the resource is in an incompatible state.
`429`	Rate limit exceeded.
`500`	Unexpected server error.

Next steps

Getting started

Walk through a full Distribution integration end to end — search offers, create a booking, pay, and cancel.

​Client types

Distribution API

​Base URL

​Authentication

​Distribution API — API key

​Quick start

​Response envelope

​Errors

​Next steps

Getting started

Client types

Base URL

Authentication

Distribution API — API key

Quick start

Response envelope

Errors

Next steps