API Concepts

A short orientation to how the Vibe Developer Platform API is shaped. Read this once before integrating; come back to the linked References when you need details.

Object model

Vibe's resources form a tree:

graph TD
    Account --> Advertiser
    Advertiser --> Campaign
    Advertiser --> Creative
    Advertiser --> Audience
    Advertiser --> ImpressionTracker
    Campaign --> Strategy
    Strategy --> CA[Creative associations]
    Audience --> AudienceSync
    AudienceSync --> Batch

And two read-only catalogs you'll query while building a Strategy's targeting:

  • Channels — CTV apps and channels.
  • Interest segments — audience taxonomies.

Identifiers

ObjectID type
Accountinteger
AdvertiserUUID
CampaignUUID
StrategyUUID
CreativeUUID
AudienceUUID
AudienceSyncUUID

Conventions in one place

Every API call shares the same contract. The details live in their own pages:

Errors

Vibe API endpoints return errors in a uniform JSON envelope:

{
  "error": {
    "type": "Bad Request",
    "message": "Missing or invalid account_id query parameter.",
    "status": 400,
    "detail": null,
    "request_id": "ec7cc78b-00ec-4883-bee1-5188b28635aa",
    "doc_url": null
  }
}
FieldDescription
typeShort error classifier.
messageHuman-readable description.
statusHTTP status code.
detailStructured context for the error, or null.
request_idInclude this value in any support request — it lets Vibe trace the call.
doc_urlLink to the relevant docs page when applicable.

Common status codes:

StatusMeaning
400Malformed request — bad JSON, missing required header, wrong content-type, unknown revision.
401Missing or invalid token.
403Authenticated but the token lacks the required scope.
404Resource doesn't exist or isn't visible to your tenant.
409Conflict — operation isn't valid in the resource's current state.
422Well-formed request that failed semantic validation. See detail.
500Unexpected server error. Retry with exponential backoff.

OAuth endpoints (/oauth2/auth, /oauth2/token) follow standards-compliant OAuth error shapes per RFC 6749, not this envelope. See OAuth.

Testing

Use a dedicated test Advertiser within your real Vibe account to keep test data isolated from production at this time.