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

Courier User Profiles API

The User Profiles API from Courier — 2 operation(s) for user profiles.

Courier User Profiles 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 Profiles. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 8 operations across 2 paths, and defines 21 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.

8 operations 2 paths 21 schemas 2 DELETE2 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://api.courier.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 8

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

User Profiles 8
GET
/profiles/{user_id}
Get a profile
profiles_get 1 param → 200400
POST
/profiles/{user_id}
Create a profile
profiles_create 1 param body → 200400
PUT
/profiles/{user_id}
Replace a profile
profiles_replace 1 param body → 200400
PATCH
/profiles/{user_id}
Update a profile
profiles_mergeProfile 1 param body → 204
DELETE
/profiles/{user_id}
Delete a profile
profiles_delete 1 param → 204400
GET
/profiles/{user_id}/lists
Get list subscriptions
profiles_getListSubscriptions 2 params → 200400
POST
/profiles/{user_id}/lists
Subscribe to one or more lists
profiles_subscribeToList 1 param body → 200400
DELETE
/profiles/{user_id}/lists
Delete list subscriptions
profiles_deleteListSubscription 1 param → 200400

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are GetListSubscriptionsItem (5 properties), UserProfilePatch (3 properties), NotificationPreferenceDetails (3 properties), Paging (2 properties). Each schema is shown below with its type and property counts.

ChannelPreference
object
1 property 1 required
ChannelClassification
string
NotificationPreferences
object
BadRequest
object
1 property 1 required
UserProfilePatch
object
3 properties 3 required
GetListSubscriptionsResponse
object
2 properties 2 required
ProfileGetResponse
object
2 properties 1 required
RecipientPreferences
object
2 properties
SubscribeToListsRequest
object
1 property 1 required
SubscribeToListsResponse
object
1 property 1 required
GetListSubscriptionsItem
object
5 properties 4 required
MergeProfileResponse
object
1 property 1 required
BaseError
object
1 property 1 required
SubscribeToListsRequestItem
object
2 properties 1 required
Paging
object
2 properties 1 required
ProfileUpdateRequest
object
1 property 1 required
DeleteListSubscriptionResponse
object
1 property 1 required
NotificationPreferenceDetails
object
3 properties 1 required
ReplaceProfileResponse
object
1 property 1 required
PreferenceStatus
string
Rule
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Courier publishes across the network.

Courier Inbox Real-Time API
Courier Audiences API
Courier Audit Events API
Courier Authentication API
Courier Automations API
Courier Brands API
Courier Bulk API
Courier Courier Create API
Courier Device Tokens API
Courier Inbound API
Courier Journeys API
Courier Lists API
Where this information came from

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