Getting Started

Push trip data from any external system — ERPs, custom scheduling tools, other FBO software — directly into AirPlx. One POST request creates trips on your schedule, with the same data quality and aircraft matching as the email integration, but without the email.

How It Works


  External System        POST /api/v1/trips        AirPlx
  (ERP, scheduler,   ----------------------->    processes request,
   custom tool)          with Bearer token         matches aircraft,
                                                   creates trips
                         JSON response
                    <-----------------------     returns per-trip
                                                   status

You generate an API key in AirPlx Settings
Your system sends a POST request with one or more trips
AirPlx matches aircraft, validates data, and creates the trips
Each trip gets an individual status in the response (created, duplicate, quarantined, or failed)
Trips appear on your schedule immediately

Authentication

All requests require a Bearer token in the Authorization header. API keys are scoped to a single FBO — requests are authenticated against the FBO that owns the key.


Authorization: Bearer ak_your_api_key_here

Setup

Generate an API Key

Go to Settings > Integrations in AirPlx
Find the API Keys card
Click Generate New Key
Enter a label (e.g., “ERP Integration”)
Copy the key immediately — it won’t be shown again

Store your API key securely. Treat it like a password. If compromised, revoke it immediately in Settings and generate a new one.

Verify Your Key

Use the verify endpoint to confirm your key is valid and see which FBO it’s scoped to. No data is created — this is just a connectivity check.

GET /api/v1/auth/verify


curl https://api.airplx.com/api/v1/auth/verify \
  -H "Authorization: Bearer ak_your_api_key_here"

Response (200 OK):


{
  "valid": true,
  "fbo_id": "d3b07384-d113-4ec8-...",
  "fbo_name": "Hailey Air Center",
  "key_prefix": "ak_3f7c8a9b",
  "label": "ERP Integration"
}

If the key is invalid, revoked, or disabled, you’ll get a 401.

Send Your First Trip


curl -X POST https://api.airplx.com/api/v1/trips \
  -H "Authorization: Bearer ak_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "trips": [
      {
        "tail_number": "N236MJ",
        "arrival_date": "2026-03-15T14:30:00Z"
      }
    ]
  }'

That’s the minimum — just a tail number and an arrival time. See Creating Trips for the full field reference and code examples.

Check the Result

Check your schedule — the trip should appear within seconds. If the tail number isn’t in the AirPlx database, the trip is queued in your Operations Inbox for review instead.

Managing API Keys

API keys are managed in Settings > Integrations.

Revoking a key: Find the key in the list, click the delete icon, and confirm. The key stops working immediately.

Enabling/disabling a key: Toggle the switch on the key. Disabled keys return 401 Unauthorized. Re-enable anytime without generating a new key.

Rotating keys: Generate a new key, update your integration to use it, then revoke the old one. You can have multiple active keys at once, so there’s no downtime during rotation.

Good to Know

Create-only — The API creates trips. Update and delete support is planned for a future release. Use the AirPlx UI for those operations today.
No rate limits — Send as many trips as you need, as often as you need.
Testing — Use a staging environment if one is available for your FBO. Contact AirPlx support to discuss testing options.

Troubleshooting

Getting 401 Unauthorized — Check that your key starts with ak_ and the full header is Authorization: Bearer ak_.... Verify the key is enabled in Settings > Integrations. Use GET /api/v1/auth/verify to test credentials in isolation.

Trips not appearing on schedule — Check the API response for quarantined or failed statuses. Trips with unrecognized tail numbers go to Operations > Inbox for review. Also confirm you’re looking at the correct FBO’s schedule (keys are scoped to one FBO).

Times are wrong — The API does not convert timezones. Send UTC, not local time. If your arrival is 10:00 AM US Eastern (UTC-5), send 15:00:00Z. Timestamps must end with Z.