# JetsLab API Docs

> Public integration docs for JetsLab delivery, logistics, marketplace, merchant, and checkout flows.

## Primary docs
- HTML docs: https://jetslab.co/apis
- Markdown integration guide: https://jetslab.co/apis/integration-guide.md
- Root llms.txt alias: https://jetslab.co/llms.txt

## API base
- REST API: https://api.jetslab.co/api/v1

## Authentication
- Merchant server integrations: `X-API-Key: <merchant_api_key>`
- End-user session flows: `Authorization: Bearer <access_token>`
- Merchant delivery confirmation: `X-API-Key` plus `X-Merchant-Secret`

## Recommended integration flow
- Register or onboard a merchant account.
- Store the merchant API key securely on your server.
- Create orders with the unified endpoint and send `X-Idempotency-Key` on retries.
- Track order progress with `GET /orders/my-orders/` or merchant webhooks.
- Mark delivery as received once fulfillment is complete.

## Core endpoints
- POST https://api.jetslab.co/api/v1/orders/orders/unified-create/
- POST https://api.jetslab.co/api/v1/orders/api_deliveries/merchant_create_order
- GET https://api.jetslab.co/api/v1/orders/my-orders/
- POST https://api.jetslab.co/api/v1/orders/order/mark-as-received
- POST https://api.jetslab.co/api/v1/merchant/register/
- POST https://api.jetslab.co/api/v1/merchant/register-webhook/

## Operational notes
- The docs are public and do not require login.
- Endpoint authentication is route-specific; read the endpoint notes before integrating.
- Do not hardcode a buyer payment method in checkout UIs. Let the buyer choose MTN or Airtel explicitly.
- Multi-merchant checkout uses a single buyer escrow with staged disbursement and partial failure handling.