CharterOps exposes aircraft, operators, airports and charter records through a versioned JSON API. This guide describes the implemented API preview. Public access is coming soon.
Choose a plan and activate access
When signup opens, create your account in the dashboard and choose an organization plan. Open Settings > API to enable API access, with 250,000 monthly requests and 10 API keys. Payment must activate the organization before you can enter the app or create and use API keys; selecting a plan alone does not activate access. Complimentary access requires an explicit administrator grant. If payment is not configured, the dashboard shows Payment not available yet.
Create a key
In the dashboard, an organization owner or admin can create a key under API: open the organization menu at the bottom of the sidebar and choose API. Choose the smallest set of scopes your integration needs. Copy the secret when it appears; it is shown once.
Keep the key on your server, outside source control. The examples below use environment variables. Set CHARTEROPS_API_URL to your verified API origin and CHARTEROPS_API_KEY to your key before running them.
Read aircraft
curl --get "$CHARTEROPS_API_URL/v1/aircraft" \
--header "Authorization: Bearer $CHARTEROPS_API_KEY" \
--data-urlencode "limit=10"A successful list response contains items, next_cursor and total. Aircraft records describe registry information; they do not establish charter availability.
Read airports
curl --get "$CHARTEROPS_API_URL/v1/airports" \
--header "Authorization: Bearer $CHARTEROPS_API_KEY" \
--data-urlencode "q=Teterboro" \
--data-urlencode "limit=10"Use the API reference for every field and filter. Follow pagination to read additional pages, and check errors before adding retries.
Inspect one airport and your allowance
curl --include "$CHARTEROPS_API_URL/v1/airports/KTEB" \
--header "Authorization: Bearer $CHARTEROPS_API_KEY"Read X-Quota-Limit, X-Quota-Remaining and X-Quota-Reset from the response headers. For trip estimates, consult POST /v1/estimates in the reference and supply the required request body. Estimates are informational, not operator quotes.