Natzar Partner API Reference - v1.0.0
    Preparing search index...

    Type Alias ConsultOrigin

    ConsultOrigin: "partner" | "platform"

    Who opened a consult.

    • partner — you did, through this API.
    • platform — OUR agent did, mid-conversation, because the patient asked for a clinician or the assistant judged one was warranted. You will see these on your own patients: the agent conversation and the consult lifecycle are one product, and a consult the patient started by asking is still their consult.

    The distinction is about PROVENANCE, not permission. Everything a patient can do — consent, rate, join, read the transcript — works on both. What origin gates is the scope of a call made with the TENANT KEY ALONE: the management operations (claim, takeover, resolve, replies, close) and the default of the list filters are partner-origin only, because an application credential reassigning a thread our own clinicians are working would leave the patient with a physician nobody told.

    A PHYSICIAN credential (see ./endpoints, "Acting as a physician") is scoped to the whole tenant instead — every consult of the clinic, whichever surface opened it — since that physician IS one of the clinicians the platform routes to. Their list reads default to origin=any.