Threads setup

Create an app

Go to Meta for Developers and create a new app. Give your app a name and email.

Request access to Threads

Select Access the Threads API.

Add business details, or skip

If you are unable to skip or move to the next step, and get a message saying “There are no business portfolios available to connect to this app”, go to your Meta Business Suite Settings and make sure you have enabled Two-Factor Authentication (2FA) for your account.

Finish creating the app

Configure API access

On the app dashboard, Select “Access the Threads API” to begin customizing the API access.Add all four of these. threads_basic is selected for you; the other three are not:

• threads_basic
• threads_content_publish
• threads_manage_replies
• threads_manage_insights

Threads is the one network where a missing scope does not stop the connect. The channel appears, looks healthy, and then replies and analytics fail later with no obvious cause. Add all four now rather than finding out which one you skipped a week from now.

Set threads API settings

• Click the “Settings” tab. Copy your “Threads App ID”, and set the postqueen environment variables THREADS_APP_ID to this value.
• Click the “Show” button next to the Threads App Secret, and set the postqueen environment variable THREADS_APP_SECRET to this value. Note that the next box is quite small, make sure you scroll across the copy the full value. It should be 32 characters long.

Your Threads OAuth2 Redirect URI:

• Production: https://postqueen.example.com/integrations/social/threads
• Local development: https://redirectmeto.com/http://localhost:4200/integrations/social/threads
• Docker: https://redirectmeto.com/http://localhost:4007/integrations/social/threads

Threads will not send a visitor back to a plain http address, so when your FRONTEND_URL is not https she wraps the callback through redirectmeto.com on its way home. That wrapped address is the literal string she sends to Threads, which makes it the one you register. Local development and Docker both fall into this case. Register the bare localhost URI instead and the login stops on Threads with a redirect mismatch.

You have to “click” the URL to make it active, otherwise the form will not save. You can use the same value for the Uninstall Callback URL and Delete Callback URL, but note that PostQueen does not support either at this time. The form will not save unless you enter something.

Go back to the ‘Dashboard’ view of the Facebook developers portal and click “Finish customization”. Make sure you clicked through the setup wizard, and select “Yes I’m finished” to complete the setup. The API may not work until you have done this.

Restart PostQueen

Add the Threads account as a tester

Allow the app on your threads account

• On threads.com, open your account settings;
• Open Website permissions, and switch to the “Invites” tab;
• If all has gone well, you should have a pending invite. Accept that invite.

Start testing

• Go back to the Meta developers portal, and in the sidebar, click Testing, and then open the Open Graph API Explorer.
• In the header, dropdown the API selector and change it to threads.net v1.

• In the right sidebar, under Access Token, click Generate Threads Access Token. This will open a new window where you can select the Threads account you want to test with - it should be an account that accepted the earlier invite. If everything has worked successfully you should be provided with a very long alphanumeric access token - you do not need to do anything with this, but it proves things are working correctly.

Good luck!