Skip to main content

​
What Trailflow shares with approved partners

  • the hosted Mintlify docs URL
  • the authenticated partner portal URL
  • org-specific onboarding contacts provided during onboarding
  • the public status page: https://status.trailflow.ai

​
Share with partner

​
Access approval flow

  1. Confirm the customer organization and partner contact list.
  2. Enable partner test access for the customer organization.
  3. Invite approved partner users into the org with a partner portal role.
  4. Issue the first test key during onboarding or let an approved partner admin create it from the authenticated partner portal after test access is enabled.
  5. Confirm rate limit, polling expectations, webhook signature verification, and the partner’s UAT plan.
  6. Enable live access only after Trailflow approves production cutover.
  7. Issue live keys only when the integration is ready for production traffic.

​
Environment guidance

  • Test mode: same Trailflow host and same contract shape as production, but scoped test credentials, orgs approved for partner testing, and partner-side non-production webhook endpoints.
  • Live mode: approved production credentials for real traffic.
  • Sandbox: Trailflow does not currently provide a separate public sandbox host. Partners should plan around test-mode keys instead.

​
Onboarding email contents

  1. Confirm the customer org, technical contacts, and support contacts.
  2. Send the Mintlify docs URL, the authenticated partner portal URL, and the OpenAPI contract plus core guides.
  3. Confirm whether Trailflow will issue the first test key or whether the approved partner admin should create it in the authenticated partner portal.
  4. Confirm request limits, idempotency behavior, webhook retry expectations, and secure secret storage.
  5. Confirm UAT window, support hours, cutover criteria, and escalation path.
  6. Schedule live-access approval only after the partner validates the integration.

​
Support expectations

  • Trailflow monitors authentication failures, rate limits, server errors, and webhook delivery failures for approved partner integrations.
  • Webhook replay is coordinated with Trailflow support after the partner confirms remediation.
  • Contract changes are additive by default. Any non-additive change requires direct partner review.