**With the [Papo](https://papo.global/) REST API, you can list existing tags, create new tags, and apply a tag to a contact with an open conversation — all through authenticated requests, without opening the dashboard. It's a programmatic way to automate the categorization and organization of service from external systems, CRMs, or automation tools.**

The Papo API exposes Conversation resources that include tag management. With them, your team can maintain a consistent taxonomy, prepare categories before campaigns, and classify contacts and conversations in real time, using the same authentication as other platform endpoints.

## Summary of tag operations via API

| Operation | What it does | When to use |
| :--- | :--- | :--- |
| List tags | Returns the tags registered in the account, with name and color for visual identification. | Audit account standardization or sync tags with another tool. |
| Create tag | Creates a tag in the account without applying it to a contact. | Prepare new categories before applying in bulk or in automations. |
| Apply tag to contact + conversation | Creates the tag if it doesn't exist and applies it to the contact and the open conversation. | Automate triage, qualification, or classification as soon as the conversation comes in. |

## How API authentication works

All write routes, including tag 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 upon creation; store it in a safe place and revoke it if there is a suspected leak.

## How to use it in practice

1. Access the developer/API area in the Papo dashboard and generate a secret key. Also copy the account's public key.
2. In each request, authenticate with the secret key as a Bearer token. If you want to strengthen validation, send the public key in the header indicated in the documentation.
3. To list tags, call the API's tag listing endpoint. The response returns the registered tags, allowing you to map what already exists before creating new ones.
4. To create a tag without applying it, send a JSON payload with the tag information to the creation endpoint. Consult the official documentation for the exact format.
5. To apply a tag to a contact with an open conversation, call the tagging endpoint. If the tag doesn't exist yet, it will be created automatically and applied to the contact and the open conversation.

Since the API is REST and uses JSON, any language with HTTP support can be used to integrate tags into 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

- **Teams that use external automations** to classify conversations without opening the Papo interface.
- **Operations that need to create tags in bulk** before campaigns or when implementing a new service taxonomy.
- **Integrators and white label resellers** who connect Papo to client systems and want to maintain consistent categorization across accounts.
- **Companies that already use the Papo API** for contacts and messages and want to complete the flow with tags.

## Frequently asked questions

### Do I need to create the tag before applying it via API?

No. The API has a feature that creates the tag in the account if it doesn't exist and applies it to the contact and the open conversation. There is also the option to only create the tag, without applying it to any contact.

### Does the tag applied via API apply to both the contact and the conversation?

Yes. The tagging feature applies the tag to the contact and the open conversation, helping to classify both the lead's history and the ongoing service.

### Is the authentication the same as used in other Papo endpoints?

Yes. Write routes require the account's secret key, sent as a Bearer token. The public key is optional and, if sent, must match the same account.

### Where do 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 tags and other resources.

### Can I use the API to classify old conversations in bulk?

The application feature described in the platform acts on the contact and the open conversation. For specific cases of migration or retroactive classification, it's best to consult the official documentation and combine conversation listing with sequential calls, when the flow allows.

## 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 send WhatsApp message templates (HSM)](/hc/papo/articles/how-to-use-papo-api-send-whatsapp-message-templates-hsm)

---

**[Start for free →](https://papo.global/?utm_source=helpcenter&utm_medium=article&utm_campaign=how-to-use-papo-api-create-manage-tags&utm_content=en)**

Create your free account and centralize WhatsApp, Instagram, email, and SMS in a single inbox, with tags to organize your service.