A recognizable voice
Keep the selected profile visible so the author identity stays clear.
Workflow preview · Confirm Threads access with our team
Bring profile identity, post preparation and conversation context into your app. Explore a Threads workflow that gives every thought a clear path to review.
Make room for writing and review without losing sight of the profile or the intended action.
Fans APIPlan your editorial flow | ThreadsConfirm the platform connection |
|---|---|
ProfileKeep the selected identity attached to the draft. | ProfileConfirm the account and authorization required for your use case. |
Post preparationBring the message and its preview into the same workspace. | Post preparationCheck supported content types and the native publishing flow. |
RepliesPreserve the original post beside a proposed response. | RepliesConfirm reply-related permissions separately from publishing access. |
ReviewSeparate draft, review and request results. | ReviewUse the actual API response before presenting a post as published. |
This is a Threads workflow concept. FansAPI availability and supported operations remain unconfirmed.
Keep identity and context close while the message takes shape.
Start with the identity your app should work with. Confirm the connection and required permissions.
Write the message with its preview close by. Keep the original context visible when preparing a reply.
Check the profile, content and intended action. Wait for a confirmed response before changing the published state.
A focused writing experience, with the original post above and a separate reply below.
Keep the selected profile visible so the author identity stays clear.
Give the draft room to develop without filling the screen with unrelated controls.
Keep the context of a response within view while composing.
Check the intended content and destination before submission.
Separate local drafts from requests and confirmed published results.
Treat publishing, reading replies and managing replies as separate access questions.
const response = await fetch(process.env.THREADS_API_URL, {
headers: {
[process.env.THREADS_AUTH_HEADER_NAME]:
process.env.THREADS_AUTH_HEADER_VALUE
}
});
const data = await response.json();
console.log(data);import os
import requests
response = requests.get(
os.environ["THREADS_API_URL"],
headers={
os.environ["THREADS_AUTH_HEADER_NAME"]:
os.environ["THREADS_AUTH_HEADER_VALUE"]
},
timeout=30,
)
print(response.json())<?php
$request = curl_init(getenv('THREADS_API_URL'));
curl_setopt_array($request, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTPHEADER => [
getenv('THREADS_AUTH_HEADER_NAME') . ': ' .
getenv('THREADS_AUTH_HEADER_VALUE'),
],
]);
$response = curl_exec($request);
curl_close($request);
echo $response;require "net/http"
require "json"
uri = URI(ENV.fetch("THREADS_API_URL"))
request = Net::HTTP::Get.new(uri)
request[ENV.fetch("THREADS_AUTH_HEADER_NAME")] =
ENV.fetch("THREADS_AUTH_HEADER_VALUE")
response = Net::HTTP.start(uri.host, uri.port,
use_ssl: uri.scheme == "https", read_timeout: 30
) { |http| http.request(request) }
puts JSON.parse(response.body)var request = HttpRequest.newBuilder()
.uri(URI.create(System.getenv("THREADS_API_URL")))
.header(
System.getenv("THREADS_AUTH_HEADER_NAME"),
System.getenv("THREADS_AUTH_HEADER_VALUE"))
.timeout(Duration.ofSeconds(30))
.GET().build();
var response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());curl --fail-with-body --max-time 30 \
"$THREADS_API_URL" \
-H "$THREADS_AUTH_HEADER_NAME: $THREADS_AUTH_HEADER_VALUE"THREADS_API_URL · server environmentModel the writing experience without confusing a local draft with a platform result.
| Moment | Interface state | Meaning |
|---|---|---|
| Profile selected | Author context | The identity associated with the proposed content. |
| Writing | Draft | Text being prepared in your workspace. |
| Final check | Ready for review | Content and destination are visible together. |
| After submission | Reported result | A result confirmed by the actual integration. |
These are interface states, not Threads API field names.
Prepare the account and permissions your Threads workflow needs. Confirm the FansAPI connection separately.
Identify the profile and whether your application needs publishing or conversation-related actions.
Meta’s Threads API uses authorized requests. Confirm app access, permissions and the FansAPI authentication contract.
Keep tokens private and use the documented request lifecycle for the selected operation.
The essentials before your first request.