OrgRelay developer documentation
Everything a developer needs to make a business system usable by OrgRelay's AI: the contract, the two transports, how authentication and approvals work, and a tool that proves your connector is correct before anyone binds it.
Who these docs are for
You are probably one of three people. The customer's own IT team, connecting an in-house ERP or warehouse system. An outsourced developer who has been handed the developer kit and a deadline. Or a system integrator who installs OrgRelay for several clients and wants one way to connect the same platform each time. The docs are the same for all three; the quickstart is the shortest path for each.
If you are deciding whether a company should use OrgRelay at all, read what OrgRelay does on orgrelay.com first. These pages assume that decision is made.
The pieces
| You want to | Read |
|---|---|
| Get a working connector in 15 minutes | Quickstart |
| Know exactly what OrgRelay expects | Connector spec and standard tool names |
| Pick between MCP and plain REST | MCP transport, REST compatible mode |
| Avoid writing code for an existing API | OpenAPI import, GraphQL import, third-party MCP |
| Handle tokens, OAuth and rotation | Authentication |
| Implement write tools safely | Approvals and write tools |
| Push new orders or low-stock alerts | Events |
| Pass a security review | Security requirements |
| Prove it works | Self-test tool |
| Start from code | Templates in four languages |
| Package company know-how for the AI | Agent Skills |
How OrgRelay treats your system
OrgRelay does not ship with any system built in. When an owner binds a connection, OrgRelay reads your manifest and learns the name, logo and tools from you. Nothing appears in the interface until it is bound.
Three rules shape everything else in these docs:
- Tools are either read or write. A read tool is called directly. A write tool is never called until a person approves the request. The rules are on approvals and write tools.
- One token is one company. Your connector decides the tenant from the token and never from a field in the request. The self-test checks this with two tokens. See security.
- Permissions are enforced before the call. If a staff member's role is not allowed to use your connector, OrgRelay does not send the request at all. You still check permissions on your side.
Platforms that already have a connector
For common platforms such as Shopify, Odoo, QuickBooks Online, HubSpot or Kingdee, the work is already done. The connector directory shows which tools each one exposes and which credentials it needs. When a platform is missing, the fastest route is usually OpenAPI import.
The other direction: OrgRelay as an MCP server
These docs cover OrgRelay calling your system. Staff can also call OrgRelay from their own AI client. That is the MCP guide: Claude Code, Claude Desktop, Codex and Cursor.
Versions
The current spec is orgrelay-connector/1, document version 1.1.0 (9 November 2026). Within major version 1 only backward-compatible changes are made. What changed and when is on the changelog.