Search taggable locations (Instagram or Threads)
Search physical places to get a valid location_id for tagging a post. The platform query parameter selects the source, and the two sources use DIFFERENT ids (a Facebook Place ID is not a Threads location id), so always search with the platform you will tag.
platform=instagram (default): search by name (q). Returns only real venues with a precise address (the kind Instagram accepts); national brand pages, personal profiles, and Instagram location IDs are not returned because Instagram rejects them. Pass a returned id as the top-level location_id on POST /posts/create. Requires a Facebook account connected to the workspace (the lookup runs through Facebook's place data). Response shape: { data: [...], error, needsPermission }.
platform=threads: search by name (q) OR by coordinates (latitude + longitude). Pass a returned id as threads.location_id on POST /posts/create / PATCH /posts/{id}. Requires a Threads account connected with the threads_location_tagging permission (connections made before that permission was added must be reconnected; the response then carries error.code = threads_reauth_required). Threads allows 500 location searches per account per rolling 24 hours. Response shape: { locations: [...] } or { error: { code, message } }.
Query parameters
Which platform the location will be tagged on. Determines the search source and the id type returned.
Place name to search (min 2 chars), e.g. a dealership, café, or venue name. Use a specific name — generic brands return their individual store locations, not the brand. Required for platform=instagram; for platform=threads pass either q or latitude + longitude.
Threads only. Search places around this point; pass together with longitude instead of q.
Threads only. Pass together with latitude.
Response
Matching places. The shape depends on platform.
Example response
{
"data": [
{
"id": "313813441",
"name": "Griffith Observatory",
"address": "2800 E Observatory Rd, Los Angeles, CA, 90027, United States"
}
]
}Changes
No recorded changes to this endpoint across all 1 revision of this API.