Magnite First Party Partner Segments API

The First Party Partner Segments API from Magnite — 2 operation(s) for first party partner segments.

Operations 2

DELETE /api/v0/first_party_partner_segments/{id} Destroy #
POST /api/v0/first_party_partner_segments/bulk_create Bulk Create #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/magnite-first-party-partner-segments-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

magnite-first-party-partner-segments-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SpringServe UI API (V0) First Party Partner Segments API
  version: 0.1.0
  description: '> **_NOTE:_** This document covers the v0 API (`/api/v0`).'
security:
- api_key: []
- bearer_token: []
tags:
- name: First Party Partner Segments
paths:
  /api/v0/first_party_partner_segments/{id}:
    parameters:
    - name: id
      in: path
      required: true
      schema:
        type: string
    delete:
      summary: Destroy
      responses:
        '204':
          description: No content
      tags:
      - First Party Partner Segments
      operationId: first_party_partner_segments_id_delete
  /api/v0/first_party_partner_segments/bulk_create:
    post:
      summary: Bulk Create
      requestBody:
        content:
          application/json:
            schema:
              type: object
            examples:
              single:
                $ref: '#/components/examples/first_party_partner_segment_bulk_create_single'
              multiple:
                $ref: '#/components/examples/first_party_partner_segment_bulk_create_multiple'
        required: true
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
      tags:
      - First Party Partner Segments
      operationId: first_party_partner_segments_bulk_create_post
components:
  examples:
    first_party_partner_segment_bulk_create_multiple:
      summary: Bulk create — multiple items
      value:
        first_party_partner_segments:
        - code: SEG-001
          vendor_id: 1
          category: automotive
          dmp_segment_id: 1
          description: First party segment
          cpm: 1.11
          political: false
          adv_id: 1
          enabled: true
          account_ids:
          - 1
        - code: SEG-002
          vendor_id: 1
          category: sports
          dmp_segment_id: 1
          description: Second first party segment
          cpm: 1.11
          political: false
          adv_id: 1
          enabled: false
          account_ids: []
    first_party_partner_segment_bulk_create_single:
      summary: Bulk create — single item
      value:
        first_party_partner_segments:
        - code: SEG-001
          vendor_id: 1
          category: automotive
          dmp_segment_id: 1
          description: First party segment
          cpm: 1.11
          political: false
          adv_id: 1
          enabled: true
          account_ids:
          - 1
  securitySchemes:
    api_key:
      type: apiKey
      in: header
      name: Authorization
      description: SpringServe authorization token based authentication.
    bearer_token:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 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 will be automatically set if you run the example for /api/v0/auth or /api/v1/auth