← maia-astro.com

Threads App Review

English walkthrough for Meta reviewers. App: Threads use-case 1718572092659451 (parent Meta app 3525052200997205). Brand account: @maya.tarot.astro.

This is not a consumer Facebook Login product. The person using the app connects their own Threads account via official Threads OAuth, then uses the API only to manage that account’s presence: search public conversations, read replies on their own posts, and publish a reply after they tap Approve.

There is no multi-user consumer feed, no scraping, and no unattended public commenting. Until threads_keyword_search has Advanced Access, keyword search returns only the authenticated user’s own posts — that is expected.

Open the live console Download screencast (1080p) Privacy Policy Terms Data deletion

How to test (reviewer)

  1. Open https://pay.maia-astro.com/review/ (English UI).
  2. Click Connect with Threads. Complete the official Threads OAuth dialog. Grant: threads_basic, threads_keyword_search, threads_read_replies, threads_manage_replies, threads_content_publish.
  3. On your own Threads account, publish a short public post that contains the word tarot (required while the permission is Standard Access).
  4. In the console, search tarot. Your post appears. This is threads_keyword_search.
  5. Optionally edit the draft. Click Approve and publish reply. Nothing is posted without that tap. This is threads_manage_replies + threads_content_publish.
  6. Click Load my posts, then Show replies. This is threads_basic + threads_read_replies.

No test password is required. Use any Threads account that accepted the app’s tester invite, or the app-role account. We cannot share the brand account password.

What the app does with each permission

Paste-ready App Review notes are below. They match Meta’s allowed usage: help the user manage their social media presence.

threads_basic

Maia is a presence tool for a Threads creator. After the person connects their Threads account via official Threads OAuth (not Facebook Login), the app reads that account’s profile and their own posts so they can see what they already published and pick a post whose replies they want to manage. The data is shown only to the authenticated person. This is required before any other Threads API call.

Value: the person sees their own Threads identity and recent posts in one console.
Necessary: every Threads API endpoint depends on threads_basic.
Server note: the brand account @maya.tarot.astro also stores a long-lived user token for scheduled operator work. Reviewers should use the web console OAuth flow, which is the complete login grant.

threads_keyword_search

The app helps the connected Threads user manage their social media presence by searching public Threads conversations for keywords they cover (for Maia: tarot, astrology, and related self-reflection topics). The console shows the public post text, author username, timestamp, and permalink. The person may then write or edit a reply and tap Approve to publish a response to that public content.

This matches allowed usage: show public content the user searched for, and let them publish a response. The app does not scrape, store other people’s profiles, run unattended outreach, or show a public multi-user feed.

Until Advanced Access is granted, the official API returns only the authenticated user’s own posts. After approval, the same search returns other people’s public posts. Reviewers: publish a short public Thread containing “tarot”, then search that word.

Value: the creator finds conversations they can meaningfully join instead of posting into the void.
Necessary: without this permission the app cannot discover public keyword matches, which is the core presence-management feature.

threads_read_replies

The app lists replies under the authenticated user’s own Threads so they can see what people wrote and decide whether to answer. Replies are shown only to that user, in the same console.

Value: the creator does not miss comments on their own posts.
Necessary: the replies endpoint requires threads_read_replies. The app does not read replies on other people’s posts.

threads_manage_replies

The app publishes a reply on behalf of the connected Threads profile only after the person taps “Approve and publish reply”. The API call is POST /{user-id}/threads with media_type=TEXT, text, and reply_to_id, then POST /{user-id}/threads_publish. The app does not hide/unhide replies and does not change who can reply.

Value: the person can answer a search result or a comment on their own post without leaving the console, and they stay in control of every send.
Necessary: creating a reply on behalf of the profile is exactly the allowed usage of threads_manage_replies. Nothing is posted without the Approve tap.

threads_content_publish

The app uses threads_content_publish only to publish the reply container created in the step above (threads_publish). It does not publish original feed posts through this console (those go through a separate scheduling tool the owner already uses). The person still has to tap Approve.

Value: the approved reply actually appears on Threads.
Necessary: threads_publish requires threads_content_publish.

Screencast checklist

  1. Open https://pay.maia-astro.com/review/ (English UI).
  2. Click Connect with Threads. Show the official OAuth screen and the permission list being granted.
  3. Return to the console. Search “tarot”. Show results.
  4. Show the draft. Tap Approve and publish reply. Show the new reply on Threads or via the permalink.
  5. Load my posts → Show replies.

If a recording cannot complete OAuth on the reviewer’s machine, the live console above is the same flow. This is a Threads OAuth app, not Facebook Login for consumers.

Legal URLs (already live)

Maia · maia-astro.com · Telegram: @maia_astro_bot · Last updated: 2026-08-22