The Trailflow Partner API contract is available through the API reference tab in this portal and is surfaced from the canonical OpenAPI 3.1 specification. This page exists to clarify how the contract should be consumed. The OpenAPI document is the source of truth for endpoint definitions, but it is most useful when read alongside the integration guides, examples, authentication rules, versioning notes, and webhook behavior documented in this portal. Use the API reference for:Documentation Index
Fetch the complete documentation index at: https://trailflow.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
- endpoint paths and methods
- request and response schemas
- parameter definitions
- status codes and error envelopes
- authentication and idempotency rules
- polling and pagination behavior
- webhook signing and retries
- representative example payloads
Recommended reading order
- Start with the API reference when you need exact schemas and field names.
- Use the guides when you need to understand workflow behavior, retries, pagination, signing, and implementation expectations.
- Use the examples page to compare representative request and response bodies before automating an integration or handing the work to an agent.