Skip to main content
Workflows define the stages and milestones a record moves through. Use these endpoints to create and change workflows and to read their stages, milestones and the workflow history of custom component instances. This area has 15 endpoints, and all seven SDKs call every one.

At a glance

Before you call

Register your API credentials once when your app starts, as shown in Authentication. Every SDK sample on these pages then gets its client in one line. With cURL, send the access token in an Authorization header: Authorization: Bearer $ACCESS_TOKEN.

Things to know

  • Creates and updates are wrapped in workflow. One workflow comes back under workflow too, and name is required to create one.
  • A new workflow starts as a draft. An update can move a draft to active, and move an active workflow to inactive and back.
  • A workflow is read by its wf_ id or its code. The milestone listing takes the wf_ id in its workflow_uuid slot.
  • Component instance routes take the component’s dashed uuid. Under /workflows/custom_components, component_uuid is the hex of the cmp_ id with the dashes put back and object_code is the instance’s code; the cmp_ id and the bare hex return 404.
  • Deleting a milestone sits in this area. DELETE /milestones/{milestone_uuid} is listed with the workflow endpoints.
  • Listings page by cursor. Records sit under data; pass pagination.next_cursor as cursor to read the next page, and stop when pagination.has_more is false.