Full API Integration
Build identity, consent, ordering, questionnaires, scheduling requests, appointment tracking, communications, and results into one native, API Partner-owned experience.
Build on Fitnescity Health
Embed nationwide diagnostic testing into your product across 1,000+ test centers — go live in 1–2 weeks.
Use Full API Integration as the primary path to keep location search, product discovery, identity, consent, ordering, questionnaires, scheduling requests, appointment tracking, communications, and results in your product. Use this overview to understand the platform, then open the detailed guide when you are ready to implement each request against the same diagnostic-grade network trusted by major hospitals, imaging centers, and healthcare platforms.
At a glance
Full API Integration is the primary documentation flow. Your application owns every customer-facing step and uses Fitnescity Health APIs from discovery through scheduling, communications, and results.
Discovery
Locations, tests, and availability
Customer identity
Reusable customer identity
Customer consent
Collected via API or supplied as PDF evidence, as provisioned
Orders and questionnaires
Order creation and questionnaire submission
Scheduling and tracking
Appointment request, confirmation, physician-order document, and results
What API Partners build
Search and merchandising
Search locations by geo coordinates, inspect catalog and offering pairs, and surface single-test products and availability on your own PDP and booking surfaces.
Identity, consent, and orders
Create reusable customer identities, establish test-specific consent, and create orders after payment is handled through your own checkout, before submitting questionnaires and requesting an appointment.
Scheduling requests
Send a primary appointment preference and one to three alternate availabilities, then track the request-then-confirm lifecycle through appointment reads and webhooks.
Results retrieval
Poll results scoped to your own members with allowlisted payloads and auditable order / appointment identifiers.
Operational readiness
Separate staging and production keys, route-aware throttling, request ids, and a clear go-live checklist for API Partner teams.
Environments
Use staging for implementation and API Partner testing. Switch the host and credentials only when you are ready to send live traffic.
Examples use Staging (Sandbox)
Staging (Sandbox)
Default referencehttps://api-staging.engineeringfitnescity.com
Use this shared non-production environment for implementation, QA, and API Partner testing before go-live.
Credentials
Use a staging-only API key. Staging keys do not work in production.
- Shared environment used for API Partner testing and Fitnescity Health validation.
- No production data should be used in staging.
- Behavior matches the current v1 contract, but releases may arrive here before production.
Production
https://public-api.fitnescity.com/
Use this environment for live member traffic after your integration is ready to launch.
Credentials
Use a production API key issued separately from staging credentials.
- Live environment for member traffic and results retrieval.
- Switch to production only after validating your integration in staging.
- Keep environment-specific secrets and API hosts separate in your deployment config.
Documentation map
Start with this overview, open the Full API Integration guide for the complete native sequence, and then use the route-by-route reference once your implementation model is clear.
Getting Started
Access, auth, rate limits, support, and staging usage.
Full API Integration
Native identity, consent, order, questionnaire, scheduling, communications, and tracking flow.
Error Handling
Common statuses, retry rules, envelopes, and request tracing.
Concepts
Core objects and relationship model.
Results
Polling model, allowlisted payloads, and PHI handling notes.
Webhooks
Appointment lifecycle events, signing, and delivery model.
Communications
Appointment emails and text/SMS notifications with API Partner branding.
Go-Live
Readiness checklist for production launch.
API Reference
Endpoint contracts, cURL examples, and payloads.