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

Attentive Custom Events API

Use the Custom Events API to send user actions to use in the Attentive Segment Builder and Journey Builder for both email and text messages. This data cannot contain any sensitive or special categories of information as defined in applicable data protection and privacy laws, including the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA). See a list of specific categories of data you cannot share with Attentive [here](https://docs.attentivemobile.com/pages/legal-docs/pi-disclaimer/).

Attentive Custom Events API is one of 19 APIs that Attentive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Custom Events. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

1 operations 1 paths 3 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.attentivemobile.com/v1
Authentication
HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Attentive Custom Events API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (OAuthFlow) using the authorizationCode flow, exposing 6 scopes. By default, every request must be authenticated.

  • OAuthFlow — This API uses OAuth 2 with the authorization code grant flow. [More info](https://docs.attentivemobile.com/pages/authentication/)

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Custom Events 1

Use the Custom Events API to send user actions to use in the Attentive Segment Builder and Journey Builder for both email and text messages. This data cannot contain any sensitive…

POST
/events/custom
Custom Events
postCustomEvents body → 200400401403404429500

Schemas 3

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

ExternalIdentifiers
object
clientUserId or another custom identifier. This field is required if either phone or email is not provided. If using an external identifier instead of phone or…
2 properties
CustomEventsRequest
object
5 properties 2 required
EventUser
object
User associated with the action. Note that this is a visitor to the site and does not need to be actively subscribed to Attentive. Phone, email, or an external…
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

attentive-custom-events-api-openapi.yml Raw ↑

Other APIs Attentive publishes across the network.

Attentive Access Token API
Attentive Bulk Segment Operations API
Attentive Bulk Status API
Attentive Bulk User Operations API
Attentive Custom Attributes API
Attentive eCommerce API
Attentive Identity API
Attentive Offers API
Attentive Privacy Request API
Attentive Product Catalog API
Attentive Segments API
Attentive Subscribers API
Where this information came from

This is an independent, third-party profile of Attentive Custom Events 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.