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

Bird Preferences API

Stated messaging preferences (consent grants and opt-outs) recorded per handle across email, SMS, and WhatsApp, with causally ordered writes.

Bird Preferences API is one of 65 APIs that Bird publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Preferences. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

This API exposes 5 operations across 3 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://{region}.platform.bird.com, https://platform.bird.com, http://localhost:8080.

5 operations 3 paths 18 schemas 1 DELETE3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.bird.com
Authentication
HTTP Bearer, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 4

Bird Preferences API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). An API key is passed in the cookie as bird_session (CookieAuth). An API key is passed in the header as X-Realtime-Key (RealtimeKey). An API key is passed in the header as X-Realtime-Secret (RealtimeSecret). By default, every request must be authenticated.

  • BearerAuth — Pass the API key as a bearer token in the Authorization header. Keys use the format bk{region}. The prefix identifies the region and selects the API endpoint.…
  • CookieAuth — Session cookie set after signing in to the Bird dashboard. The cookie value is an opaque session token; no session data is stored in the cookie itself.
  • RealtimeKey — The Realtime app key. Together with X-Realtime-Secret, it authenticates a request to the Realtime API in addition to the workspace credential. Both values come…
  • RealtimeSecret — The Realtime app secret paired with X-Realtime-Key. The API returns the secret only when the key is created and does not store it. Create a new key and revoke…

Paths & Operations 5

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

Preferences 5

Stated messaging preferences (consent grants and opt-outs) recorded per handle across email, SMS, and WhatsApp, with causally ordered writes.

GET
/v1/contacts/{contact_id}/preferences
List a contact's preferences
listContactPreferences 4 params → 200401403404422429500
GET
/v1/preferences
List preferences
listPreferences 5 params → 200401403422429500
POST
/v1/preferences
Record a preference
createPreference 1 param body → 200201400401403422429500
GET
/v1/preferences/{preference_id}
Get a preference
getPreference 1 param → 200401403404422429500
DELETE
/v1/preferences/{preference_id}
Delete a preference
deletePreference 2 params → 200401403404422429500503

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are ErrorBody (11 properties), PreferenceStatement (6 properties), NextAction (5 properties), _ListEnvelope (3 properties). Each schema is shown below with its type and property counts.

_ListEnvelope
object
3 properties 3 required
ContactID
string
ErrorDetail
object
2 properties 2 required
PreferenceCoverage
string
How much traffic the statement covers. nontransactional covers marketing and other non-essential messages while transactional messages such as receipts and ver…
ErrorBody
object
11 properties 6 required
Preference
One person's current stated preference for one channel: whether they have consented to or opted out of receiving messages at a handle, and how much traffic the…
PreferenceOrigin
string
How the statement was made. Statements the person made themselves (unsubscribelink, unsubscribeevent, keyword, preferencepage) carry more weight than ones asse…
NextAction
object
5 properties 2 required
Timestamps
object
2 properties 2 required
PreferenceWriteResult
object
The outcome of one preference write or delete. applied: true means the request took effect: either it changed the record, or an identical statement already had…
3 properties 3 required
PreferenceID
string
PreferenceStatement
object
6 properties 2 required
PreferenceTransitionID
string
Error
object
1 property 1 required
PreferenceStatus
string
What the statement says: granted records consent to receive messages, revoked records an opt-out. There is no third state: a person who never stated anything s…
PreferenceChannel
string
The channel a preference statement applies to. A preference addresses one channel: the handle that identifies the person differs per channel, so opting out of…
PreferenceCreate
Records one preference statement for a handle. Writing is an upsert by key (channel, handle, sender scope, and topic), and statements are causally ordered: a s…
PreferenceList

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bird-preferences-api-openapi.yml Raw ↑

Other APIs Bird publishes across the network.

Bird Customer Data API
Bird Phone Numbers API
Bird Identity Verification API
Bird Touchpoints API
Bird Accounts API
Bird FAQ API
Bird Intent API
Bird SMS Messaging API
Bird Channels API
Bird Contacts API
Bird Conversations API
Bird Legacy MessageBird API
Where this information came from

This is an independent, third-party profile of Bird Preferences 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.