Nest Engineering Docs
Interface

Interfaces

Inbound and outbound contracts for Interface

Authentication

  • All endpoints require X-API-Key except GET /api/v1/health and docs assets.
  • Keys are loaded from Secret Manager (INTERFACE_API_KEY) at startup.
  • Missing or invalid keys return 401 Unauthorized.

Base paths

  • v1: /api/v1
  • v2: /api/v2

Endpoint catalog

Most endpoints are POST /search with JSON filters and pagination (limit, offset). Deprecated routes are marked in the table.

VersionResourceOperationsNotes
v1/healthGETHealth check (no auth)
v1/instancesPOST /searchRead-only
v1/organizationsPOST /searchRead-only
v1/clinicsPOST /searchRead-only
v1/householdsPOST /searchRead-only
v1/contactsPOST /searchRead-only
v1/patientsPOST /search, POST /syncsync provides best-match lookup
v1/team-membersPOST /searchRead-only
v1/appointmentsPOST /searchDeprecated (use v2)
v1/invoice-linesPOST /search, POST /countDeprecated (use v2 invoices)
v1/invoicesPOST /search, POST /countDeprecated (use v2)
v1/migration-memberPOST /searchRead-only
v1/reportsPOST /fiscalRead-only
v1/productsPOST /searchRead-only
v1/appointment-typesPOST /search, POST /updateupdate writes is_wellness
v1/appointment-statusesPOST /search, POST /updateupdate writes status
v2/appointmentsPOST /search, POST /countPreferred for appointments
v2/invoicesPOST /searchPreferred for invoices

Response envelopes

  • v1 endpoints generally return lists of models.
  • v2 endpoints return a Response envelope with metadata and data payloads.

Outbound dependencies

  • Cloud Spanner for all reads and limited writes.
  • Secret Manager for API keys and optional Sentry DSN.

Last updated on