Connecting Threads to AutoPost

Contents

0. Cover & contents

1. Overview

2. Understanding the terms

3. Step A — Checking your Threads profile

4. Step B — Preparing a Meta app

5. Step C — Adding the Access the Threads API use case

6. Step D — Adding the publishing permission

7. Step E — Entering the three addresses in Settings

8. Step F — Making your profile a Threads Tester

9. Step G — Connecting in AutoPost

10. Step H — Your first post

11. Managing connected accounts

12. Troubleshooting

13. Security and privacy

14. Checklist

15. Help

1. Overview

What you'll achieve

After following this guide, AutoPost can send text, images, and videos to your Threads profile: right away when you press Send now, or automatically at the time you schedule.

It works through the official Threads sign-in and your own Meta app. You never give your Threads password to AutoPost. A regular Threads profile is accepted too — Threads has no Business or Creator accounts like Instagram does.

Estimated time

You only do this once. Most of the time is spent in the Meta dashboard and in your Threads settings.

What you need

What AutoPost sends to Threads

Carousels are supported: 2–10 photos/videos in one post (add several media in New post), alt text per media item.

Not supported by AutoPost yet: polls, replies, GIFs, spoilers, and editing or deleting posts that are already published. To delete a post, do it directly in the Threads app or on the Threads website.

2. Understanding the terms

3. Step A — Checking your Threads profile

3.1 Your Threads profile must already exist

AutoPost connects a Threads profile, not an Instagram account. If you've never opened Threads, first create your profile in the Threads app or at threads.com.

3.2 Finding your Threads username

You'll need this name in Step F.

1. Open threads.com and sign in.

2. Open Profile.

3. Note the username shown there (without the @).

3.3 Public or private profile?

Our test used a public profile. Meta's documentation doesn't forbid private profiles from using the Threads API, but the documentation itself is inconsistent about permission renewal for private profiles. If your private profile is ever labeled needs reconnecting, just reconnect it (11.2).

4. Step B — Preparing a Meta app

If you already have a Meta app

For example the app you created while following the Facebook Page guide (/panduan/facebook/en) or the Instagram guide (/panduan/instagram/en). Just use that app. This guide was tested with the same app: the Access the Threads API use case can be added to an app that already serves a Facebook Page and Instagram. Go on to Step C.

If you don't have a Meta app yet

Follow Step B in the Facebook Page guide (/panduan/facebook/en) to create an app at developers.facebook.com. Once the app exists, add the Threads use case through Step C below.

5. Step C — Adding the Access the Threads API use case

1. At developers.facebook.com, open your app.

2. In the left menu, choose Use cases.

3. Press Add use case (the button at the top right). A window for adding more use cases opens. Access the Threads API usually appears under the Featured filter; if you don't see it, choose the All filter.

4. Tick the box on the right of the Access the Threads API card.

5. Press Save at the bottom right.

Access the Threads API now appears in your app's list of use cases, with a Customize button.

6. Step D — Adding the publishing permission

1. On the Access the Threads API card, press Customize.

2. In the left menu of that page, choose Permissions and features.

3. The threads_basic row is already there and marked Ready for testing. This permission is required and can't be removed.

4. On the threads_content_publish row, press Add.

5. The threads_content_publish row is now also marked Ready for testing.

You don't need to add any other permissions. "Ready for testing" sounds as if it isn't ready, but for your own profile acting as a Threads Tester, this status is enough.

7. Step E — Entering the three addresses in Settings

7.1 Copying the addresses from AutoPost

1. In AutoPost, open the Social accounts menu. On the Threads card, press Connect (it says Manage if an account is already connected).

2. The Threads page opens. The How to connect card has numbered steps, followed by a blue box with the three addresses.

3. Click an address in the blue box. The whole address is selected at once. Copy it (Ctrl+C), then paste it into the Meta dashboard field named right above that address.

For AutoPost at app-autopost.solusikecerdasankomputasi.com, the three are:

7.2 Pasting them in the Meta dashboard

1. In the Meta dashboard, open Use cases, press Customize on the Access the Threads API card, then choose Settings in the left menu.

2. The top of the page shows the Threads app ID and, to its right, the Threads app secret (hidden, with a Show button). Below them is the Threads Display Name field (or similar). The ID and secret are used in Step G.

3. In the Redirect Callback URLs field, paste the redirect URL, then press Enter. The address turns into a label (a small box). Without Enter, the address isn't saved as a list item yet.

4. In the Uninstall Callback URL field, paste the uninstall (deauthorize) address.

5. In the Delete Callback URL field, paste the data deletion address.

6. Press Save.

Below them is the User Token Generator section. You don't need it — AutoPost gets its own token when you grant permission in Step G.

8. Step F — Making your profile a Threads Tester

Until the app passes App Review for the Threads permissions, only profiles that have a role in the app can grant those permissions. So your Threads profile needs to be made a Threads Tester, and then the invitation must be accepted.

8.1 Adding the tester in the Meta dashboard

1. In the app dashboard's left menu, choose App roles → Roles. (From the Settings page of the Threads use case, the Add or Remove Threads Testers button takes you to the same place.)

2. Press Add People.

3. A window for adding people to your app opens. Don't choose the roles at the top (Administrator, Developer, Tester, Analytics User). In the section for additional roles for this app, choose Threads Tester.

4. In the field that asks for the Threads account username, type your Threads username (from Step A, without the @).

5. With the correct Threads name, an account suggestion appears below the field. Choose your account.

6. Press Add.

Your profile now appears in the App roles list with the Threads Tester role and the status Pending (or similar wording meaning "Waiting for approval"). That status disappears once the invitation is accepted (8.2).

8.2 Accepting the invitation in Threads

The invitation is accepted from that Threads profile itself, in a web browser.

1. Open threads.com and sign in with the profile you just invited.

2. Open Settings, then Website permissions. This page has four tabs: Active, Expired, Removed, and Invites.

3. Choose the Invites tab.

4. On the invitation from your app (in this example AutoPost), press Accept. Before it's accepted, the invitation shows a consent sentence (starting with "By accepting this tester invitation…") and two buttons: Accept and Decline. Don't press Decline.

By pressing Accept, you agree to Meta's Platform Terms and Developer Policies — the invitation says so. Since the app is your own, that's expected.

Once accepted, AutoPost stays listed on the Invites tab, now with a Remove button (the picture below was taken after the invitation was accepted, so the Accept button is no longer visible). Don't press Remove here.

In the Meta dashboard, the status in the App roles list is now empty — no longer pending. Under the Threads Tester role, a note says that Threads users can manage invitations in the Website permissions section of their profile.

9. Step G — Connecting in AutoPost

9.1 Copying the Threads app ID and secret

Both are in the Settings of the Access the Threads API use case (Step E, 7.2), at the very top.

1. Threads app ID — copy the number.

2. Threads app secret (to the right of the ID) — press Show, then copy all of it. Meta may ask for your Facebook password first; enter it yourself, and never give it to anyone else.

9.2 Filling in the form

Go back to the Threads page in AutoPost. Below the box with the three addresses is a form:

1. Threads app ID — paste the ID. It's 10–20 digits.

2. Threads app secret — paste the secret. It's deliberately shown as dots.

3. Press Connect Threads.

9.3 Granting permission in Threads

AutoPost takes you to the Threads permission page. It reads "AutoPost is requesting access to:" followed by the list of permissions.

1. Check the profile name on the blue button. Make sure it's the profile you want to connect. If it's the wrong profile, press Cancel, sign out of Threads, sign in with the right profile, then repeat from 9.2.

2. Press Continue As (your profile name) — for example Continue As rina_kusuma.

9.4 What AutoPost does behind the scenes

1. When you press Connect Threads, AutoPost checks the format of the ID and secret, then creates a random security code (state). That code, the ID, and the secret are stored encrypted in a browser cookie that lasts 10 minutes.

2. After you grant permission, Threads sends you back to the redirect URL. AutoPost makes sure the security code matches and that you're still signed in with the same AutoPost account.

3. AutoPost exchanges the authorization code for a 1-hour token, then immediately exchanges that for a 60-day token.

4. AutoPost reads your Threads profile (ID, username, name, profile photo).

5. The token, Threads app ID, and Threads app secret are stored encrypted (AES-256-GCM) in the database. The secret is stored because it's needed to verify that revocation and data-deletion notifications really come from Meta. The temporary cookie is deleted.

6. The token is renewed automatically when 15 days or less of its validity remain (and the token is at least 24 hours old — a Meta requirement). The AutoPost worker runs this check about once an hour, so you don't need to reconnect every 60 days. According to Meta, each renewal also extends the 90-day permission period.

9.5 Signs that it worked

You return to the Threads page in AutoPost. A green box appears at the top:

Your profile appears in the Connected accounts card with the label connected. Under the name are the display name and the token's validity, for example "Rina Kusuma · token valid until Nov 28, 2026 (renewed automatically)", then the time it was connected, the Retest button, and the red Disconnect button.

9.6 What "1 of 3" means

Each AutoPost account can connect at most 3 Threads profiles. This limit is enforced in the database. Once you have 3, the text next to the button says "Already 3 accounts — you can only reconnect the same account. Disconnect one to add another." A fourth profile is rejected with the message "There are already 3 Threads accounts. Disconnect one first if you want to replace it."

10. Step H — Your first post

10.1 Quick rules before you send

• Text only is fine. An image or video isn't required.

• At most 500 characters — an emoji counts as more than one (see the table below).

• At most 5 different links (including the Link field).

• Images in JPEG or PNG, up to 8 MB.

• Videos in MP4 or MOV: up to 5 minutes, up to 1 GB, 23–60 fps. The Upload from gallery button in AutoPost accepts files up to 50 MB.

• Alt text up to 1,000 characters.

• The first hashtag becomes the topic (10.5).

• Threads allows 250 posts through the API per profile every 24 hours.

How Threads counts emoji. According to Meta's documentation, an emoji counts as many characters as its UTF-8 bytes. AutoPost counts it the same way (deliberately a little strict), so text that passes in AutoPost won't be rejected by Threads for its length. Examples of AutoPost's count:

So 480 regular characters plus five 🎉 emoji is exactly 500 (480 + 5×4). One more emoji makes it 504 — over the limit, and the composer holds it back. Regular letters, digits, spaces, and accented letters (for example é) count as one.

10.2 Text with a link

1. Open New post and write your text.

2. Fill in Link (optional), for example the address of your article.

3. Look at the Limits per platform card. For Threads there are two rows: Threads (x/500) and — as soon as there's a link — Threads · different links (x/5). Without an image/video, the note says: "No photo/video: the Link field appears as a link preview and isn't counted."

4. Under Send to, make sure only your Threads profile is selected (with a check mark).

5. Choose Send now (next to Save as draft and Schedule), then press the gold Send now button.

6. For a moment you'll see "Saved — sending to the selected accounts…", then the green message "Sent to 1 account." The composer is cleared and the choice goes back to Save as draft.

10.3 Images

1. Press Upload from gallery and choose a .jpg or .png image (or create one with the Image studio, which always saves JPEG).

2. Fill in Alt text — a short description of the image for screen readers. This field appears below the media field once an image is attached (it isn't visible in the next picture).

3. Choose your Threads profile under Send to, then Send now.

On the right, the Photo check card assesses the image. The Ready label means the format is accepted.

If the Link field is filled in, the link is written on a new line at the end of the text (unless it's already in the text) and counts toward the 500 characters. The Threads row in Limits per platform is renamed Threads · text + link, with the note "There's a photo/video: the Link field is added at the end of the text and counted."

10.4 Videos

1. Press Upload from gallery and choose an MP4 or MOV video.

2. When a Threads profile is selected, the Alt text field also appears for videos: "For videos, alt text is sent to Threads only."

3. Choose your Threads profile under Send to, then Send now.

10.5 Hashtags and topics

Threads uses one topic per post. AutoPost has no topic field: Threads takes the first valid hashtag in the text as its topic. In our test on 29 September 2026, text ending in #AutoPost was published with the topic autopost (shown next to the profile name: "› autopost"). In the published text, that hashtag appears as the word AutoPost without the # sign.

When the text contains more than one hashtag and a Threads profile is selected, the composer shows a note (it doesn't block anything):

According to Meta's documentation: a hashtag made only of digits (for example #1) doesn't become a topic, and a topic stops before a space or the characters . & @ ! ? , ; :. Put the hashtag that best represents the post first.

10.6 Checking the result

In AutoPost, open the Posts menu. A successful send has the status sent. A successful send with a note (for example an image that was skipped or text that was shortened) is labeled sent · note in Details per account. A failed send has the status failed; the reason is in Details per account, and the Resend failed button is available.

On Threads, open your profile.

In our test on 29 September 2026, all three posts were visible from a browser that was not signed in to Threads — meaning they're shown to the public.

10.7 Scheduling and Auto post

• Schedule: choose Schedule, fill in the date and time (WIB), then press Schedule post. The AutoPost worker sends it by itself at that time. The 500-character and 5-link rules still apply: the composer holds the post back, and the server rejects it too.

• Auto post: a Threads profile can be chosen as a target. Once it's chosen, the Auto post form shows the note "Threads: max. 500 characters per post"; if the text is written by AI with a length other than Short, it adds the suggestion "Choose the Short post length so Threads posts don't need shortening." Because Auto post doesn't go through the composer, AutoPost adjusts by itself when sending:

  • Text over 500 characters is shortened at a word boundary with a "…" mark, and links stay intact. The note in Details per account: "The text was shortened to 500 characters to fit Threads' limit."

  • Images other than JPEG/PNG are skipped; the text is still published (with a note as in 10.3).

  • When there's a note like that, AutoPost also adds the link to the post: "View on Threads: …".

• The full guide to the composer is the New post guide: the Download guide (PDF) button on the New post page, or its web version at /panduan/postingan-baru/en.

11. Managing connected accounts

11.1 Retest

The Retest button in the Connected accounts card opens the token, makes sure it hasn't expired, renews it if it's close to expiring, then reads your Threads profile again. If everything is healthy, one of these messages appears:

• "Retest finished — the account is still healthy and ready to send."

• "Retest finished — the account is healthy and we extended its token too."

If Threads is busy (rate limits, network, a momentary outage), the account status isn't changed; the message ends with "We didn't change the account status — try testing again shortly." If the token has expired or was revoked, the account is labeled needs reconnecting. Other errors give it the label has a problem. The reason appears in red text under the account name.

Retest also updates the name and profile photo if you changed them on Threads.

11.2 Reconnecting

Fill in the Threads app ID and Threads app secret again, press Connect Threads, then Continue As … with the same Threads profile. AutoPost refreshes the token (it doesn't create a new account), and scheduled posts keep running.

Reconnect when:

• the account is labeled needs reconnecting;

• you revoked AutoPost's permission on Threads and want to use it again;

• the Threads app secret was changed in the Meta dashboard (13.3);

• you move the profile to another Meta app.

11.3 Disconnect

The Disconnect button removes that account from AutoPost along with its token and Threads app secret. AutoPost asks "Disconnect this account? Its token is deleted too."; press Yes, disconnect to continue. The result: "Account disconnected — its row and token are gone from the database."

Disconnecting also removes that account from scheduled posts and auto posts that target it, and the records of earlier sends to that account in Details per account are removed too. If you only want to refresh the token, don't disconnect — reconnect instead (11.2).

Disconnecting in AutoPost does not revoke the permission on the Threads side. To revoke it as well, see 11.6.

11.4 Deleting or editing posts

AutoPost can't delete or edit posts that are already published on Threads yet. Deleting a post in AutoPost's Posts menu only removes it from AutoPost; the post on Threads stays. Delete it directly in the Threads app or on the Threads website if needed.

11.5 Adding a 2nd and 3rd profile

1. Make the next Threads profile a Threads Tester in the same app (8.1), then accept the invitation from that profile (8.2).

2. In your browser, sign out of the first Threads profile and sign in with the next one.

3. Repeat 9.2 and 9.3 with the same ID and secret. On the permission page, check that the button says Continue As followed by the next profile's name, not the first profile's.

At most 3 Threads profiles. We haven't tried this with a second profile yet; the flow is the same as for the first.

11.6 Revoking permission from Threads

You can revoke AutoPost's permission directly from Threads:

1. On threads.com, open Settings → Website permissions — the same place as the invitation in 8.2.

2. The app currently using your permission is usually listed on the Active tab. Press Remove on your app (in this example AutoPost). We haven't captured this step yet; if it looks different, look for your app on the page's tabs.

What happens in AutoPost (according to Meta's documentation and AutoPost's design; we hadn't received a real notification from Meta when this guide was written):

• Meta calls the uninstall (deauthorize) address (Step E). AutoPost verifies it with the stored Threads app secret, then marks the account needs reconnecting with a red note: "AutoPost's permission was revoked from Threads. Reconnect if you want to use this account again." The next sends to that account will most likely fail until it's reconnected.

• If you (through Meta) ask for your data to be deleted, Meta calls the data deletion address. AutoPost deletes that Threads account row along with its token (the records of its earlier sends in Details per account are removed too), records the request, then gives Meta a confirmation code and the page address /hapus-akun?threads=<code>. That page says: "Threads data deletion confirmation code: …. If Meta gave you this code when you requested deletion, the related Threads account and its token were deleted from AutoPost at that time, and the code is recorded in our system. Keep this code if you want to ask us about it." Posts already published on Threads aren't deleted.

12. Troubleshooting

All the AutoPost messages below are written exactly as they appear on screen. On the Threads page the messages start with "Failed:"; in Details per account, messages that will be retried end with "(retrying automatically, attempt N of 4)". Parts that vary are marked "…" or "N".

12.1 When you press "Connect Threads" or return from Threads

Other Threads limit messages from table 12.4 (for example "Threads is temporarily holding posts from this account …") can also appear while connecting. The phrase "We'll try again …" in messages like that is always replaced by "Press Connect Threads again shortly.", because nothing is retried automatically while connecting.

These messages appear as a red ribbon starting with "Failed:" at the top of the Threads page, for example:

Is the Connect Threads button disabled with a red box above it? That box is titled "The server encryption key isn't set up yet", "The app's public address isn't set", or "The account list couldn't be read". Report it to the AutoPost administrator.

12.2 When you press Retest or Disconnect, or in the account status

12.3 In the composer (New post) and when saving

Examples of what the composer holds back (only the Threads profile selected):

12.4 When sending or after a scheduled time

The reason for a failure appears in the Posts menu, in the Details per account section of the post's card. After Send now, a summary also appears in the composer, for example "Sent to 1 account.", "Not sent yet — 1 will be retried automatically.", or "All sends failed — open the Posts page to see why."

Content and media:

Notes on successful sends (label sent · note):

Tokens, permissions, and Threads limits:

Network and outages:

12.5 Problems that don't show an AutoPost message

13. Security and privacy

13.1 Keeping the Threads app secret safe

• The Threads app secret is pasted in only one place: the Threads app secret field in AutoPost.

• Never paste it anywhere else: group chats, email, shared notes, screenshots, or other sites that ask for it.

• AutoPost never asks for your Threads, Instagram, or Facebook password.

• Turn on two-factor authentication for your Instagram/Threads account and your Facebook account.

13.2 What AutoPost stores

• Tokens, Threads app IDs, and Threads app secrets are stored encrypted (AES-256-GCM) in the database and are opened only on the AutoPost server: when exchanging and renewing the token, when sending, on Retest, and when verifying revocation or data-deletion notifications from Meta. AutoPost's pages never show your token.

• The Threads ID and username, display name, profile photo address, and the list of permissions — to show the account and to choose it as a target.

• While connecting, the ID and secret are briefly stored encrypted in a browser cookie for at most 10 minutes, then deleted.

• AutoPost asks for only two permissions: threads_basic and threads_content_publish. AutoPost doesn't read your other Threads posts, replies, followers, or messages.

The details are in AutoPost's Privacy Policy, section 5a. Threads data.

13.3 If the Threads app secret leaks

1. In the Meta dashboard, regenerate or change your app's Threads app secret.

2. Open the Settings of the Access the Threads API use case again, press Show, and make sure the value has changed. Copy the new value.

3. In AutoPost, reconnect every Threads profile with the new secret (11.2). This matters: AutoPost uses the stored secret to verify notifications from Meta, so the old secret must be replaced in AutoPost too.

4. Press Retest on every account to make sure they're all healthy.

We haven't captured where the button for changing the Threads-specific secret is, so step 2 matters: make sure the value you paste really is the new one.

13.4 Stopping using AutoPost for this profile

1. Press Disconnect in AutoPost (11.3). The token and Threads app secret are deleted right away.

2. Revoke the app's permission on Threads: Settings → Website permissions, then Remove on your app (usually on the Active tab; see 11.6).

3. If the app isn't used for anything else anymore (including a Facebook Page and Instagram), you may delete the app at developers.facebook.com. Use cases that have been added can't be removed on their own.

To delete your whole AutoPost account, see the Delete account page (/hapus-akun).

14. Checklist

• The Threads profile exists, and its username was noted from threads.com → Profile (not from Instagram).

• The Meta app has the Access the Threads API use case.

• Under Permissions and features, threads_basic and threads_content_publish are marked Ready for testing.

• In the Settings of the Threads use case, the three addresses exactly match the box in AutoPost (the redirect URL has become a label), and Save was pressed.

• The profile was added as a Threads Tester, and the invitation was Accepted on threads.com.

• The Threads app ID and Threads app secret were pasted into AutoPost (not Facebook's).

• Continue As … was pressed with "Create and share posts" left on, and the account shows as connected.

• A test text + link post has the status sent and appears on the Threads profile.

• (Optional) Test posts with a JPEG/PNG image and an MP4 video were published.

15. Help

• The New here? How to use this page box on AutoPost's Threads page summarizes the steps and common problems.

• The Help menu in AutoPost has a short guide for every menu and the illustrated Telegram guide.

• Other complete guides can be downloaded with the Download guide (PDF) button on their own pages: New post, Facebook Page, and Instagram (web versions: /panduan/postingan-baru/en, /panduan/facebook/en, /panduan/instagram/en).

• The Privacy Policy (section 5a. Threads data) and the Delete account page (section Threads data) explain what data is stored and how to delete it.