Developer Documentation

Reference for the REXTEN REST API and the official REXTEN Zapier integration. API access is available on the Enterprise plan and is scoped to your own company's data.

Base URL

All REST API requests use the versioned base URL below.

Base URL
https://api.rexten.pro/api/v1

Authentication

Send your personal access token in the Authorization header with every request.

Authorization: Bearer YOUR_TOKEN

Endpoints

All endpoints are read-only and scoped to your company.

GET/v1/me

Current company and account.

GET/v1/services

List services.

GET/v1/services/{id}

Get a service by id.

GET/v1/clients

List clients.

GET/v1/clients/{id}

Get a client by id.

GET/v1/bookings

List bookings.

GET/v1/bookings/{id}

Get a booking by id.

GET/v1/team-members

List team members (specialists).

GET/v1/reviews

List reviews.

GET/v1/schedule

Working schedule and availability.

Query parameters

Pagination: page, per_page (max 100).

Filters: search, date ranges and status are supported on list endpoints.

Response format

List endpoints return a data array with meta pagination; single endpoints return a data object.

List response
{
  "data": [
    { "id": 1 }
  ],
  "meta": { "page": 1, "per_page": 25, "total": 120, "last_page": 5 }
}
Single response
{
  "data": { "id": 42 }
}

Rate limits

Requests are rate-limited per token. When the limit is exceeded the API responds with HTTP 429.

Errors

Errors return a JSON body with an error code and a human-readable message.

JSON
{
  "error": "forbidden",
  "message": "..."
}

Example request

Replace YOUR_TOKEN with your personal access token.

cURL
curl -sS -H "Authorization: Bearer YOUR_TOKEN" \
  https://api.rexten.pro/api/v1/me

Connect REXTEN to thousands of apps with Zapier. You authorize Zapier from your Zapier account — REXTEN acts as the OAuth 2.0 provider, and each connection works only with your own company's data.

The Zapier integration requires the Enterprise plan (API access).

Authentication (OAuth 2.0)

Zapier uses the OAuth 2.0 authorization-code flow with automatic token refresh.

GEThttps://api.rexten.pro/oauth/authorize

Authorization URL — the user grants access.

POSThttps://api.rexten.pro/oauth/token

Access Token URL — exchanges the code for tokens.

POSThttps://api.rexten.pro/oauth/token

Refresh Token URL — same endpoint with grant_type=refresh_token.

POSThttps://api.rexten.pro/oauth/revoke

Token revocation (RFC 7009).

GEThttps://api.rexten.pro/api/zapier/v1/me

Connection test endpoint.

Supported scopes: read write. Access tokens expire and are refreshed automatically.

Headers sent on every API call
Authorization: Bearer ACCESS_TOKEN
Accept: application/json

Triggers

GEThttps://api.rexten.pro/api/zapier/v1/bookings

Triggers when a new booking is created in your workspace (polling).

New Booking

Sample
{
  "id": "booking_123",
  "booking_id": 123,
  "status": "confirmed",
  "customer_id": 456,
  "customer_name": "John Smith",
  "customer_email": "[email protected]",
  "customer_phone": "+13239990000",
  "service_id": 12,
  "service_name": "Deep Cleaning",
  "specialist_id": 8,
  "specialist_name": "Anna",
  "start_at": "2026-06-25T10:00:00-07:00",
  "end_at": "2026-06-25T12:00:00-07:00",
  "timezone": "America/Los_Angeles",
  "total_amount": "180.00",
  "currency": "USD",
  "created_at": "2026-06-23T19:00:00+00:00",
  "updated_at": "2026-06-23T19:00:00+00:00"
}

Actions

POSThttps://api.rexten.pro/api/zapier/v1/customers

Creates a new customer in your workspace.

Create Customer

Input fields: first_name (required), last_name, email, phone, address, notes.

Request body
{
  "first_name": "John",
  "last_name": "Smith",
  "email": "[email protected]",
  "phone": "+13239990000"
}
POSThttps://api.rexten.pro/api/zapier/v1/bookings

Creates a booking using REXTEN scheduling and availability checks.

Create Booking

Input fields: service_id (required), start_at (required), customer_id or customer, specialist_id, timezone, notes, status.

Request body
{
  "customer_id": 456,
  "service_id": 12,
  "specialist_id": 8,
  "start_at": "2026-06-25T10:00:00",
  "timezone": "America/Los_Angeles",
  "notes": "From Zapier"
}

Dynamic dropdowns

These endpoints power the customer, service and specialist pickers inside Zapier actions.

GEThttps://api.rexten.pro/api/zapier/v1/customers

Customers — id, name, email, phone.

GEThttps://api.rexten.pro/api/zapier/v1/services

Services — id, name, duration_minutes, price, currency.

GEThttps://api.rexten.pro/api/zapier/v1/specialists

Specialists — id, name.

Security

  • The company is resolved from the OAuth token; it is never accepted from the request.
  • Every query is scoped to the current company; objects from other companies return 404/422.
  • Dedicated rate limits for the Zapier API and OAuth endpoints.
  • read/write scopes, access-token expiry with refresh, and token revocation.
  • Responses never include payment or card data or internal tokens.

How to connect

In Zapier, create a Zap, search for REXTEN, and choose “Connect a new account”. Sign in with your REXTEN business account and authorize access. You can then use REXTEN triggers and actions in your Zaps.