How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

MediaMath Targeting API

Targeting

MediaMath Targeting API is one of 46 APIs that MediaMath publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Targeting. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.

This API exposes 20 operations across 13 paths, and defines 22 schemas. It is described by OpenAPI 3.0.0, at version 3.0.1807.

Requests are made against a single base URL, https://api.mediamath.com/api/v3.0.

20 operations 13 paths 22 schemas 2 DELETE10 GET7 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.0.1807
Base URL
https://api.mediamath.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

MediaMath Targeting API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (Auth0) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

Paths & Operations 20

Across 13 paths, the API surfaces 20 operations — 2 DELETE, 10 GET, 7 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Targeting 20

Targeting

GET
/target
(Legacy) List Targets
list-targets-legacy 4 params → 200400401403
POST
/target
(Legacy) Create a Target
create-target-legacy body → 201400401403
GET
/target/{target_id}
(Legacy) Get a Target
get-target-legacy 1 param → 200400401403404
POST
/target/{target_id}
(Legacy) Update a Target
update-target-legacy 1 param body → 200400401403404
DELETE
/target/{target_id}
(Legacy) Delete a Target
delete-target-legacy 1 param → 200400401403404
PUT
/target/{target_id}
(Legacy) Update a Target
put-update-target-legacy 1 param body → 200400401403404409
GET
/targets
List targets
list-targets 4 params → 200400401403
POST
/targets
Create a Target
create-target body → 201400401403404
GET
/targets/{target_id}
Get a Target
get-target 1 param → 200400401403404
POST
/targets/{target_id}
Update a Target
update-target 1 param body → 200400401403404409
DELETE
/targets/{target_id}
Delete a Target
delete-target 1 param → 200400401403404
GET
/target-path
List Target paths
list-target-paths-legacy 4 params → 200400401403
POST
/targeting
Add and View Targeting
add-view-targeting body → 200207400401403
POST
/contextual_segments/cpm_estimate
Contextual Segments CPM estimates
contextual-segments-cpm-estimate 1 param body → 200400401403
GET
/targeting_segments/frequently_used
Get Frequently Used Contextual Segments
get-targeting-segments-frequently-used 2 params → 200400401403404
GET
/audience_segments/frequently_used
Frequently Used Audience Segments
get-audience-segments-frequently-used 3 params → 200400401403
POST
/audience_segments/cpm_estimate
Audience Segments CPM Estimate
audience-segments-cpm-estimate 1 param body → 200400401403
GET
/technology_target_values
List Technology Target Values
list-technology-target-values 5 params → 200400401403
GET
/path_targeting_segments
List Contextual Segments
list-contextual-segments 6 params → 200400401403404
GET
/path_audience_segments
List Path Audience Segments
list-path-audience-segments 9 params → 200400401403404

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are path_audience_segment (17 properties), location_response (13 properties), audience_vendor (12 properties), target_update (10 properties). Each schema is shown below with its type and property counts.

path_audience_segment
object
17 properties
error_response
object
2 properties 2 required
target_update
object
10 properties
target_create
target_dimension_include
object
3 properties 3 required
audience_vendor
object
12 properties
audience_target
object
2 properties
contextual_segment_collection
object
2 properties
contextual_segment_collection_full
object
2 properties
cpm
object
2 properties
list_metadata
object
6 properties 2 required
contextual_segment_short
object
7 properties
single_metadata
object
1 property 1 required
day_part
object
4 properties 3 required
audience_segments_group
object
2 properties
target_dimension_exclude
object
3 properties 1 required
targeting_base
object
6 properties
location_response
object
13 properties 13 required
target_base
object
9 properties 1 required
contextual_segment_full
path_audience_segments_collection_full
object
2 properties
audience_segment_short
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mediamath-targeting-api-openapi.yml Raw ↑

Other APIs MediaMath publishes across the network.

MediaMath Marketplaces API V2.0
MediaMath Bring Your Own Algorithm (BYOA) API
MediaMath Audience Onboarding API
MediaMath Server-to-Server Data Distribution API
MediaMath Ad Servers API
MediaMath Advertisers API
MediaMath Agencies API
MediaMath Atomic Creatives API
MediaMath Audience Vendors API
MediaMath Campaign Plans API
MediaMath Campaigns API
MediaMath Campaigns Budget Flights API
Where this information came from

This is an independent, third-party profile of MediaMath Targeting API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.