API Quickstart - drio Docs

The fastest path for engineering teams automating drio through the 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: create an app, inspect its configuration, and publish it.

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 now means:

register a client with /api/v1/auth/register
send users through /api/v1/auth/authorize
exchange the returned drio code at /api/v1/auth/token

Keep the same client_id and registered redirect_uri across the flow.

The Shortest Useful Flow

Most integrations start with these four steps:

list templates
create an app from a template
inspect the app config
publish the app

1. List Templates

Templates are public, so you can browse them before authenticating.

curl https://getdrio.com/api/v1/templates

This returns the template catalog, including IDs such as support.

2. Create An App

Use a bearer token to create an app from a template.

curl -X POST https://getdrio.com/api/v1/apps \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "templateId": "support",
    "name": "Acme Support",
    "slug": "acme-support",
    "companyUrl": "https://acme.com"
  }'

The response returns the app record, including its id.

3. Inspect The App Config

Fetch the current authoring snapshot for the app.

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

Use this when you need the full builder state behind an app, not just summary metadata.

4. Publish The App

Publishing is done through the commands endpoint.

curl -X POST https://getdrio.com/api/v1/apps/app_123/commands \
  -H "Authorization: Bearer ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "publish_app"
  }'

The response returns the updated app record. A deployed app reports "status": "deployed".

When To Use The API

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

automate app creation from another internal system
standardize publishing flows across multiple apps
inspect app state and configs in external tooling
support a technical due diligence or operations workflow