Skip to main content

​
Overview

Stenoa’s API allows external systems to trigger workflows inside Stenoa using inbound REST APIs. Hospitals, integration engines, and third-party platforms can send structured event payloads to initiate consults, update active Cases, or route information to on-call teams. This lets you build integrations on top of Stenoa. Use our API when you need Stenoa to respond automatically to system-level actions, such as a new referral, ECG result, patient movement update, or device alert.

​
Base URL

The Stenoa API is built on REST principles. We enforce HTTPS in every request to improve data security, integrity, and privacy. The API does not support HTTP. All requests contain the following base URL:

​
Authentication

To authenticate you need to add an Authorization header with the contents of the header being Bearer re_xxxxxxxxx where re_xxxxxxxxx is your API Key.

​
Response codes

Stenoa uses standard HTTP codes to indicate the success or failure of your requests. In general, 2xx HTTP codes correspond to success, 4xx codes are for user-related failures, and 5xx codes are for infrastructure issues.

​
Rate limit

The default maximum rate limit is 2 requests per second. This number can be increased for trusted senders by request. After that, you’ll hit the rate limit and receive a 429 response error code. To configure your event sources via our inbound APIs, contact Support.