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 (opsional)

Mayoritas developer Meta menggunakan webhooks untuk mendapatkan notifikasi realtime dan mengurangi jumlah panggilan API, sehingga mengurangi perubahan pembatasan laju. Webhooks ditambahkan secara otomatis, tetapi bersifat opsional.

Untuk menerima webhooks dari Meta, Anda perlu:

Membuat endpoint di server Anda untuk menerima dan memproses notifikasi HTTP ini
Mengirim permintaan POST untuk berlangganan aplikasi Anda ke webhooks
Mengonfigurasi webhooks di dasbor aplikasi Anda (langkahnya tercantum di bagian ini)

Untuk mengonfigurasi webhooks untuk kasus penggunaan Anda di dasbor aplikasi, ikuti langkah-langkah berikut. Langkah-langkah ini mengasumsikan Anda berada di dasbor Kasus penggunaan > Penyesuaian > Penyesuaian kasus penggunaan dan telah memilih opsi Webhooks di menu.

Pilih produk - Pada menu pilihan, pilih aset, seperti Halaman dan Akun Iklan, yang ingin diberitahukan kepada Anda.
Tambahkan URL Panggilan Balik Anda, endpoint yang Anda buat untuk menerima webhooks.
Tambahkan token Verifikasi Anda yang akan digunakan Meta sebagai bagian dari verifikasi URL panggilan balik.
Anda dapat menambahkan autentikasi klien ke proses verifikasi dengan menggeser TLS Bersama dari Tidak ke Ya. (Opsional)

Catatan: Untuk menerima notifikasi webhook, aplikasi Anda harus diterbitkan. Tinjauan Aplikasi tidak diperlukan untuk menggunakan 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.