Marcas y seguimiento de marcas
Esto complementa el Referencia de la API. GET /api/v1/marcas es el API-key tracked-brands list (metered credits). Detail tabs and deep brand analytics use /api/marcas/* in the browser while you are logged in.
Nota sobre la ruta: Tracked brands over an API key: solo
GET /api/v1/marcas.GET /api/brandses el panel de control list for the logged-in session (same underlying data, not the metered JSON route for keys). Biblioteca de anuncios de Meta (GET /api/v1/adlibrary) is documented in Biblioteca de anuncios de Meta.
MCP tool (Brand tracker)
marcas_seguidas— same data asGET /api/v1/marcas(optionalbuscar,clasificar,board_id).
Configuración: MCP. Parámetros: MCP · Referencia de herramientas. Para buscar_anuncios_en_Facebook, véase Biblioteca de anuncios de Meta.
Autenticación y medición compartidas (/api/v1/adlibrary, /api/v1/marcas)
GET /api/v1/marcas uses the same auth and metering path as /api/v1/adlibrary. Full parameter context for the ad library route lives in Biblioteca de anuncios de Meta.
- Clave API:
Clave X-API,Autorización: al portador, o?api_key=(véase Referencia de la API). - Sesión: Si el visitante ya ha iniciado sesión, las mismas rutas pueden ejecutarse sin clave; no obstante, el usuario activo debe cumplir con la comprobación de acceso a la API que se indica a continuación.
- Plan: La cuenta debe incluir Acceso a la API. De lo contrario
403. - Créditos / límite de velocidad: Créditos mensuales de API y 60 solicitudes por minuto por usuario. Una vez agotado,
429con un error JSON y opcionalcréditosobjeto.
Cuando utilizas una clave API sin una sesión de navegador activa, el servidor sigue asociando la clave a tu cuenta para esa solicitud, de modo que el comportamiento coincide con el del panel de control.
GET /api/v1/marcas — Tracked brands list (API key)
Returns the same tracked-brands list you see in the app’s Brand tracker, scoped to the API key owner.
Query parameters
| Parámetro | Por defecto | Descripción |
|---|---|---|
clasificar |
date_added |
date_added, nombre, new_ads, growth |
buscar |
'' |
Case-insensitive match on brand name or page id |
board_id |
— | If set, only brands on that saved board (must belong to the user) |
Response
JSON array of brand rows (not wrapped in { success, data }). Each item includes fields such as id (Facebook page id), nombre, logo_url, added_at, page_url, status, total_ads, active_ads_on_page, formats, new_ads_count, new_ads_change, and related summary fields (same shape as the in-app list).
Brand details (GET /api/brands/*) — session / logged-in
These routes require a logged-in browser session (except GET /api/brands/shared-board, which uses a token). They are no the metered API-key list — that is GET /api/v1/marcas only. Automating detail tabs means driving the app with session cookies, not the API key alone.
Brand identifier: Almost all detail endpoints take id = Facebook page_id (same as id in the brands list).
Track / untrack brands (session)
Yes — you can both track and remove brands in the Brand tracker, using session-authenticated routes:
Track a brand
POST /api/brands/follow
JSON body:
{ "url": "https://www.facebook.com/ads/library/?view_all_page_id=108897621643793" }
Notas:
- Requires a logged-in session and plan capacity.
- Devoluciones
éxito, además debrand,has_data, ydetails_urlwhen accepted.
Remove a tracked brand
POST /api/brands/unfollow
JSON body:
{ "page_id": "108897621643793" }
Notas:
- Removes the brand from your tracker.
- Also removes that brand from your boards for the current user.
- Devoluciones
éxito,amount, ymax_allowed.
Count tracked brands
GET /api/brands/amount-tracked returns:
amount- number of brands currently tracked by the logged-in user.max_allowed- plan cap for Brand tracker.
Date range filter (many detail tabs)
Query parameters map as follows:
fecha_rango |
Significado |
|---|---|
(absent) o todos |
No date filter |
en directo |
Last seen in the last 3 days (actualizado el field) |
7d, 30d, 3m, 6m |
Ads with start date on or after the rolling cutoff (comenzó field) |
personalizado |
Requires fecha_de_inicio y fecha_hasta como A-M-D |
Used directly by GET /api/brands/ads. The same filter applies to other brand insight tabs (ad copies, headlines, hooks, personas, themes, …): pass the same fecha_rango / fecha_de_inicio / fecha_hasta query params on those endpoints.
Example: paginated ads for one brand
GET /api/brands/ads?id={page_id}&page={n}
página: 0-based page index (12 ads per page).- Optional date filter:
fecha_rango,fecha_de_inicio,fecha_hastaas above. - Response: JSON array of processed ad objects.
Other detail endpoints — common query parameters
| Parámetro | Where it applies |
|---|---|
id |
Marca page_id on ads, ad-hooks, ad-copies, ad-headlines, personas, themes, angles, desires, emotions, awareness-stages, funnel-stages, usps, landing-pages, and similar get* methods. |
página |
Ads list: 0-based, 12 ads/page. Many other tabs use 1-based pagination (typically 20 rows per page). |
clasificar, buscar |
Text / insight tabs; default Uso or method-specific (see each handler). |
fecha_rango, fecha_de_inicio, fecha_hasta |
Any tab that supports the date filter (same semantics as the table above). |
view=eu |
Cuando view is eu, EU-specific field variants and search behavior apply. |
GET /api/brands/ads-by-ids |
ids — comma-separated ad ids. |
GET /api/brands/search |
q — search string. |
GET /api/brands/ads-launched |
min, máximo (date strings), metric: ads_launched (default), spend, alcanzar (spend/reach EU-oriented per code comments). |
GET /api/brands/shared-board |
token, buscar, clasificar — public share link; no login cookie required. |
GET /api/brands/download-landing-screenshot |
url — target page URL to capture. |
Brand-related routes are also summarized in the API reference.