Desarrollo de apps con Meta
Volver al documento en español
Se actualizó este documento.
La traducción en español no está disponible todavía.
Actualización del documento en inglés: 9 de sep.
Actualización del documento en español: 10 de 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

  1. 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.
  2. Click on a use case to view the permissions that are available, both required and optional, for this use case.
  3. 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.

PermissionUsageAllowed 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

  1. In the left side menu, click Settings. You'll find your Threads app ID and Threads app secret.
  2. 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
  3. Click Save.
  4. 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.

  5. 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 disminuir la cantidad de llamadas a la API. Gracias a esto, también disminuye la variación en la limitación de frecuencia. Webhooks se agrega de forma automática, pero es una característica opcional.

Para recibir webhooks de Meta, debes hacer lo siguiente:

  1. Crear un punto de conexión en tu servidor para recibir y procesar las notificaciones HTTP
  2. Enviar una solicitud POST para suscribir tu app a los webhooks
  3. Configurar webhooks en el panel de tu app (el paso que se desarrolla en esta sección)

Para configurar webhooks para tu caso de uso en el panel de la app, sigue los siguientes pasos. Esta explicación presupone que te encuentras en el panel Casos de uso > Personalizar > Personalizar caso de uso y que seleccionaste la opción Webhooks en el menú.

  1. Seleccionar productos: en el menú desplegable elige sobre qué recursos quieres recibir notificaciones, por ejemplo, Página y Cuenta publicitaria.
  2. Agrega tu URL de devolución de llamada, es decir, el punto de conexión que creaste para recibir webhooks.
  3. Agrega el token de verificación que usará Meta como parte de la verificación del URL de devolución de llamada.
  4. Puedes agregar la autenticación de clientes al proceso de verificación. Para ello, cambia la configuración de TLS mutuo de No a Sí. (Opcional)

Nota: Para recibir notificaciones de webhooks tu app debe estar publicada. No se precisa la revisión de la app 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.

  1. 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.

  1. When you are ready to publish, select Publish in the left side menu.
  2. Review your use cases and requirements.
  3. 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

  1. 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

  1. 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.
  2. 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.

See Also

Visit the following to learn more about the app development process: