**With the [Papo](https://papo.global/) REST API, you can list all flows available in your account, enable or disable journeys, and enroll contacts in automations programmatically — all through authenticated requests, without opening the panel. It is the way to integrate the flow engine with external systems, n8n workflows, CRMs, or internal scripts.**

Papo's API exposes flow resources that let you manage automations just as you already manage inboxes or contacts. With it, development teams, integrators, and white label resellers can control in batch which journeys are active, start contacts in sequences, and sync automation status with business processes.

## Summary of Flow operations via API

| Operation | Description | Example use |
| :--- | :--- | :--- |
| List flows | Returns the available flows and sequences, with identifier, name, type, and status (Active/Inactive). | Audit automations, sync with external dashboards, or check what is running. |
| Enable/disable flow | Changes the status of a specific flow, releasing or pausing contact receipt and processing. | Pause a journey during maintenance, release it after adjustments, or disable a completed campaign. |
| Enroll contact | Inserts an existing contact at the beginning of an active flow, starting the configured journey. | Include leads from an external CRM, trigger a welcome flow after integration, or correct manual entries. |

## How API authentication works

All API calls, including those involving flows, require the account's **secret key**. It must be sent as a Bearer token in the `Authorization` header. The account's **public key** is optional, but if sent it must match the same account as the secret key.

The API base URL is `https://app.papo.global/api/v1`. Keys are generated in the developer area of the Papo panel. The secret key appears only once at creation; store it in a safe place and revoke it if there is any suspicion of leakage.

The authentication pattern is the same used in all endpoints:

```
curl https://app.papo.global/api/v1/me \
  -H "Authorization: Bearer sk_live_…" \
  -H "X-Papo-Public-Key: pk_live_…"
```

## Managing flows via API in practice

Although the exact details of each endpoint and parameter are in the official API documentation, the general workflow follows these conceptual steps:

1. **Authenticate** with the secret key (and, if desired, the public key) to validate the account.
2. **List the flows** to get the current list of journeys, including their identifiers and status. This lets you map what already exists and choose the right flow for the next operations.
3. **Change the status** of a specific flow, if needed. Send a request that sets the flow as active (released to receive contacts) or inactive (paused). Only active flows process contacts and accept enrollments.
4. **Enroll a contact** in an active flow. Provide the contact identifier and the desired flow identifier to insert it at the beginning of the journey. The contact's history in the CRM is preserved.
5. **Integrate with external systems** — through webhooks or direct calls, you can start contacts coming from an external form, an event in another system, or a data pipeline.

The platform also supports creating empty and inactive flows and filling their nodes via API, making it possible to provision complete automations programmatically. For the exact payload formats, required fields, and code examples, see the flows section in the Papo API documentation.

## Who this integration is for

- **IT teams that operate multiple automations** and need to pause, reactivate, or monitor flows in batch without accessing the panel manually.
- **White label resellers** that want to automatically provision standardized journeys for each new client, enroll initial contacts, and keep alignment across platforms.
- **Integrators and developers** who connect Papo to CRMs, ERPs, or tools such as n8n, triggering flows from external events (a purchase, a signup, a scheduled appointment).
- **Operations that work with conditional enrollment**, where contacts are included in flows only after passing business rules defined in other systems.

## Frequently asked questions

### Do I need the secret key to list flows?

Yes. Listing flows, like any operation that returns account data, requires authentication with the secret key. The pattern is the same as all other endpoints: send the Bearer token in the `Authorization` header.

### Can I enable or disable a flow via API?

Yes. The API allows changing a flow's status between active and inactive. You need the flow identifier and the secret key. Inactive flows do not receive contacts and do not advance the journey, even if an enrollment is attempted.

### How do I enroll a contact in a flow via API?

Provide the contact identifier and the active flow identifier in the enrollment call. The contact will be inserted at the beginning of the journey, without deleting conversation history or profile data. The official documentation details the exact parameter format.

### Is it possible to create a flow from scratch via API?

Yes. The API allows you to create an empty flow (with only the Start node) and inactive, as well as fill its nodes with questions, messages, and conditions. This is useful for provisioning automations at scale, especially in reseller or new customer onboarding scenarios.

### Does the API return the status of each flow when listing?

Yes. The listing includes the status (Active or Inactive) of each flow and sequence, plus identifier, name, and type, allowing external systems to monitor what is running and what is paused.

### Where can I find the complete documentation for flow routes?

The official documentation is available at [https://papo.global/pt/docs](https://papo.global/pt/docs). There you will find all endpoints, accepted parameters, error codes, and examples in multiple languages. The flow routes follow the same REST pattern and authentication as the other modules.

## Read also

- [How to use the Papo API to create and update contacts in bulk](/hc/papo/articles/how-to-use-papo-api-to-create-and-update-contacts-in-bulk)
- [How to use the Papo API to create and manage tags](/hc/papo/articles/how-to-use-papo-api-create-manage-tags)

---

**[Start integrating your flows right now →](https://chat.papo.global/app/auth/signup?papo_lp=home&utm_source=lp&utm_medium=landing&utm_campaign=home&utm_content=start-free&papo_lp_v=start-free)**

Create your free Papo account, access the API keys, and connect your automations with the outside world.