Skip to main content

Endpoint

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:
Required scope: workflows:read

Path Parameters

Request Example

Response

Success Response

Status Code: 200 OK

Response Fields

Workflow Schema Object

Variable Object Fields

Error Responses

400 Bad Request

Returned when the version format is invalid, or when the access token has no user behind it. client_credentials tokens act as the admin who created the application, so this applies only to tokens issued before application creators were recorded.

401 Unauthorized

Returned when the access token is missing, unknown, revoked, or expired, or when an X-API-Key was sent instead of a bearer token. See OAuth error responses.

403 Forbidden

Returned when the token lacks the required scope:
Or when the user may not access this workflow:

404 Not Found

Returned when the workflow or version does not exist.

429 Too Many Requests

Returned when your organization exceeds its per-minute request limit.

500 Internal Server Error

Returned when the request fails due to a server error.

Notes

Use "latest" as the version to always get the most recent workflow schema without tracking version numbers.
The schema is fetched as the access token’s user. A workflow the user cannot reach returns 403 rather than a schema.
Variable types and validation rules must be respected when initiating workflows. Validation failures result in a 422 error.

Use Cases

This endpoint is useful for:
  • Form generation - Dynamically create input forms based on workflow variables
  • Validation - Validate user input before initiating workflows
  • Documentation - Display workflow requirements to users
  • Integration planning - Understand what data is needed to start a workflow