Engagedly Locations API
Manage office locations and addresses
Engagedly Locations API is one of 8 APIs that Engagedly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Locations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 5 operations across 2 paths, and defines 7 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 Locations 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 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Manage office locations and addresses
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Location (8 properties), LocationRequest (7 properties), Pagination (4 properties), ErrorDetail (3 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.