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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Courier

Courier User Preferences API

The User Preferences API from Courier — 2 operation(s) for user preferences.

Documentation Provider Profile APIs.io OpenAPI GitHub

Courier User Preferences API is one of 22 APIs that Courier publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.courier.com.

3 operations 2 paths 11 schemas 2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.courier.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Courier User Preferences API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 3

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

User Preferences 3
GET
/users/{user_id}/preferences
Get user's preferences
users_preferences_list 2 params → 200400
GET
/users/{user_id}/preferences/{topic_id}
Get user subscription topic
users_preferences_get 3 params → 200404
PUT
/users/{user_id}/preferences/{topic_id}
Update or Create user preferences for a specific subscription topic
users_preferences_update 3 params body → 200400

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are UsersTopicPreference (6 properties), UsersTopicPreferenceUpdate (3 properties), Paging (2 properties), UsersUserPreferencesListResponse (2 properties). Each schema is shown below with its type and property counts.

UsersTopicPreference
object
6 properties 4 required
BaseError
object
1 property 1 required
ChannelClassification
string
Paging
object
2 properties 1 required
UsersUserPreferencesUpdateResponse
object
1 property 1 required
NotFound
object
1 property 1 required
UsersTopicPreferenceUpdate
object
3 properties 1 required
UsersUserPreferencesGetResponse
object
1 property 1 required
PreferenceStatus
string
BadRequest
object
1 property 1 required
UsersUserPreferencesListResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

courier-user-preferences-api-openapi.yml Raw ↑

Other APIs Courier publishes across the network.

Courier Inbox Real-Time API
AE Profile APIs.io
Courier Audiences API
AE Profile APIs.io
Courier Audit Events API
AE Profile APIs.io
Courier Authentication API
AE Profile APIs.io
Courier Automations API
AE Profile APIs.io
Courier Brands API
AE Profile APIs.io
Courier Bulk API
AE Profile APIs.io
Courier Courier Create API
AE Profile APIs.io
Courier Device Tokens API
AE Profile APIs.io
Courier Inbound API
AE Profile APIs.io
Courier Journeys API
AE Profile APIs.io
Courier Lists API
AE Profile APIs.io
#User Preferences
← Back to C APIs
API Details
ID
courier:courier-user-preferences-api
Base URL
https://api.courier.com
Docs
https://www.courier.com/docs/reference
Provider
Courier
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=courier-user-preferences-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/courier-user-preferences-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

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