Tremor Video DSP is the demand-side platform originally built by Tremor Video and Tremor International; following the consolidation of Tremor Video DSP and Amobee it is now marketed as the Nexxen DSP, part of the unified Nexxen advertising stack (DSP, SSP, Ad Server and Data Platform). It offers a REST API for programmatic and connected-TV (CTV) advertising operations, letting partners manage advertisers, insertion orders, packages, line items, ads, creatives, audience segments, inventory and publisher deals, plus read-only device and geographic reference services and an asynchronous reporting service. The four services sit behind one gateway at services.amobee.com and share a single OAuth2 client-credentials bearer token. Nexxen publishes no OpenAPI; the machine-readable contract is a public Postman collection of 94 requests with 75 saved response examples, and API credentials are provisioned inside an existing DSP contract.
Tremor Video is listed with 5 APIs on the APIs.io network, including Nexxen DSP API, Nexxen DSP Token Service, Nexxen DSP Reporting API, and 2 more. Tagged areas include Company, MarTech, Advertising, AdTech, and DSP.
Tremor Video’s developer surface includes documentation, API reference, getting-started guide, authentication, code examples, engineering blog, support, and 21 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/tremor-video/"><img src="https://apis.io/badge/tremor-video/card.svg" alt="Tremor Video on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Typed Event Surface+6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
REST API for the Nexxen DSP (formerly Amobee / Tremor Video DSP) Campaign Management service — advertisers, insertion orders, packages, line items, ads, creatives, audience segm...
OAuth2 client-credentials token service for the Nexxen DSP APIs. A client POSTs its client_id and client_secret with grant_type=client_credentials as a JSON body and receives an...
Asynchronous reporting service for the Nexxen DSP. A report is submitted as a query (aggregationType, startTime/endTime, filters by objectType, optional S3 outputPath), answered...
Read-only reference service for the device taxonomy used in Nexxen DSP line-item targeting — device types, operating systems, manufacturers and individual devices, each listable...
Read-only geographic reference service for Nexxen DSP geo targeting — continents, countries, regions, cities, DMAs, named places and street addresses, each listable and retrieva...
aid: tremor-video
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: self-serve
trial: false
try_now: false
public: false
gated: none
gated_source:
- onboarding
label: Self-serve signup
confidence: medium
source:
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/tremor-video.png
name: Tremor Video
description: Tremor Video DSP is the demand-side platform originally built by Tremor Video and Tremor International; following
the consolidation of Tremor Video DSP and Amobee it is now marketed as the Nexxen DSP, part of the unified Nexxen advertising
stack (DSP, SSP, Ad Server and Data Platform). It offers a REST API for programmatic and connected-TV (CTV) advertising
operations, letting partners manage advertisers, insertion orders, packages, line items, ads, creatives, audience segments,
inventory and publisher deals, plus read-only device and geographic reference services and an asynchronous reporting service.
The four services sit behind one gateway at services.amobee.com and share a single OAuth2 client-credentials bearer token.
Nexxen publishes no OpenAPI; the machine-readable contract is a public Postman collection of 94 requests with 75 saved response
examples, and API credentials are provisioned inside an existing DSP contract.
url: https://raw.githubusercontent.com/api-evangelist/tremor-video/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- sapphire-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-13'
x-docs-platform: fern
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
x-enrichment:
date: '2026-08-13'
status: enriched
artifacts_added: 13
pass: local-v1
tags:
- Company
- MarTech
- Advertising
- AdTech
- DSP
- Programmatic
- CTV
- Video Advertising
tags_raw:
- Company
- Martech
- Advertising
- AdTech
- DSP
- Programmatic
- CTV
- Video Advertising
apis:
- name: Nexxen DSP API
description: REST API for the Nexxen DSP (formerly Amobee / Tremor Video DSP) Campaign Management service — advertisers,
insertion orders, packages, line items, ads, creatives, audience segments, retargeting segments, beacons, inventory lists,
publisher deals and location groups. OAuth2 client-credentials authentication; a shared JSON envelope of queryTotal /
data / errors / links; offset-limit pagination; marketId scoping with a 300 Multiple Choices disambiguation response.
Published as a public Postman collection rather than an OpenAPI.
humanURL: https://www.postman.com/nexxen-api/nexxen/documentation/9md8q3a/nexxen-dsp-apis
baseURL: https://services.amobee.com/campaign/v5/api
properties:
- type: Authentication
url: authentication/tremor-video-authentication.yml
- type: PostmanCollection
url: collections/tremor-video.postman_collection.json
- type: Examples
url: examples/tremor-video-examples.yml
- type: ErrorCatalog
url: errors/tremor-video-problem-types.yml
- type: RateLimits
url: rate-limits/tremor-video-rate-limits.yml
- name: Nexxen DSP Token Service
description: OAuth2 client-credentials token service for the Nexxen DSP APIs. A client POSTs its client_id and client_secret
with grant_type=client_credentials as a JSON body and receives an access_token used as a Bearer token on every other Nexxen
DSP service. It is the only service in the suite that does not itself require an access token.
humanURL: https://www.postman.com/nexxen-api/nexxen/documentation/9md8q3a/nexxen-dsp-apis
baseURL: https://services.amobee.com/accounts/v1/api
properties:
- type: Authentication
url: authentication/tremor-video-authentication.yml
- type: PostmanCollection
url: collections/tremor-video.postman_collection.json
- name: Nexxen DSP Reporting API
description: 'Asynchronous reporting service for the Nexxen DSP. A report is submitted as a query (aggregationType, startTime/endTime,
filters by objectType, optional S3 outputPath), answered with 202 Accepted and a report id on the Location header, then
polled for the result. Scoped to limited quick pulls: 19 months lookback, 300MB maximum output, 24-hour result retention,
and a published limit of 10,000 calls per day at 8 per second.'
humanURL: https://www.postman.com/nexxen-api/nexxen/documentation/9md8q3a/nexxen-dsp-apis
baseURL: https://services.amobee.com/reporting/v2/api
properties:
- type: Authentication
url: authentication/tremor-video-authentication.yml
- type: RateLimits
url: rate-limits/tremor-video-rate-limits.yml
- type: PostmanCollection
url: collections/tremor-video.postman_collection.json
- name: Nexxen DSP Device API
description: Read-only reference service for the device taxonomy used in Nexxen DSP line-item targeting — device types,
operating systems, manufacturers and individual devices, each listable and retrievable by id and filterable by its parent
in the hierarchy.
humanURL: https://www.postman.com/nexxen-api/nexxen/documentation/9md8q3a/nexxen-dsp-apis
baseURL: https://services.amobee.com/device/v1/api
properties:
- type: Authentication
url: authentication/tremor-video-authentication.yml
- type: PostmanCollection
url: collections/tremor-video.postman_collection.json
- name: Nexxen DSP Location API
description: Read-only geographic reference service for Nexxen DSP geo targeting — continents, countries, regions, cities,
DMAs, named places and street addresses, each listable and retrievable by id, with regions filtered by country, cities
and DMAs filtered by region, and free-text search on places and addresses.
humanURL: https://www.postman.com/nexxen-api/nexxen/documentation/9md8q3a/nexxen-dsp-apis
baseURL: https://services.amobee.com/location/v1/api
properties:
- type: Authentication
url: authentication/tremor-video-authentication.yml
- type: PostmanCollection
url: collections/tremor-video.postman_collection.json
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/tremor-video-domain-security.yml
- type: Website
url: https://nexxen.com/
- type: Documentation
url: https://www.postman.com/nexxen-api/nexxen/documentation/9md8q3a/nexxen-dsp-apis
- type: APIReference
url: https://www.postman.com/nexxen-api/nexxen/collection/9md8q3a/nexxen-dsp-apis
- type: GettingStarted
url: https://www.postman.com/nexxen-api/nexxen/collection/9md8q3a/nexxen-dsp-apis
- type: Postman
url: https://www.postman.com/nexxen-api/nexxen/
- type: Login
url: https://login.amobee.com/portal/amobee/dsp/login
- type: Authentication
url: authentication/tremor-video-authentication.yml
- type: Conventions
url: conventions/tremor-video-conventions.yml
- type: DataModel
url: data-model/tremor-video-data-model.yml
- type: Conformance
url: conformance/tremor-video-conformance.yml
- type: X-MCPServerCandidate
url: mcp/tremor-video-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Packages
url: packages/tremor-video-packages.yml
- type: LLMsTxt
url: llms/tremor-video-llms.txt
- type: Lifecycle
url: lifecycle/tremor-video-lifecycle.yml
- type: PostmanCollection
url: collections/tremor-video.postman_collection.json
- type: Examples
url: examples/tremor-video-examples.yml
- type: ErrorCatalog
url: errors/tremor-video-problem-types.yml
- type: RateLimits
url: rate-limits/tremor-video-rate-limits.yml
- type: Plans
url: plans/tremor-video-plans-pricing.yml
- type: AgentSkill
url: skills/_index.yml
- type: LLMsTxt
name: Provider-published llms.txt (verbatim)
url: llms/tremor-video-nexxen-llms.txt
- type: TermsOfService
url: https://nexxen.com/master-service-terms/
- type: PrivacyPolicy
url: https://nexxen.com/services-privacy-policy/
- type: Blog
url: https://nexxen.com/blog/
- type: Support
url: https://nexxen.com/contact-us/
- type: WellKnown
url: well-known/tremor-video-well-known.yml
- type: OAuthScopes
url: scopes/tremor-video-scopes.yml
Tremor Video API — frequently asked questions
Does Tremor Video have an API?
Yes. APIs.io lists 5 APIs from Tremor Video, including Nexxen DSP API, Nexxen DSP Token Service and Nexxen DSP Reporting API, and 2 more.
How do I authenticate with the Tremor Video API?
Tremor Video documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Tremor Video Authentication.
Is the Tremor Video API ready for AI agents?
Tremor Video has a Kin Score of 30.0 out of 100 (thin) and an Agent Readiness score of 20.5 (agent-aware), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: