emnify subpackage_applicationTokens API
The subpackage_applicationTokens API from emnify — 2 operation(s) for subpackage_applicationtokens.
emnify subpackage_applicationTokens 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_applicationTokens. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.
This API exposes 3 operations across 2 paths, and defines 6 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_applicationTokens 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 3
Across 2 paths, the API surfaces 3 operations — 1 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ApiV1ApplicationTokenGetResponsesContentApplicationJsonSchemaItems (7 properties), ApplicationTokenPostRequestUnprocessableEntityError (3 properties), Application tokens_ApplicationTokenPost_Response_200 (1 property). 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.