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 Accounts API

The Accounts API from Rubicon Project — 23 operation(s) for accounts.

Rubicon Project Accounts 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 Account. 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 23 paths. 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 23 paths 0 schemas 16 GET1 PATCH8 POST1 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 Accounts 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 23 paths, the API surfaces 26 operations — 16 GET, 1 PATCH, 8 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Accounts 26
GET
/api/v0/accounts
Index
accounts_get 3 params → 200
GET
/api/v0/accounts/{id}
Show
accounts_id_get 1 param → 200
PUT
/api/v0/accounts/{id}
Update
accounts_id_put 1 param body → 200
GET
/api/v0/accounts/current
Get Current
accounts_current_get → 200
POST
/api/v0/accounts/{id}/set_current
Set Current
accounts_id_set_current_post 1 param → 200
GET
/api/v1/accounts
Index
accounts_get 7 params → 200
POST
/api/v1/accounts
Create
accounts_post body → 201
GET
/api/v1/accounts/{id}
Show
accounts_id_get 1 param → 200
PATCH
/api/v1/accounts/{id}
Update
accounts_id_patch 1 param body → 200
GET
/api/v1/accounts/current
Get the currently active account for the authenticated user
accounts_current_get → 200
GET
/api/v1/accounts/displayable
Get the accounts that the current user can select as their current account context
accounts_displayable_get → 200
GET
/api/v1/accounts/meta
Meta
accounts_meta_get → 200
GET
/api/v1/accounts/new
Get the defaults for a new account given an optional preset
accounts_new_get 1 param → 200
GET
/api/v1/accounts/permissions
Permissions Collection
accounts_permissions_get → 200
POST
/api/v1/accounts/{id}/bulk_connect_curators
Bulk DC Accounts (Curator)
accounts_id_bulk_connect_curators_post 1 param body → 200
POST
/api/v1/accounts/{id}/bulk_connect_dsps
Bulk DC Accounts (DSP)
accounts_id_bulk_connect_dsps_post 1 param body → 200
POST
/api/v1/accounts/{id}/bulk_set_dc_visibility
Bulk DC Accounts
accounts_id_bulk_set_dc_visibility_post 1 param body → 200
GET
/api/v1/accounts/{id}/curator_dc_accounts
DC Accounts (Curator)
accounts_id_curator_dc_accounts_get 1 param → 200
GET
/api/v1/accounts/{id}/dc_accounts
DC Accounts
accounts_id_dc_accounts_get 1 param → 200
GET
/api/v1/accounts/{id}/dsp_dc_accounts
DC Accounts (DSP)
accounts_id_dsp_dc_accounts_get 1 param → 200
GET
/api/v1/accounts/{id}/salesforce_sync
Salesforce Sync
accounts_id_salesforce_sync_get 1 param → 200
POST
/api/v1/accounts/{id}/set_current
Set Current
accounts_id_set_current_post 1 param → 200
GET
/api/v1/accounts/{id}/used_partner_segment_vendors
Used Partner Segment Vendors
accounts_id_used_partner_segment_vendors_get 1 param → 200
POST
/api/v1/accounts/bulk/update
Update Multiple Accounts
accounts_bulk_update_many_post body → 204200400422
POST
/api/v1/accounts/dvplus/{dvplus_id}/set_current
Set Current by Magnite DV+ ID
accounts_dvplus_dvplus_id_set_current_post 1 param → 200
GET
/api/v1/accounts/foreign_seat/{foreign_platform_name}/{foreign_seat_id}/white_label
Show for Account by Foreign Seat
accounts_foreign_seat_foreign_platform_name_foreign_seat_id_white_label_get 3 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rubicon-project-accounts-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 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
Rubicon Project Changelogs API
Where this information came from

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