Attentive Identity API
Use the Identity API to manage user identifiers. With this API, you can programmatically add a client user identifier or custom identifier(s) to a user.You should only use clientUserId and customIdentifiers to send Attentive your system-assigned unique identifiers (even when testing).Notes: - Sending duplicate values could lead to unintentionally bridging users together. - Don't use customIdentifiers to send attributes (e.g., first name, last name). To send those typesof attributes, use our [Custom Attributes API](https://docs.attentivemobile.com/openapi/reference/tag/Custom-Attributes/). - Avoid sending null values or empty strings. If you don't have a valid identifier, you should omitthe field from the payload.
Attentive Identity API is one of 19 APIs that Attentive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Identity. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 1 operation across 1 path, and defines 2 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Attentive Identity 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.
Use the Identity API to manage user identifiers. With this API, you can programmatically add a client user identifier or custom identifier(s) to a user. You should only use client…
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are IdentifyRequestDto (6 properties), CustomIdentifierDto1 (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Attentive 12
Other APIs Attentive publishes across the network.
This is an independent, third-party profile of Attentive Identity 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.