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

Rubicon Project Demand Tags API

The Demand Tags API from Rubicon Project — 17 operation(s) for demand tags.

Rubicon Project Demand Tags API is one of 78 APIs that Rubicon Project publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Demand Tags. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 26 operations across 17 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 4 base URLs: https://console.springserve.com/api/v0, https://console.clearline.magnite.com/api/v0, https://console.springserve.com/api/v1, https://console.clearline.magnite.com/api/v1.

26 operations 17 paths 6 schemas 3 DELETE14 GET1 PATCH6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://console.springserve.com/api/v1
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Rubicon Project Demand Tags API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (api_key). It accepts HTTP bearer tokens (JWT) (bearer_token). By default, every request must be authenticated.

  • api_key — SpringServe authorization token based authentication.
  • bearer_token — SpringServe authorization bearer token based authentication. This key is included in the response from the /api/v0/auth and /api/v1/auth endpoints. This key wi…

Paths & Operations 26

Across 17 paths, the API surfaces 26 operations — 3 DELETE, 14 GET, 1 PATCH, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Demand Tags 26
GET
/api/v0/demand_tags
Index
demand_tags_get 3 params → 200
POST
/api/v0/demand_tags
Create
demand_tags_post body → 201
GET
/api/v0/demand_tags/{id}
Show
demand_tags_id_get 1 param → 200
PUT
/api/v0/demand_tags/{id}
Update
demand_tags_id_put 1 param body → 200
DELETE
/api/v0/demand_tags/{id}
Destroy
demand_tags_id_delete 1 param → 204
GET
/api/v0/demand_tags/{demand_tag_id}/demand_tag_keys
Index
demand_tags_demand_tag_id_demand_tag_keys_get 4 params → 200
POST
/api/v0/demand_tags/{demand_tag_id}/demand_tag_keys
Create
demand_tags_demand_tag_id_demand_tag_keys_post 1 param body → 201
GET
/api/v0/demand_tags/{id}/duplicate
Duplicate
demand_tags_id_duplicate_get 1 param → 200
GET
/api/v0/demand_tags/{demand_tag_id}/demand_tag_keys/{id}
Show
demand_tags_demand_tag_id_demand_tag_keys_id_get 2 params → 200
PUT
/api/v0/demand_tags/{demand_tag_id}/demand_tag_keys/{id}
Update
demand_tags_demand_tag_id_demand_tag_keys_id_put 2 params body → 200
DELETE
/api/v0/demand_tags/{demand_tag_id}/demand_tag_keys/{id}
Destroy
demand_tags_demand_tag_id_demand_tag_keys_id_delete 2 params → 204
GET
/api/v1/demand_tags
Index
demand_tags_get 15 params → 200
POST
/api/v1/demand_tags
Create
demand_tags_post body → 201422
GET
/api/v1/demand_tags/{id}
Show
demand_tags_id_get 5 params → 200404
PATCH
/api/v1/demand_tags/{id}
Update
demand_tags_id_patch 1 param body → 200
DELETE
/api/v1/demand_tags/{id}
Delete
demand_tags_id_delete 1 param body → 204
POST
/api/v1/demand_tags/bulk_update
Update Multiple Demand Tags
demand_tags_bulk_update_same_attributes_post body → 200400
GET
/api/v1/demand_tags/download
Download CSV
demand_tags_download_get 2 params → 200400401
POST
/api/v1/demand_tags/macro_suggester
Suggest VAST endpoint macros
demand_tags_macro_suggester_post body → 200
GET
/api/v1/demand_tags/new
Get defaults for a new Demand Tag
demand_tags_new_get 3 params → 200
GET
/api/v1/demand_tags/permissions
Permissions Collection
demand_tags_permissions_get → 200
GET
/api/v1/demand_tags/{id}/creatives_summary
Creatives Summary
demand_tags_id_creatives_summary_get 4 params → 200
GET
/api/v1/demand_tags/{id}/duplicate
Duplicate Demand Tag
demand_tags_id_duplicate_get 2 params → 200404
GET
/api/v1/demand_tags/{id}/permissions
Permissions Member
demand_tags_id_permissions_get 1 param → 200
POST
/api/v1/demand_tags/bulk/update
Update Multiple Demand Tags
demand_tags_bulk_update_many_post body → 204200400422
GET
/api/v1/demand_tags/new_from_forecast/{id}
New From Demand Forecast
demand_tags_new_from_forecast_id_get 2 params → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are DemandTagCreateRequest (9 properties), DemandTagPriority (6 properties), MacroSuggesterRequest (4 properties), MacroSuggesterResponse (2 properties). Each schema is shown below with its type and property counts.

DemandTagResponse
object
Demand Tag schema based on DemandTagSerializer for V1 API
DemandTagCreateRequest
object
9 properties
DemandTagIndexResponse
MacroSuggesterRequest
object
4 properties
MacroSuggesterResponse
object
2 properties
DemandTagPriority
object
Supply tag priority assignment for a demand tag
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rubicon-project-demand-tags-api-openapi.yml Raw ↑

Other APIs Rubicon Project publishes across the network.

Magnite Exchange API (xAPI) OpenRTB Extensions
Rubicon Project Account Partner Segments API
Rubicon Project Accounts API
Rubicon Project Advertiser Domain Lists API
Rubicon Project App Bundle Lists API
Rubicon Project App Name Lists API
Rubicon Project Audiences API
Rubicon Project Audios API
Rubicon Project Auth API
Rubicon Project Bid Maps API
Rubicon Project Bills API
Rubicon Project Campaigns API
Where this information came from

This is an independent, third-party profile of Rubicon Project Demand Tags 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.