Search targeting interests
Search for interest-based targeting options available on the platform.
API key authentication - use your Zernio API key as a Bearer token
In: header
Query Parameters
Search query
Social account ID
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.ads.searchAdInterests({ query: { q: 'string', accountId: 'account_abc123', },});console.log(data);{
"interests": [
{
"id": "string",
"name": "string",
"category": "string"
}
]
}{
"error": "Unauthorized"
}List destinations for the Conversions API GET
Returns the list of pixels (Meta), conversion actions (Google), or conversion rules (LinkedIn) accessible to the connected ads account. Use the returned `id` as `destinationId` when posting to `POST /v1/ads/conversions`. For Google and LinkedIn, each destination's `type` reflects the conversion type (PURCHASE, LEAD, SIGN_UP, etc.) — the event type is locked to the destination. For Meta, `type` is absent: pixels accept any event name per request. For LinkedIn, destinations are returned across every sponsored ad account the connected token can access; the `adAccountId` field on each destination identifies the parent ad account and is required for subsequent CRUD calls (update, delete, associations, metrics).
Search geo targeting locations (Meta) GET
Resolve a human-readable location name into Meta's opaque `key` used in `targeting.cities[]` / `targeting.regions[]` on `POST /v1/ads/create` (and the same fields under `targeting.geo_locations` on `POST /v1/ads/boost`). Wraps Meta's `/search?type=adgeolocation` endpoint. Meta-only for now. Other platforms have their own location id systems and are not exposed here. Per Meta's docs, `q` must contain only the locality name (e.g. `"Amsterdam"`, not `"Amsterdam, NL"`). Use `countryCode` to disambiguate when the same name exists in multiple countries.