API Conventions
This page describes the conventions and rules that apply to all Recranet Booking API requests. Following these conventions ensures consistent and predictable behavior across all endpoints.
Base URL
All API requests are made to: https://app.recranet.com/api
HTTP Methods
The API uses standard HTTP methods to indicate the type of operation:
| Method | Purpose |
|---|---|
| GET | Retrieve data |
| POST | Create a new resource |
| PUT | Update an existing resource |
| PATCH | Batch update/create resources |
| DELETE | Remove a resource |
Required Headers
Every request must include the following headers:
Accept: application/json
Content-Type: application/jsonThe Accept header is required on all requests. The Content-Type header is required when sending a request body (POST, PUT, PATCH).
Organization Scope
Most endpoints require an organization context. To make sure the correct organizational scope is used, provide the organization ID as a query parameter to all requests. Some endpoints do not need a organization ID, but it's easier to provide it by default.
?organization=1000
Requests without a valid organization context will be rejected.
Date and Time Formats
The API uses ISO 8601 formats for all date and time values.
Date only:
2026-01-15
DateTime (with timezone):
2026-01-15T14:30:00+01:00
All datetime values are returned in UTC unless otherwise specified.
Updated 16 days ago