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 Supply Partners API

The Supply Partners API from Rubicon Project — 2 operation(s) for supply partners.

Rubicon Project Supply Partners 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 Supply Partners. 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 5 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 0.1.0.

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

5 operations 2 paths 0 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

Rubicon Project Supply Partners 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 5

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

Supply Partners 5
GET
/api/v0/supply_partners
Index
supply_partners_get 3 params → 200
POST
/api/v0/supply_partners
Create
supply_partners_post body → 201
GET
/api/v0/supply_partners/{id}
Show
supply_partners_id_get 1 param → 200
PUT
/api/v0/supply_partners/{id}
Update
supply_partners_id_put 1 param body → 200
DELETE
/api/v0/supply_partners/{id}
Destroy
supply_partners_id_delete 1 param → 204

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rubicon-project-supply-partners-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 Supply Partners 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.