API Quickstart - drio Docs

The fastest path for engineering teams automating drio through the supported v3 management API.

This page is for developers and technical reviewers. Use the API when you want to automate the same lifecycle that happens in the dashboard: inspect an app, turn discovered operations into tools, validate the draft, and publish a release.

Before You Start

You need:

a drio account
an OAuth access token for protected routes
a clear reason to automate instead of using the dashboard directly

If you do not have a token yet, start with Authentication. The auth flow means:

discover the authorization server from drio
register a client with the advertised AuthKit issuer
authorize with PKCE against AuthKit
exchange the returned code at AuthKit's token endpoint

Keep the same client_id and registered redirect_uri across the flow.

The Shortest Useful Flow

Most integrations start with these four steps:

find the app you want to automate
inspect compact authoring state
import or create operation-backed tools
validate and publish a release

1. Find An App

Use a bearer token to list apps you can manage.

curl https://getdrio.com/api/v3/apps \
  -H "Authorization: Bearer ACCESS_TOKEN"

The response returns app summaries. Use the app id in the remaining calls.

2. Inspect Authoring State

Fetch the app summary when you need release endpoint metadata.

curl https://getdrio.com/api/v3/apps/app_123 \
  -H "Authorization: Bearer ACCESS_TOKEN"

Fetch compact authoring state when you need the draft's integrations, operations, tools, and validation status in one response.

curl https://getdrio.com/api/v3/apps/app_123/authoring-state \
  -H "Authorization: Bearer ACCESS_TOKEN"

3. Create A Tool From An Operation

List operations for the integration you want to expose.

curl https://getdrio.com/api/v3/apps/app_123/integrations/integration_123/operations \
  -H "Authorization: Bearer ACCESS_TOKEN"

Import one or more operations as runtime-backed MCP tools.

curl -X POST https://getdrio.com/api/v3/apps/app_123/integrations/integration_123/operations/import-tools \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "operation_ids": ["operation_123"],
    "place_on_canvas": true
  }'

You can also create a single named tool from an operation:

curl -X POST https://getdrio.com/api/v3/apps/app_123/tools \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Search issues",
    "description": "Search issue records in the connected tracker.",
    "source": {
      "type": "integration_operation",
      "integration_id": "integration_123",
      "operation_id": "operation_123"
    },
    "annotations": {
      "read_only_hint": true
    }
  }'

v3 does not accept low-level binding writes. Tool creation derives the internal runtime records and returns a runtime_status so you can see whether the tool will be exposed.

4. Validate And Publish

Validate before publishing:

curl -X POST https://getdrio.com/api/v3/apps/app_123/draft/validate \
  -H "Authorization: Bearer ACCESS_TOKEN"

Publishing creates a new immutable release from the current draft and rotates the app to a fresh successor draft.

curl -X POST https://getdrio.com/api/v3/apps/app_123/releases \
  -H "Authorization: Bearer ACCESS_TOKEN"

The response returns the new published release.

When To Use The API

The API is a good fit when your team wants to:

automate operation-to-tool publishing from another internal system
standardize release workflows across multiple apps
inspect current authoring state in external tooling
support a technical due diligence or operations workflow

latest docs describe v3
archived v1 docs remain available for migration reference only