Introduction

Outis is an approval gate. Your service asks for something to happen, the people who hold the keys turn them on a physical box, and you read the answer. Outis never runs the thing itself.

What an integration does

1. Creates a request with POST /v1/requests, naming an action and what the operators should see on the panel.
2. Waits while each eligible operator gets an arming code, types it into their box and turns the key. Policy on the server decides how many keys and inside what window.
3. Reads the decision, by polling GET /v1/requests/{id} or by receiving a signed callback, and acts on authorized.

Your service never sees an arming code and never learns who holds which key.

What you need

• An Outis organization with at least one operator who has claimed a box. Sign up and generate keys from the dashboard.
• An API key with the propose and read scopes.
• One of the SDKs, or curl.

Quickstart Generate a key, create a request and read the decision.

How approval works Quorum, windows, self approval and what the box shows.

API reference Every endpoint, field, error and limit.

Integrations GitHub, Slack, and how to build your own.