Authenticate and create a delivery match via the Frayt API
domain: frayt.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Email integrations@frayt.com (or api@frayt.com) to request an API key and sandbox credentials — Frayt does not offer self-serve API signup.
Exchange your client ID and secret for a bearer token via the OAuth endpoint /api/v2.2/oauth/token.
Pass the returned token as a Bearer credential in the Authorization header on subsequent requests.
Create a "Match" (Frayt's term for an order/delivery) against the relevant endpoint group for your use case (quoting, booking, or tracking) — the v2.2 API is organized around four distinct endpoint groups.
Schedule a live test session with Frayt via email before flipping the integration to production.
Once testing passes, request that Frayt turn on the production integration for your account.
Known gotchas
There is no public self-serve API key generation — every integration starts with an email handshake and a scheduled test session, so plan onboarding lead time.
Frayt's core resource is called a "Match," not an "order" or "delivery," in the API's own vocabulary — searching the docs for "order" endpoints will come up short.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?