Customer API

The Customer API provides a simple, reliable interface for retrieving KongAir customer data — profiles, contact details, payment methods, and frequent flyer numbers — from a single authenticated endpoint.

Version: 0.1.0 · Spec: OAS 3.1 · Base URL: https://api.kong-air.com


What You Can Do

Retrieve Customer Profiles Access a customer's full profile including their unique ID, username, display name, and contact information in a single call.

Access Payment Methods Fetch saved payment methods — card type, last four digits, and expiry date — for billing and checkout flows.

Read Frequent Flyer Data Pull frequent flyer numbers and tier status to power loyalty-driven features and personalized experiences.


Quick Start

All requests to /customer require a bearer token in the Authorization header.

Fetch a Customer

curl -X GET https://api.kong-air.com/customer \
  -H "Authorization: Bearer <your_token>" \
  -H "Accept: application/json"

Example Response

{
  "id": "cust-9876543210",
  "username": "johndoe",
  "name": "John Doe",
  "information": {
    "email": "johndoe@example.com",
    "phone": "+1-555-000-1234",
    "frequent_flyer_number": "FF-00123456",
    "payment_methods": [
      {
        "type": "visa",
        "last_four": "4242",
        "expiry": "09/27"
      }
    ]
  }
}

Health Check

The /health endpoint is unauthenticated and Kubernetes-compatible.

curl https://api.kong-air.com/health
# { "status": "OK" }

Endpoints

MethodPathDescription
GET/customerFetch full customer profile, payment methods, and loyalty data
GET/healthKubernetes liveness check — returns { "status": "OK" }

Reference

DetailValue
Base URLhttps://api.kong-air.com
Version0.1.0
Spec FormatOAS 3.1
AuthenticationBearer Token
Supportsupport@kongair.dev

Authentication note: All /customer requests must include a valid Authorization: Bearer <token> header. The /health endpoint is open and requires no credentials.