Quickstart: connect your inventory

Coming from a traffic system, a rate desk, and a sales team? Map your systems shows where each one plugs in. Then: pick a Level, pick a direction per capability, go live. You can mix: push avails by file while we pull orders into an endpoint you host.

Path A: files and the console (Level 0)

Drop three files and a manifest to your S3 prefix (or SFTP). Rates and packages are integrity-checked and versioned on ingest; orders arrive in your approval queue. About a week from first drop to live catalog.

$ aws s3 cp catalog.csv   s3://switchboard-ingest/yourco/2026-W40/
$ aws s3 cp rates.csv     s3://switchboard-ingest/yourco/2026-W40/
$ aws s3 cp avails.csv    s3://switchboard-ingest/yourco/2026-W40/
$ aws s3 cp manifest.json s3://switchboard-ingest/yourco/2026-W40/
# manifest: schema_version, file checksums, effective window

Path B: push API (Levels 0-1)

PUT /v1/me/catalog        # packages + taxonomy versions
PUT /v1/me/rate-cards     # versioned commits; drift detection
PUT /v1/me/avails         # tri-state, batched
GET /v1/me/orders?status=seller_review
POST /v1/me/orders/{id}/decide   # approve | reject | counter, per unit

Path C: we pull from you

You host order intake and feeds; Switchboard calls you and consumes callbacks, polls, or a shared SQS queue. This is the pattern running with national partners today. Already run an order or inventory API? We call it: the endpoint contract is published at Host your own API. Declare it in your capability profile and the platform adapts.

Then climb

Level 2 adds live availability, Level 3 adds negotiation (counters on the 10-20% of units that would otherwise reject), Level 4 adds the last-minute fast lane with holds and clearance pricing. See Seller levels. Your profile declares what you support; Switchboard never calls what you have not advertised.