Fitnescity Health Developers
Public API documentation

Use Full API Integration—the default approach—to keep diagnostic testing search, customer identity, consent when required, ordering, questionnaires, scheduling, and results in your product. Start in Staging (Sandbox) for API Partner testing before switching hosts and credentials for live traffic.

Default test host
https://api-staging.engineeringfitnescity.com
Request access
Go-Live

Production launch checklist for Fitnescity Health Public API integrations.

Use this checklist to reduce avoidable production issues before you switch from Staging (Sandbox) to the live production host.

Launch checklist

  1. 1. Staging integration is complete for search, offering-product resolution, availability preview, direct order creation, and scheduling.
  2. 2. Environment-specific configuration is separated cleanly: staging host/key vs production host/key.
  3. 3. Direct-order integrations persist order_id, order_ref, external payment reference, and Idempotency-Key.
  4. 4. Full API scheduling sends a primary appointment preference and one to three alternate availabilities.
  5. 5. Request ids from API errors are captured in your logs for support escalation.
  6. 6. Result polling is implemented if your workflow depends on post-appointment data.
  7. 7. Retry behavior is bounded and respects the documented Retry-After, 409, 429, and 5xx semantics for each route.

Recommended production cutover

  • Deploy production host and credentials behind a feature flag or environment toggle in your own system.
  • Switch a small initial traffic slice or API Partner cohort first.
  • Watch 401, 403, 409, 429, and 5xx rates closely during the first hours of live traffic.

Runbook expectations

  • Keep a fast path for rotating production keys if an integration secret is exposed or rolled unexpectedly.
  • Make sure support teams can search by email, order_id, appointment_id, and request_id when debugging live issues.
  • Treat base URL changes and credential changes as separate release steps so rollbacks stay simple.