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

Magnite Postal Code Lists API

The Postal Code Lists API from Magnite — 6 operation(s) for postal code lists.

Magnite Postal Code Lists API is one of 77 APIs that Magnite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

12 operations 6 paths 4 schemas 2 DELETE6 GET1 PATCH2 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
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Magnite Postal Code Lists 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 12

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

Postal Code Lists 12
GET
/api/v0/postal_code_lists
Index
postal_code_lists_get 3 params → 200
POST
/api/v0/postal_code_lists
Create
postal_code_lists_post body → 201
GET
/api/v0/postal_code_lists/{id}
Show
postal_code_lists_id_get 1 param → 200
PUT
/api/v0/postal_code_lists/{id}
Update
postal_code_lists_id_put 1 param body → 200
DELETE
/api/v0/postal_code_lists/{id}
Destroy
postal_code_lists_id_delete 1 param → 204
GET
/api/v1/postal_code_lists
Index
postal_code_lists_get 7 params → 200
POST
/api/v1/postal_code_lists
Create
postal_code_lists_post body → 201422
GET
/api/v1/postal_code_lists/{id}
Show
postal_code_lists_id_get 1 param → 200
PATCH
/api/v1/postal_code_lists/{id}
Update
postal_code_lists_id_patch 1 param body → 200422
DELETE
/api/v1/postal_code_lists/{id}
Delete
postal_code_lists_id_delete 1 param → 204
GET
/api/v1/postal_code_lists/permissions
Collection Permissions
postal_code_lists_permissions_get → 200
GET
/api/v1/postal_code_lists/{id}/permissions
Permissions Member
postal_code_lists_id_permissions_get 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are PostalCodeListResponse (8 properties), PostalCodeListUpdateRequest (4 properties), PostalCodeListCreateRequest (3 properties), PostalCodeListErrorResponse (2 properties). Each schema is shown below with its type and property counts.

PostalCodeListResponse
object
8 properties
PostalCodeListCreateRequest
object
3 properties 1 required
PostalCodeListErrorResponse
object
2 properties
PostalCodeListUpdateRequest
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magnite-postal-code-lists-api-openapi.yml Raw ↑

Other APIs Magnite publishes across the network.

Magnite Account Partner Segments API
Magnite Accounts API
Magnite Advertiser Domain Lists API
Magnite App Bundle Lists API
Magnite App Name Lists API
Magnite Audiences API
Magnite Audios API
Magnite Auth API
Magnite Bid Maps API
Magnite Bills API
Magnite Campaigns API
Magnite Changelogs API
Where this information came from

This is an independent, third-party profile of Magnite Postal Code Lists 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.