Engagedly Users API
Manage user profiles, permissions, and activation status
Engagedly Users API is one of 8 APIs that Engagedly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Users. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 11 operations across 7 paths, and defines 15 schemas. It is described by OpenAPI 3.0.3, at version beta.
Requests are made against a single base URL, https://api.engagedly.com/beta.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Engagedly Users API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as ClientKey (clientKeyAuth).
An API key is passed in the header as SecretKey (secretKeyAuth).
By default, every request must be authenticated.
clientKeyAuth— Client key obtained from the Engagedly portal under Integrations Engagedly APIsecretKeyAuth— Secret key obtained from the Engagedly portal. Shown only once upon generation.
Paths & Operations 11
Across 7 paths, the API surfaces 11 operations — 4 GET, 1 PATCH, 1 POST, 5 PUT. Each is listed below with its method, path, parameters, and response codes.
Manage user profiles, permissions, and activation status
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are User (28 properties), UserUpdateRequest (20 properties), UserCreateRequest (20 properties), UserRef (8 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 Engagedly 7
Other APIs Engagedly publishes across the network.