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
Communications

Appointment-related emails and text/SMS notifications carry API Partner branding alongside Fitnescity Health.

Members who schedule through an API Partner integration receive co-branded emails throughout the appointment lifecycle, and certain workflows can also send text/SMS notifications. API Partner branding appears alongside Fitnescity Health branding so the member experience feels connected to the API Partner app they started from.

This communication model applies to Full API Integration as well as other API Partner workflows.

API Partner-managed communications

For communications-enabled and communications-paused integrations alike, API Partners may place the appointment check-in link in their own customer email or text/SMS. This view-only page is separate from Fitnescity Health-managed notifications and shows the customer, appointment time, test, facility/location, and appointment ID.

appointment confirmed
-> GET /v1/appointments/{appointmentId}/check-in-link
-> place returned opaque URL in API Partner-owned email/SMS
-> request again after any reschedule

Request the endpoint server-side with read:appointments. The URL expires six hours after appointment start, not six hours after the request. Treat it as opaque: do not log, parse, decorate, or expose it to analytics. It is not included in normal appointment payloads or webhooks, and cancellation, refund, no-show, or rescheduling invalidates it; request a fresh link after a reschedule.

Text/SMS notifications

In addition to email, Fitnescity Health may send text/SMS notifications for appointment confirmations, reminders, rescheduling updates, and cancellations when the workflow supports it. API Partners should treat those messages as part of the member communication model, not as a separate opt-in channel.

Email categories

Broadly, these are the categories of appointment-related emails that will carry API Partner branding for members who entered through an API Partner flow.

Booking confirmation

Sent to the member after an appointment is successfully scheduled.

Appointment reminders

Sent ahead of the scheduled appointment to reduce no-shows.

Rescheduling notices

Sent when an appointment is rescheduled by the test location or Fitnescity Health ops.

Cancellation notices

Sent when an appointment is cancelled.

Results availability

Sent when test results are ready for the member to review.

Sender policy and safety

  • From / Reply-To
    Both remain Fitnescity Health-owned sender identities for deliverability and DMARC alignment. API Partner branding is visual only.
  • Branding payload
    Logo, colors, and display name are validated and escaped before template rendering. Invalid branding falls back to standard Fitnescity Health templates.
  • Delayed notifications
    Reminder jobs re-check the current API Partner branding settings at send time so stale disabled branding is not rendered.