Developers
Build connections to Ordering.co products, or work in their product repositories. Each product has two documentation tracks with different audiences and boundaries.
Choose a documentation track
| Track | Use it when | What it covers |
|---|---|---|
| Integrations | You are connecting a product, provider, route, notification, payment, or handoff. | Public inputs, visible results, availability, ownership boundaries, and safe failure behavior. |
| Engineering | You are contributing to an Ordering.co product repository. | Architecture, repository map, local setup, configuration, validation, build boundaries, and troubleshooting. |
Integration guides do not expose private implementation details or replace server contracts. Engineering guides describe the checked-in repositories; they do not grant access to credentials, customer environments, release systems, or deployment approval.
Products
| Product | Integrations | Engineering |
|---|---|---|
| Website | Website developer reference | Website engineering guide |
| Customer App | Customer App developer reference | Customer App engineering guide |
| Business App | Business App developer reference | Business App engineering guide |
| Driver App | Driver App developer reference | Driver App engineering guide |
| Dashboard | Dashboard developer reference | Dashboard engineering guide |
| AI Dashboard | AI Dashboard developer reference | AI Dashboard engineering guide |
Connect an AI assistant with MCP
Follow MCP setup to sign in and install detected clients with the developer quickstart, or configure Claude Code or Codex manually. The guide covers project URLs, read/write scopes, key replacement, and the supported API catalog. MCP keys are separate from API keys.
API contracts
Start with the REST API v400 quickstart for authentication, latest orders, pagination, and the distinction between API keys and MCP scopes.
Use the canonical API Reference for requests, schemas, and authentication. Product integration guides explain routes and cross-product handoffs without duplicating endpoint documentation. Before enabling interactive requests, read Safe API Reference testing.
For the standard session entry point, start with the public
POST /auth contract.