Skip to main content

​
What this is

Targeter’s partner API (under API) is how external systems call Targeter. This section is the other direction: how Targeter calls your API. It is the ideal contract for publishers, media houses, and ad platforms that Targeter creates ads on and pulls reporting from. If you implement these endpoints, Targeter can onboard your inventory without a custom adapter for every function.

​
Base URL

All requests are made to the host you provide during setup:
Use snake_case JSON, UTC ISO 8601 timestamps for ad flights, YYYY-MM-DD for insight windows, and ISO 4217 currency codes.

​
Authentication

Targeter sends a token you issue during integration setup:

​
Ideal functions

Targeter expects this set of operations. Implement all of them unless a function is marked optional during onboarding.
  • Create office — create a broker/advertiser office; you generate office_id
  • Get office ID — resolve an existing office to its office_id
  • Create ad — create an ad under a Targeter campaign
  • Update ad — change budget, dates, targeting, creatives, or platforms
  • Delete ad — permanently remove an ad
  • Pause ad — stop delivery without deleting
  • Resume ad — restart a paused ad
  • Get ad status — return current delivery status

​
Typical flow

​
Errors

Match Targeter’s partner API: HTTP status codes plus a JSON body.
Use 401 for missing or invalid tokens, 404 when an office or ad does not exist, and 409 when the current ad status does not allow the requested action.