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

Extole User Subscriptions API

The User Subscriptions API from Extole — 3 operation(s) for user subscriptions.

Extole User Subscriptions API is one of 44 APIs that Extole publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User Subscriptions. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against a single base URL, https://{brand}.extole.io.

6 operations 3 paths 24 schemas 1 DELETE3 GET1 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.extole.io
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Extole User Subscriptions API declares 3 security schemes for authenticating requests. An API key is passed in the cookie as extole_token (COOKIE). An API key is passed in the header as Authorization (HEADER). An API key is passed in the query as access_token (QUERY). By default, every request must be authenticated.

Paths & Operations 6

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

User Subscriptions 6
GET
/v6/subscriptions
List subscriptions
listSubscriptions 2 params → 200400401402403415429
GET
/v6/users/{user_id}/subscriptions
List user subscriptions
listUserSubscriptions 1 param → 200400401402403415429
POST
/v6/users/{user_id}/subscriptions
Create a user subscription
createUserSubscription 1 param body → 200400401402403415429
GET
/v6/users/{user_id}/subscriptions/{subscription_id}
Get a user subscription
getUserSubscription 2 params → 200400401402403415429
PUT
/v6/users/{user_id}/subscriptions/{subscription_id}
Update a user subscription
updateUserSubscription 2 params body → 200400401402403415429
DELETE
/v6/users/{user_id}/subscriptions/{subscription_id}
Delete a user subscription
deleteUserSubscription 2 params → 200400401402403415429

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are UserSubscriptionResponse (6 properties), SubscriptionResponse (6 properties), RestExceptionResponse (5 properties), UserSubscriptionRequest (5 properties). Each schema is shown below with its type and property counts.

UserSubscriptionUpdateRequest
object
Body of a PUT /v6/users/{userid}/subscriptions/{subscriptionid} request.
5 properties
SubscriptionChannelRequest
SubscriptionUserResponse
object
4 properties
ThirdPartyEmailSubscriptionChannelResponse
object
3 required
FilterExpressionInUserSubscriptionRequest
Choose between static or dynamic filter expression
SubscriptionResponse
object
6 properties 6 required
WebhookSubscriptionChannelRequest
object
2 required
SuccessResponse
object
1 property 1 required
SubscriptionChannelResponseBase
object
2 properties
SubscriptionChannelRequestBase
object
1 property
UserSubscriptionRequest
object
5 properties 2 required
RestExceptionResponse
object
Represents the API error response
5 properties 5 required
WebhookSubscriptionChannelResponse
object
3 required
ThirdPartyEmailSubscriptionChannelRequest
object
2 required
ExtoleClientSlackSubscriptionChannelRequest
object
1 required
FilterExpressionInUserSubscriptionUpdateRequest
Choose between static or dynamic filter expression
SlackSubscriptionChannelRequest
object
2 required
EmailSubscriptionChannelRequest
object
1 required
EmailSubscriptionChannelResponse
object
2 required
ExtoleClientSlackSubscriptionChannelResponse
object
2 required
SlackSubscriptionChannelResponse
object
3 required
FilterExpressionInUserSubscriptionResponse
The filter expression as configured: a literal value, or an expression (type:string) when defined dynamically.
SubscriptionChannelResponse
UserSubscriptionResponse
object
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

extole-user-subscriptions-api-openapi.yml Raw ↑

Other APIs Extole publishes across the network.

Extole Audiences API
Extole Authentication API
Extole Batch Jobs API
Extole Blocks API
Extole Campaign Controllers Actions API
Extole Campaign Controllers API
Extole Campaign Controllers Triggers API
Extole Campaign Flow Steps API
Extole Campaigns API
Extole Components API
Extole Components Grants API
Extole Components Settings API
Where this information came from

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