The ad-data layer for your platform
Onboard your users' ad accounts through a hosted, Omesta-branded flow — then read their campaign performance, leak findings, and AI recommendations through a workspace-scoped API. Read-only by default, guarded writes when you need them.
POST /api/platform/v1/connect-sessions
Authorization: Bearer omk_live_…
{ "external_ref": "user_8123",
"return_url": "https://yourapp.com/ads/connected" }
→ { "connect_url": "https://omestasystems.com/connect/c/ocs_…",
"expires_at": "2026-06-22T12:00:00Z" }One integration, the whole revenue-recovery stack
Everything Omesta does for a merchant, exposed to your product through scoped keys with hard cost caps.
Hosted connect flow
Send your users through an Omesta-branded page to attach their Meta, Google, and TikTok ad accounts. One POST, one URL — no OAuth plumbing on your side.
Workspace-scoped data
Every key resolves only to the workspaces your platform provisioned. Campaigns, spend, and performance for your users' own accounts — nothing else is reachable.
Leak detection + audits
Run Omesta's 147-pattern leak engine on a connected workspace and read the surfaced dollar value: ad waste, attribution gaps, failed-payment loss.
AI endpoints
Ad-strategist recommendations and leak fixes, behind a scoped key with hard monthly cost caps so an integration can never run up the bill.
Guarded write actions
Pause, resume, and budget changes route through Omesta's executor — learning-phase protection, budget clamps, and a full audit trail. Gated behind review.
Usage + rotation built in
Per-key usage tracking, quotas, and one-call rotation. Your developer console shows request volume, error rates, and workspace stats in real time.
Provision once. Read everything.
Create a connect session, hand the URL to your user, and the moment they finish you can read their campaigns, metrics, ad-sets, audiences, leaks, and AI recommendations — all scoped to the workspace you created.
- REST + JSON, Bearer-key auth
- Workspace-scoped — never cross-tenant
- Hard monthly cost caps on AI + audit calls
- Per-key usage, quotas, one-call rotation
GET /api/platform/v1/workspaces/{ref}/campaigns
Authorization: Bearer omk_live_…
→ { "data": [
{ "id": "120249…", "name": "Retargeting · warm",
"platform": "meta", "spend": 4076,
"results": 163, "cpa": 25.0 } ],
"workspace": "ws_3a9f…" }Invite-only, on purpose
You're touching other people's ad accounts and spend. There is no self-serve key — every developer is reviewed and signs the agreement first.
Apply
Tell us what you're building and which scopes you need. Takes two minutes.
Human review
Every application is reviewed by a person — no auto-approval, no self-serve keys.
Sign the agreement
Approved developers click-wrap the Omesta Developer Agreement (versioned, evidenced).
Get your key
Your omk_live_ key reveals once in the console, with usage charts and docs alongside.
Request a developer key
Invite-only while we onboard early partners. Each application is reviewed by a human; approved developers sign the Omesta Developer Agreement before keys are issued.
Questions? support@omestasystems.com · Already a developer? Open the console →
The standard for revenue recovery. Protecting payments, attribution, and ad spend.
As featured in
See all 500+ features →© 2026 Omesta Systems. All rights reserved.