What the API covers
The UluMob panel is built on the same REST API you can call. Requests and responses are JSON, and paths live under /api/v1.
| Area | What you can do |
|---|---|
| Campaigns | list, create, update, pause and resume, delete, block zones |
| Creatives | upload images, icons and video files, list them by folder |
| Filters | save and reuse targeting filters |
| Tracking | read your postback setup, edit conversion types, rotate the secret, list refused postbacks |
| Reports | group by date, country, format, OS, device, zone, campaign or ad, for up to 92 days per request |
| Billing | list transactions, start a card deposit |
| Publisher sites | add and verify sites, create zones, get tag code |
| Earnings | read earnings, manage payout methods, request a payout |
| Account | list and revoke API keys, read referral statistics |
API keys
Create keys from the account page in the panel, at /app/account. Give each key a name so you know which script uses it, and choose how long it lasts, from 1 to 3,650 days (365 by default). The key is shown once, then only its hash is stored.
Send it as a bearer token:
Authorization: Bearer <your key>
You can hold up to ten keys at a time and revoke any of them instantly. A key acts with your account's roles, so an advertiser key reaches advertiser endpoints and a publisher key reaches publisher endpoints.
Built for scripts that run unattended
- Validation you can act on: errors come back as JSON, and validation errors are
422with a message per field. - The same rules as the panel: bid floors per country, minimum daily budgets, pricing allowed per format and creative size limits are enforced identically.
- Safe deposits: card deposits require an
Idempotency-Keyheader, so a retried request never charges twice. - Review still applies: new campaigns and new or edited ads go to moderation before they serve.
- Rate limits: 120 requests a minute per user, enough for reporting jobs and bulk edits.
Common uses
Bid management. Pull yesterday's report grouped by zone, compare cost per conversion with your target, then raise bids on the zones that earn and add the rest to the campaign blacklist.
Reporting into your own tools. Export spend, impressions, clicks and conversions into a spreadsheet, a warehouse or a dashboard on a schedule, grouped the way your team reads them.
Campaign cloning. Create the same campaign for many countries from one template, each with its own per-country bid.
Publisher operations. Create zones for a new section of your site, fetch the tag code and check zone quality from your own deployment scripts.
Engine endpoints
Ad serving itself has separate public endpoints: the publisher tag, the delivery endpoint for custom integrations that return JSON, HTML, a redirect or a VAST wrapper, and the signed conversion postback. These need no API key. They are described alongside the REST API in the documentation.
Get a key
Create an account, open your account page and generate a key. The documentation lists every endpoint with its parameters and an example campaign payload. Questions about an integration go to [email protected].