mocop
Browse · Docs · Guide · Analyze

Genkō REST API

API by Getgenko · rest

The Genkō REST API for ERP/EHR integrations. Everything here is under /api/v1. Authentication Send a REST API key in the header: Authorization: Bearer genko_…. Keys are created in Settings → Developers → REST API keys, belong to one organization, and carry granular scopes (listed below), an optional IP allowlist and an optional per-key rate limit. A key in the URL is refused. MCP keys (genko_mcp_…) do not work here. Plans: reading needs Group or above, writing Practice, and clinical data, patient deletion, batches and webhooks Network. The plan is checked on every request, so a downgrade takes effect at once. Envelope Every response is { "data": …, "error": null | { "message", "code", "details"? }, "meta": { "request_id", … } } with Cache-Control: no-store and an X-Request-Id. Branch on error.code, never on message. Codes are never renamed. Pagination Keyset only. Follow meta.next_cursor while meta.has_more is true. Default page 100,…

Endpoint: https://www.getgenko.com/api/v1

Verification: observed. Source: crawl.

Capabilities (44)

  • Who am I what may I do and how fast
  • List appointments
  • Book an appointment
  • Upsert up to 500 appointments
  • Get an appointment
  • Change status or reschedule
  • Cancel an appointment
  • Get the intake form for an appointment
  • Approve or reject a submitted intake form
  • List an appointment's clinical notes
  • Add a draft clinical note
  • Get a clinical note
  • Edit a draft clinical note
  • Discard a draft clinical note
  • Add a draft addendum to a signed note
  • Mint a calendar-embed session token
  • List patients
  • Create a patient
  • Upsert up to 500 patients
  • Create or update a patient by external_id
  • Get a patient
  • Update a patient
  • Delete or archive a patient
  • List a patient's documents
  • Get a document with a download URL
About · Contact · Privacy