Skip to main content
An outbound action is Olira pushing a notification to a system you own the moment something happens — a patient’s data updated, a log arrived that changed nothing, a mapping error, or an ingestion job finished — instead of you polling the API for changes. You register a destination, subscribe it to the triggers you care about, and Olira records every send in a delivery ledger you can inspect and resend from. That is the same model in the Olira Console and in the SDK: what you create in one, you can read and manage in the other.
SDK calls require an API key with the sdk:actions scope. In the Console, destinations and delivery history live under Outbound actions for the project you have selected.

​
How it works

Today you can send to a webhook or an email. More destination types will follow; they will show up in the same Console picker and the same SDK create call. Triggers, signing secrets, and the delivery ledger do not change.

​
Key concepts

These words are the ones you will see in the Console, the SDK, and these docs.

​
Next steps

Destinations

Webhook and email destinations, which triggers to subscribe, and when to batch.

Receiving deliveries

The payload envelope, signature verification, retries, and the delivery ledger.

SDK reference

Create, update, rotate, list, and redeliver from Python or C#.

Authentication

Create an API key and add the sdk:actions scope.