Este documento se ha actualizado.
La traducción en Español (España) no está disponible todavía.

Actualización del documento en inglés: 9 sep.
Actualización del documento en Español (España): 10 jun.

Customize a Meta app with the Access the Threads API Use Case

This document shows you how to customize the Access the Threads API use case you added to your app during the app creation process.

Customize use cases

If you are not already on the Use cases page of the dashboard, click Use cases, or the pencil icon, in the left-side menu.
Click on a use case to view the permissions that are available, both required and optional, for this use case.
Click the Add button to the right of each permission you'd like to add. If, during development, you find that your app doesn't use the permission, you can return here and remove it.

Threads API use cases permissions

The following table shows the permissions available for the Threads API use case.

Permission	Usage	Allowed actions
`threads_basic`	Required	Cannot be removed.
`threads_content_publish`	Optional.	Can be added or removed.
`threads_delete`	Optional.	Can be added or removed.
`threads_keyword_search`	Optional.	Can be added or removed.
`threads_location_tagging`	Optional.	Can be added or removed.
`threads_manage_insights`	Optional.	Can be added or removed.
`threads_manage_mentions`	Optional.	Can be added or removed.
`threads_manage_replies`	Optional.	Can be added or removed.
`threads_read_replies`	Optional.	Can be added or removed.

You can add and remove permissions at any time during the development process.

Settings

In the left side menu, click Settings. You'll find your Threads app ID and Threads app secret.
Add the following URLs:
- Client OAuth Settings – valid OAuth redirect URIs
- Deauthorize callback URL – the URL Meta will ping when a user deauthorizes your app
- Data Deletion Requests URL – the URL Meta will ping when someone requests that you delete their data
Click Save.
Click the Add or Remove Threads Test Users to add testers to your app. The page will refresh to the App roles > Roles page in the dashboard.
Click the Add People button to add people as to one or more of the following app roles:
- Adminstrator
- Developers
- Testers
- Analytics Users
- Threads Testers

Webhooks (opcional)

La mayoría de los desarrolladores de Meta utilizan webhooks para recibir notificaciones en tiempo real y reducir el número de llamadas a la API, lo que reduce el cambio de la limitación de frecuencia. Los webhooks se añaden de forma automática, pero son opcionales.

Para recibir webhooks de Meta, debes hacer lo siguiente:

Crear un extremo en el servidor para recibir y procesar estas notificaciones HTTP.
Enviar una solicitud POST para suscribir la aplicación a los webhooks.
Configurar los webhooks en el panel de la aplicación (el paso que se indica en esta sección)

Para configurar los webhooks para tu caso de uso en el panel de la aplicación, sigue estos pasos. En estos pasos, se presupone que estás en el panel Casos de uso > Personalizar > Personaliza el caso de uso y que has seleccionado la opción Webhooks en el menú.

Selecciona el producto: en el menú desplegable, selecciona los activos, como “Página” y “Cuenta publicitaria”, sobre los que quieres recibir notificaciones.
Añade la URL de devolución de llamada; es decir, el extremo que has creado para recibir los webhooks.
Añade el identificador de verificación que Meta utilizará como parte de la verificación de la URL de devolución de llamada.
Puedes añadir la autenticación del cliente al proceso de verificación. Para ello, cambia TLS mutuo de “No” a Sí. (Opcional)

Nota: Para recibir notificaciones de webhooks, la aplicación debe estar publicada. No es necesario que superes la revisión de la aplicación para usar webhooks.

Testing (Optional)

Testing is only required if you are submitting your app for App Review; if your app will access data you don't own or manage.

Click Testing in the left-side menu if you are ready to test your configuration.

Publish

Note: Some use cases require your app to be published.

When you are ready to publish, select Publish in the left side menu.
Review your use cases and requirements.
Click Publish in the lower right corner.

If you would like to become a Tech Provider click Become a Tech Provider.

For Tech Providers

The following steps must be completed if you're a Tech Provider, your app will serve clients or other business portfolios.

App Review

Click the chevron next to each requirement listed under Prepare and submit for App Review. You must complete each requirement before publishing your app.

A checkmark within a circle appears when each of these requirements has been completed.

Learn more about App Review.

Publish your app

Click the chevron to the right of Check that all requirements are met, then publish your app. If any requirements have not yet been met, messaging will appear and you will need to satisfy those requirements.
Once you have successfully completed all the requirements, click Publish in the lower-right corner.

After your app has been published, the Dashboard will show App Health with Daily API Calls.