emnify subpackage_authentication API
The subpackage_authentication API from emnify — 8 operation(s) for subpackage_authentication.
emnify subpackage_authentication API is one of 29 APIs that emnify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 5 JSON Schema definitions.
Tagged areas include subpackage_authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.
This API exposes 8 operations across 8 paths, and defines 21 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against a single base URL, https://cdn.emnify.net.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
emnify subpackage_authentication API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
BearerAuth— Retrieve a JWT via POST /api/v1/authenticate using an applicationtoken or user credentials, then send it as Authorization: Bearer .
Paths & Operations 8
Across 8 paths, the API surfaces 8 operations — 2 DELETE, 3 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 21
The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are Authentication_postMfa_Response_200 (6 properties), ApiV1UserUserIdMfaTrustedDeviceGetResponsesContentApplicationJsonSchemaItems (4 properties), PostMfaRequestUnprocessableEntityError (4 properties), ApiV1AuthenticatePostRequestBodyContentApplicationJsonSchemaTrustedDevice (4 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 emnify 12
Other APIs emnify publishes across the network.