---
title: "Developers"
description: "Integrate with Ordering.co products or contribute safely to their product repositories."
canonical: https://docs.ordering.co/docs/developers/
---

# 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](https://docs.ordering.co/docs/developers/website/)           | [Website engineering guide](https://docs.ordering.co/docs/developers/website/engineering-guide/)           |
| Customer App | [Customer App developer reference](https://docs.ordering.co/docs/developers/customer-app/) | [Customer App engineering guide](https://docs.ordering.co/docs/developers/customer-app/engineering-guide/) |
| Business App | [Business App developer reference](https://docs.ordering.co/docs/developers/business-app/) | [Business App engineering guide](https://docs.ordering.co/docs/developers/business-app/engineering-guide/) |
| Driver App   | [Driver App developer reference](https://docs.ordering.co/docs/developers/driver-app/)     | [Driver App engineering guide](https://docs.ordering.co/docs/developers/driver-app/engineering-guide/)     |
| Dashboard    | [Dashboard developer reference](https://docs.ordering.co/docs/developers/dashboard/)       | [Dashboard engineering guide](https://docs.ordering.co/docs/developers/dashboard/engineering-guide/)       |
| AI Dashboard | [AI Dashboard developer reference](https://docs.ordering.co/docs/developers/ai-dashboard/) | [AI Dashboard engineering guide](https://docs.ordering.co/docs/developers/ai-dashboard/engineering-guide/) |

## Connect an AI assistant with MCP

Follow [MCP setup](https://docs.ordering.co/docs/developers/mcp/) to copy one prompt, sign in through your browser, choose permissions and register detected clients with the developer quickstart, or configure Claude Code/Codex manually. Wait for the terminal result, reload your client and observe `whoami`. The guide covers project URLs, the supported catalog, optional plugin, compatibility, renewal and revocation. MCP keys are separate from API keys: MCP read does not restrict the optional REST credential.

## API contracts

Start with the [REST API v400 quickstart](https://docs.ordering.co/docs/developers/rest-api/) for authentication, latest orders, pagination, and the distinction between API keys and MCP scopes.

Use the canonical [API Reference](https://docs.ordering.co/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](https://docs.ordering.co/docs/developers/api-reference-sandbox-testing/).

For the standard session entry point, start with the public [POST `/auth` contract](https://docs.ordering.co/api-reference/#tag/auth/POST/auth).