Developer platform

An open API for your entire crew workflow

Pull pilot schedules into your dispatch board, BI dashboards or HR systems, and act on crew duty requests from your own tools, using the same data and actions your team has in CrewBench.

Start free — no card needed Read the API docs

REST + JSON Bearer API keys Versioned under /v1 60 requests / min per key

What syncs

Read your schedule. Act on crew requests.

Every endpoint lives under https://crewbench.io/api/v1/external and returns JSON.

GET

/schedule

Every active pilot with role, IOE and check airman flags, and their duty days for any date range.

GET

/duty_requests

All pending duty requests, with a flag showing which ones need a decision from your team.

POST

/duty_requests/:id/approve · /decline

Approve or decline a pilot request from your own tools, with an optional message back to the pilot.

POST

/duty_requests/:id/modify

Partially approve a request by confirming only some of the dates a pilot asked for.

$ curl "https://crewbench.io/api/v1/external/schedule?start_date=2026-10-01&end_date=2026-10-31" \
    -H "Authorization: Bearer cbk_your_api_key"

{
  "schedule": [
    { "id": 42, "name": "John Smith", "role": "Captain",
      "duty_days": [{ "date": "2026-10-05", "duty_code": "ON", "label": "On Duty" }] }
  ],
  "start_date": "2026-10-01",
  "end_date": "2026-10-31"
}

How it works

From API key to first request in minutes

No SDK needed. Any language that can make an HTTPS request will work.

1
Generate a key

In Settings → API, name your key (e.g. "Dispatch board") and generate it. It is shown once, then stored only as a hash.
2
Authenticate

Send the key as a Bearer token in the Authorization header of every request.
3
Build

Read schedules and act on duty requests. Revoke a key at any time and it stops working immediately.

Why it matters

What operators build with the CrewBench API

If your tool is not on our integrations list yet, the API means you do not have to wait.

Dispatch & ops boards

Show who is on duty right next to the flight board your dispatchers already watch.

BI & reporting

Feed duty days into your data warehouse or BI dashboards for utilisation and staffing analysis.

HR & payroll systems

Sync schedules into payroll or HR tools that CrewBench does not integrate with natively yet.

Workflow automation

Approve routine duty requests automatically, or route them to the right chief pilot in your own system.

FAQ

Common questions about the CrewBench API

Does CrewBench have an API? +

Yes. CrewBench has a REST API that returns JSON. You can read your pilot schedule and duty requests, and approve, decline or partially approve duty requests programmatically.

How do I authenticate with the CrewBench API? +

Generate an API key in Settings → API and send it in the Authorization header as a Bearer token. Keys are shown once, stored only as a one-way hash, and can be revoked at any time.

Are there rate limits? +

Yes. Each API key can make 60 requests per minute. Requests over the limit receive a 429 response. Wait a minute and retry.

Is the API versioned? +

Yes. The current version is v1 and is part of every endpoint URL. Breaking changes will be released under a new version.

Where can I find the full API documentation? +

The full reference, with parameters, example requests and responses, and error codes, is at crewbench.io/api-docs.