**With the [Papo](https://papo.global/) REST API, you can automate team administration without opening the dashboard: list teams, create teams, list members of a team, add users to a team, and list or create inboxes. It is the programmatic way to keep your service structure synchronized with external systems, large operations, and white label resellers.**

The Papo API exposes team and inbox resources with the same authentication as the platform's other endpoints. With them, your team can provision new structures, audit who belongs to each group, and prepare conversation routing without manual intervention in the dashboard.

## Summary of team and member operations via API

| Operation | What it does | When to use |
| :--- | :--- | :--- |
| List teams | Returns the teams registered in the account. | Audit the structure before creating a new team. |
| Create team | Creates a team with a name and optional description. | Provision a new team via script, ERP, or CRM. |
| List members of a team | Returns the users who are part of that team. | Check who is included and avoid incorrect access. |
| Add users to the team | Includes one or more users by providing comma-separated IDs. | Synchronize the team with the current roster of agents. |
| List inboxes | Returns the inboxes with the channel, in the administrator view. | Check available channels and how they are organized. |
| Create inbox | Creates a new inbox. | Provision new channels along with the team structure. |

## How API authentication works

Write operations, including team and member operations, 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 dashboard. The secret key appears only once at creation; store it in a safe place and revoke it if you suspect a leak.

## Step by step to manage teams and members via API

1. Go to the developer/API area in the Papo dashboard and generate a secret key. Also copy the account's public key if you want additional validation.
2. In each request, authenticate with the secret key as a Bearer token. If you reinforce validation, send the public key in the header indicated in the documentation.
3. List existing teams to map the current structure before creating new ones.
4. Create a team by sending a JSON payload with a name and, if necessary, a description. Consult the official documentation for the exact format.
5. List the team members to audit who is already included and avoid duplicates.
6. Add users to the team by providing comma-separated IDs. This step synchronizes the team with the current roster of agents.
7. List inboxes with the administrator view to check existing channels and use the API also to create inboxes when necessary.

Because the API is REST and uses JSON, any language with HTTP support can be used to integrate teams and members with scripts, ERPs, CRMs, or automation tools. The official documentation at `https://papo.global/pt/docs` provides details on authentication, parameters, responses, and code examples.

## Who this integration makes sense for

- **Large operations** that need to create and adjust teams frequently without opening the dashboard manually.
- **IT and automation teams** that synchronize the agent structure with directories, HR, or internal systems.
- **White label resellers** that provision customer accounts in a standardized way, reusing the same team and inbox logic.
- **Companies that already use the Papo API** for contacts and conversations and want to complete the flow with team administration.

The API manages the team structure and member inclusion. User roles, such as Agent or Administrator, and granular permissions continue to be defined in the dashboard. By adding a user to a team and connecting them to the relevant inboxes, you control operational access to conversations.

## Frequently asked questions

### Does the Papo API define the user role, such as Agent or Administrator?

No. The teams and members API focuses on creating teams, listing members, and adding users. Defining each user's role and permissions is done in the dashboard. By including a user in a team and in the correct inboxes, you restrict access to operational conversations.

### Can I create a team without adding members in the same step?

Yes. The API allows you to create a team with a name and optional description, without including users immediately. Later, you can add members using the bulk inclusion operation.

### How does the API identify the account in requests?

By the secret key sent as a Bearer token. The public key is optional and, if sent, must match the same account as the secret key.

### Does this API work for white label resellers?

Yes. Resellers can use the API to provision teams and members in customer accounts in a standardized way, reducing manual configuration and maintaining consistency across operations.

### Where can I find the exact paths and payload format?

In the official API documentation, available at `https://papo.global/pt/docs`. There you will find details on authentication, parameters, responses, and code examples for teams, members, and other resources.

## Read also

- [How to use the Papo API to create and manage tags](/hc/papo/articles/how-to-use-papo-api-create-manage-tags)
- [How to manage users and permissions within your white label platform](/hc/papo/articles/how-to-manage-users-and-permissions-white-label-platform)

---

**[Start free and automate teams and members via API →](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)**

The first user is free forever, so you can validate the integration before structuring your operation.