emnify subpackage_serviceProfiles 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_serviceProfiles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.
This API exposes
14 operations
across 7 paths,
and defines 39 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.
14 operations7 paths39 schemas6 DELETE3 GET1 PATCH2 POST2 PUT
Metadata
The identity and technical contract details declared by the specification.
emnify subpackage_serviceProfiles 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 14
Across 7 paths, the API surfaces 14 operations — 6 DELETE, 3 GET, 1 PATCH, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are Service Profiles_ServiceProfileByProfileIdGet_Response_200 (22 properties), ApiV1ServiceProfileGetResponsesContentApplicationJsonSchemaItems (11 properties), ApiV1ServiceProfileProfileIdTrafficLimitGetResponsesContentApplicationJsonSchemaItems (6 properties), ApiV1ServiceProfileProfileIdGetResponsesContentApplicationJsonSchemaIpFirewallRuleSetIpFirewallProfilesItems (3 properties). Each schema is shown below with its type and property counts.
Service Profiles_ServiceProfileByProfileIdPatch_Response_201
Period of the limit. The only supported period is Monthly, which uses calendar months and has an ID of 2. The limit resets at the beginning of each month 00:00…
