Contentio API

Quickstart

From nothing to your first API call in four requests.

1. 1Register your app

   Register once with dynamic client registration (RFC 7591). Public clients use PKCE and no secret.

   TerminalCopy

   curl -X POST https://contentio.io/oauth/register \
     -H "Content-Type: application/json" \
     -d '{
       "client_name": "My app",
       "redirect_uris": ["https://myapp.example/callback"],
       "token_endpoint_auth_method": "none",
       "grant_types": ["authorization_code", "refresh_token"],
       "response_types": ["code"]
     }'

2. 2Send the user to sign in

   Open the authorize URL with a PKCE S256 challenge. The user signs in to Contentio and approves your app.

   URLCopy

   https://contentio.io/oauth/authorize
     ?response_type=code
     &client_id=CLIENT_ID
     &redirect_uri=https://myapp.example/callback
     &code_challenge=CHALLENGE
     &code_challenge_method=S256
     &scope=email%20offline_access
     &state=STATE

3. 3Exchange the code for tokens

   Your redirect URI receives code and state query parameters. Exchange the code using the PKCE verifier.

   TerminalCopy

   curl -X POST https://contentio.io/oauth/token \
     -d grant_type=authorization_code -d code=CODE \
     -d redirect_uri=https://myapp.example/callback \
     -d client_id=CLIENT_ID -d code_verifier=VERIFIER

4. 4Call an operation

   Every operation is a POST with a JSON body, acting as the signed-in user.

   TerminalCopy

   curl -X POST https://contentio.io/api/v1/list_scheduled \
     -H "Authorization: Bearer ACCESS_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{}'

Operations

Every operation is POST https://contentio.io/api/v1/{operation}. Full request and response schemas are in the OpenAPI spec.