Skip to content
Get started
Docs

The API is in private beta with the first ten workspaces

Everything the product does, it does over this API — cards, authorisation webhooks, the AdGrid schema and the close export. Nothing is published yet: leave an address and we send the reference plus a sandbox key.

Cards

Private beta

Issue a card against an ad account, move caps, freeze and delete. Caps are enforced at authorisation, not in a nightly job.

POST /v1/cards
{
  "ad_account": "meta:4829-1174",
  "holder": "rosa@vertex.mx",
  "daily_cap": 120000,
  "currency": "USD",
  "mcc_allow": ["7311"]
}

Authorisations

Private beta

A webhook per authorisation, approved or declined, with the reason and the card that carried it. Signed with your workspace secret.

POST https://your-app/hooks/palanca
{
  "type": "authorisation.declined",
  "card": "•• 2185",
  "amount": 31000,
  "merchant": "TikTok Ads · MX",
  "reason": "over_daily_cap"
}

AdGrid

Design

Read spend, ROAS and CPM per campaign across five networks on one schema, or write a daily budget back.

GET /v1/adgrid?window=30d&network=meta
PATCH /v1/adgrid/campaigns/8841
{ "daily_budget": 145000 }

Close

Design

Pull the matched period: invoice, card transaction, FX difference and the CFDI or Nota Fiscal reference.

GET /v1/close/2026-09
-> 148 transactions, 5 invoices, 1 fx_adjustment

Amounts are integers in the smallest unit of the settlement currency. Every endpoint is idempotent on the Idempotency-Key header, and the sandbox issues cards that decline everything outside MCC 7311 so you can test the failure path first.