emnify subpackage_tagManagement 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_tagManagement. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.
This API exposes
11 operations
across 8 paths,
and defines 41 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.
11 operations8 paths41 schemas2 DELETE3 GET1 PATCH5 POST
Metadata
The identity and technical contract details declared by the specification.
emnify subpackage_tagManagement 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 11
Across 8 paths, the API surfaces 11 operations — 2 DELETE, 3 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.
The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are Tag Management_ListTags_Response_200 (5 properties), ApiV2EndpointEndpointIdTagsGetResponsesContentApplicationJsonSchemaItems (4 properties), ApiV2TagsGetResponsesContentApplicationJsonSchemaDataItems (4 properties), AssignTagToEndpointRequestUnprocessableEntityError (3 properties). Each schema is shown below with its type and property counts.
