---
title: "Look up Meta targeting ids"
method: POST
path: "/api/v1/tools/meta_search_targeting/execute"
tags: ["Meta Ads"]
---

# Look up Meta targeting ids

`POST /api/v1/tools/meta_search_targeting/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/meta_search_targeting/execute`
- Auth: HTTP bearer

Turns a plain-language audience description into the ids Meta's write endpoints require: interest ids, behaviour ids, and location keys for countries, regions, cities, postcodes and media markets.
Use when: the user describes an audience in words ("women in Berlin interested in yoga") and before any campaign creation. meta_create_image_campaign only accepts ids, never free text.
Do not use to check how an existing audience is performing (meta_get_adset_performance) or to list saved audiences (meta_list_custom_audiences).
Returns the id or location key plus the estimated audience size where Meta provides one. Search one concept at a time; broad queries return loosely related suggestions.
If several results look plausible, show the user the options with their sizes and let them choose. Do not pick one silently.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `ad_account_id` string: Meta ad account id such as act_1234567890. Omit it to use the primary account; if several accounts are active and none is primary the call fails and lists the valid ids.
    - `search_type` 'interest' | 'behavior' | 'location', required: interest = hobbies, topics, brands; behavior = purchase and device behaviours; location = places.
    - `query` string, required: What to search for, e.g. "yoga", "frequent travellers", "Berlin".
    - `location_types` string[]: For search_type=location: which kinds of place to return. Defaults to country, region and city.
    - `limit` integer: Maximum results (default 15).
    - `raw_data` boolean: Return compact JSON only (no markdown). Use when you will compute on the result.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)