Concepts

Workspace and the acting person

Every key belongs to one workspace and acts as the person who created it. What a request may do is the overlap of two things, both read live on every request: the key has the operation scope, and the person role allows the action. Demote the person and the key narrows with them; if they leave, the key stops (401 key_owner_inactive) until an owner or admin takes it over in Settings.

Approvals

Nora asks before she acts when the workspace is set up that way. A key with approvals:decide counts as its creator saying yes, and every decision is recorded as made through that key.

The rules every send follows

• Consent: nothing goes to a contact without a recorded lawful basis.
• Do-not-contact: email addresses, phone numbers, company domains, LinkedIn URLs and erased people are never contacted.
• Quiet hours: calls, texts and WhatsApp wait for daytime in the contact time zone.
• Pausing all outreach stops every operation that reaches people (409 outreach_paused).

Nora makes the plans, pages and ads

There is no operation that writes an ad, generates creatives, searches reference ads or builds a page from nothing. New ads and pages are born in a plan; the API lets you edit, approve, publish and manage what Nora made.

Report on ads

GET /ads/insights gives spend, results, cost per result and ROAS by day, campaign or network, from the hourly syncs the Ads pages read. Money is integer minor units with its currency, one row per currency; numbers a network didn't report are null, never 0.