API

RTIE Core API reference

The canonical production API is https://api.rtie.ai. Product frontends call this same host and send X-RTIE-Product-Key where product context is required; do not use product-specific API hostnames. Start at the API index for links and auth hints, use Scalar for interactive exploration, or download the OpenAPI document for generated clients and contract tests.

Open API index Open interactive reference Download OpenAPI JSON

Entry points

GET /Public API index with health, docs, OpenAPI, auth header, and prefix links. GET /docsInteractive Scalar reference backed by the live OpenAPI contract. GET /openapi.jsonMachine-readable OpenAPI 3.1 document for SDK generation and contract checks. GET /healthUnauthenticated API health check for monitors and deployment verification.

Machine-readable contract

curl -s https://api.rtie.ai/openapi.json > rtie-openapi.json
npx openapi-typescript rtie-openapi.json -o rtie-api.d.ts

Use the OpenAPI document for SDK generation, contract validation, endpoint discovery, and integration tests.

Authenticated requests

Tenant API routes accept RTIE API keys, hosted-auth JWTs, and RTIE session tokens depending on route scope. Server-to-server integrations should prefer tenant-scoped RTIE API keys from Console, then mint short-lived runtime tokens for public users or agents.

curl https://api.rtie.ai/v1/me \
  -H "Authorization: Bearer rtie_live_..."

curl https://api.rtie.ai/v1/me \
  -H "X-API-Key: rtie_live_..."

Base URLs

Production: https://api.rtie.ai
Docs: https://docs.rtie.ai
MCP private preview: https://mcp.rtie.ai/mcp
Local API: http://localhost:8787

Core integration paths

AuthenticationAPI keys, hosted auth, BYOA adapters, session tokens, tenant scope, and error responses. Rate limitsPlan quotas, 429 handling, and retry behavior. WebhooksSigned event delivery, retries, and verification headers. MCP private previewTenant-scoped agent tool server endpoint, runtime handshake, and well-known manifest.

Endpoint families

/v1/*Tenant API keys, module runtime endpoints, module catalog, runtime connect, events, actions, payments, rooms, auctions, webhooks, analytics, and realtime sync.

/api/console/*Console-only hosted-auth routes for tenant setup, module configuration, API keys, team membership, events, and storefront configuration.

/api/public/*Public product surfaces such as brand metadata and published auction listings.

Mobile build dispatch

POST /api/console/operators/:operatorId/mobile-build queues the GitHub Actions white-label EAS workflow for an operator. It does not build inside the Worker; the Worker only sends a repository dispatch to GitHub.

curl -X POST https://api.rtie.ai/api/console/operators/{operatorId}/mobile-build \
  -H "Authorization: Bearer <supabase-jwt>" \
  -H "Content-Type: application/json" \
  -d '{"platform":"android","submitToStores":false}'

Worker secret: GITHUB_TOKEN must be set and have GitHub Contents read/write permission for repository dispatch.
GitHub secret: EXPO_TOKEN must be set so Actions can call EAS.
iOS device builds: Apple signing credentials must already exist in EAS for non-interactive CI builds.
Dev mode: if the Worker has no GITHUB_TOKEN, the response is {"queued": false, "devMode": true}.