Skip to main content

Flowcall Developer API

Use Flowcall's public API to connect external systems to the ticket, WhatsApp template, and resource-record operations documented below.

Start here​

  • Base URL: https://api.flowcall.co
  • Authentication: Bearer access token
  • Create a token: In the Flowcall dashboard, open Settings → Integrations
  • Machine-readable contract: OpenAPI 3.1 specification

Keep access tokens on the server. Do not expose them in browser or mobile-client code.

When to use the API​

Use the public API when an external system needs to:

  • create a support ticket;
  • retrieve, filter, or export tickets;
  • retrieve configured WhatsApp templates or send an approved template;
  • insert structured resource data or upsert an existing resource record;
  • run an execute action from the Data Library.

API groups​

Ticket APIs​

Create manual tickets, retrieve filtered ticket lists, and export ticket data as CSV.

Read the Ticket API reference

Template APIs​

Retrieve WhatsApp templates configured for the account and send approved WhatsApp template messages.

Read the Template API reference

Resource Record APIs​

Insert structured data into a Flowcall resource or upsert a record using a configured resource field as its identifier.

Read the Resource Record API reference

Execute Action APIs​

Run an execute action from the Data Library, such as creating a return or updating an external system, with a single set of inputs.

Read the Execute Action API reference

Authentication​

Send the access token with every request:

Authorization: Bearer <your_access_token>

The token identifies the Flowcall account. Some operations also verify that the requested object belongs to that account.

Quickstart​

The following request retrieves the first page of tickets:

curl -X POST https://api.flowcall.co/apis/task-runs/tickets/list \
-H "Authorization: Bearer <your_access_token>" \
-H "Content-Type: application/json" \
-d '{
"page": 1,
"limit": 20,
"sortOrder": "desc"
}'

Limits and errors​

Rate limits vary by endpoint and are recorded in the relevant API reference. Error responses use HTTP status codes and JSON bodies; each endpoint page documents its expected validation and authorization errors.

For implementation questions or account access, contact your Flowcall account team.