Skip to main content

Corti API - Enterprise Ordering Process

Updated over a week ago

We are proud of our ability to support individual users as well as enterprise deployments. We understand that with enterprise deployments, the need to be able to scale services to support international user bases is incredibly important. We are able to accomplish this in a lightweight way by using regular strategy meetings to proactively anticipate coming scale. We also employ real time monitoring of account activities so we know when that scale we're anticipating will hit.


1️⃣ Monthly Forecasting Session

To support your onboarding plans and ensure high availability of services without unnecessary overhead, we schedule a monthly forecasting session with your team.

👉 Purpose of the session:
The forecasting session allows us to align on your deployment roadmap and proactively plan for scaling needs. This helps ensure the right services are ready at the right time—without the need to run infrastructure at maximum capacity continuously, reducing cost for both you and us.

👉 What we review together:
During each session, we’ll cover:

  • Number of clinics to be onboarded in the upcoming period

  • Number of users/providers expected to use the system

  • Language breakdown of the users being onboarded (e.g., English, German, Danish, etc.)

  • Any additional features or modules that will be activated as part of the onboarding

👉 Outcome of the session:
This forecasting enables us to:

  • Anticipate service scale-up requirements (e.g., ASR model capacity, language models, features)

  • Schedule internal readiness activities, including QA and capacity testing

  • Coordinate support resources for upcoming go-lives

⚠️ It is important that this session is attended by representatives who can speak to your onboarding plans at a detailed level.


2️⃣ API Key Generation

To ensure data segregation between the healthcare organizations you support, you will likely be generating a new API key for each organization you onboard.

👉 How it works:

  • Your team will create a new API key for each organization using our API console.

  • When a new API key is generated:

    • Our team will receive an automatic notification of the new key.

    • We’ll collect relevant information, including:

      • Organization name

      • Anticipated go-live date

      • Additional features enabled for this key

👉 Why this is important:

  • Each API key ensures that the data from one healthcare organization remains logically and technically isolated from others.

  • We can prepare hypercare support during go-live for that specific organization.

  • We can maintain accurate records of active integrations for monitoring and compliance.

👉 What you need to do:

Did this answer your question?