Ad account detail

GET /api/marketing/ad-accounts/{id}

:id is the Neike uuid, not Meta’s act_…. An account of another client answers 404. Requires the marketing:read scope.

Authentication

Send your API key in the x-neike-api-key header. Console sessions can use a bearer JWT plus x-neike-client-id instead.

Responses

Status	Description	Schema
200	—	AdAccountDto

Example

curl -X GET https://api.neike.dev/api/marketing/ad-accounts/{id} \
  -H "x-neike-api-key: whk_live_…"

AdAccountDto

Field	Type		Description
id	string	required	Account id in Neike (uuid).
provider	meta	required	Ads provider of the account. Today there is only one: meta.
ad_account_id	string	required	Account id in Meta, with prefix. Example: "act_123456789".
account_id	string	required	The same id without the act_ prefix. Example: "123456789".
name	string	required	Example: "Cuenta principal".
currency	string	required	Account currency in Meta. Example: "ARS".
timezone_name	string	required	Example: "America/Argentina/Buenos_Aires".
account_status	number	required	Meta numeric enum (1 = active, 2 = disabled…). Example: 1.
account_status_label	string	required	The same status as text, already translated. Example: "active".
business_id	string	optional	—
business_name	string	optional	—
status	available · active · disabled · revoked	required	Status in Neike: available (connected, not yet chosen), active (operable), disabled (paused by the client) or revoked (Meta invalidated the token).
last_synced_at	string (date-time)	required	—
created_at	string (date-time)	required	—