outatime Developer Docs
outatime is a digital legacy management platform. When a user's death is confirmed, the platform triggers pre-configured actions — delivering messages, documents, or notifications through external services you provide.
This documentation is for integration developers building and managing those external actions.
What you'll find here
| Section | What it covers |
|---|---|
| Getting Started | Account setup, first action, testing with simulation |
| Concepts | How actions, executors, and teams work |
| Executor Reference | Per-executor configuration and authentication |
| Guides | Step-by-step task walkthroughs |
| API Reference | Full interactive API spec |
Quick orientation
An action is a configured instruction: "when this user's death is confirmed, send a POST request to this webhook". Actions are owned by teams — groups of integration developers — and executed by the platform on the user's behalf.
Each action has an execution type that determines how the platform delivers the payload. There are eleven external executor types across three delivery models — synchronous (http, lambda, google_cloud_function, azure_function), fire-and-forget (sqs, sns, google_pubsub, azure_service_bus), and callback (sqs_callback, google_pubsub_callback, azure_service_bus_callback).
Before any live dispatch causes real effects, you can test your integration in simulation mode. With per-action simulation enabled, the platform dispatches a real request to your endpoint with "simulate": true in the payload — your endpoint receives the call and skips real effects. With global simulation active, dispatch is suppressed entirely by the platform.