Getting your API key

Register your app or site first

Before an API key means anything, you register the property you're monetizing — its name, URL, category, and country. Your first API key is generated automatically at the end of this registration; you don't request one separately as a first step.

Verify your domain or app

A newly registered property starts in PENDING status and won't be served real campaigns yet. Verify ownership by adding a DNS TXT record at _adscod-verify.<yourdomain> matching the token shown in your dashboard, then confirm — this is what flips your status to ACTIVE. Your dashboard's onboarding checklist tracks this as a required step, not an optional one.

Managing API keys

Your account supports multiple named API keys, not just one — create additional keys from API Settings (e.g. one per app or environment), see how many are active, and revoke any individual key independently without affecting the others. Each key is shown in full only once, at creation — store it immediately.

No SDK required

You can call the serve endpoint with plain HTTP from any language — no SDK installation required. That said, a maintained React SDK and a drop-in script embed also exist if you'd rather not hand-write the fetch/render pipeline yourself; see Rendering native ad formats.

Keeping your key safe

• Never expose your API key in client-side JavaScript — call the serve endpoint from your server
• Revoke a specific key from API Settings if you suspect it's been exposed — your other keys keep working
• Each key is tied to your publisher account and earnings ledger

Next step

Once your domain is verified and you have a key, head to the serve endpoint guide to make your first request.