How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

emnify subpackage_serviceLookupsAndConfiguration API

The subpackage_serviceLookupsAndConfiguration API from emnify — 5 operation(s) for subpackage_servicelookupsandconfiguration.

emnify subpackage_serviceLookupsAndConfiguration 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_serviceLookupsAndConfiguration. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 5 JSON Schemas.

This API exposes 6 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://cdn.emnify.net.

6 operations 5 paths 9 schemas 1 DELETE4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://cdn.emnify.net
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

emnify subpackage_serviceLookupsAndConfiguration 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 6

Across 5 paths, the API surfaces 6 operations — 1 DELETE, 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

subpackage_serviceLookupsAndConfiguration 6
GET
/api/v1/dns
List DNS configs
dns-get 1 param → 200
POST
/api/v1/dns
Create DNS config
dns-post 1 param body → 201
DELETE
/api/v1/dns/{dns_id}
Delete DNS config
dns-by-id-delete 2 params → 204
GET
/api/v1/service
List services
service-get 1 param → 200
GET
/api/v1/service/{service_id}/traffic_limit
Get service SMS limit
service-traffic-limit-by-id-get 2 params → 200
GET
/api/v1/traffic_limit
List traffic limits
traffic-limit-get 1 param → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ApiV1ServiceGetResponsesContentApplicationJsonSchemaItems (6 properties), ApiV1DnsGetResponsesContentApplicationJsonSchemaItems (4 properties), ApiV1TrafficLimitGetResponsesContentApplicationJsonSchemaItems (4 properties), ApiV1ServiceServiceIdTrafficLimitGetResponsesContentApplicationJsonSchemaItemsPeriod (3 properties). Each schema is shown below with its type and property counts.

Service_Lookups_and_Configuration_DnsPost_Response_201
object
Empty response body
ApiV1ServiceGetResponsesContentApplicationJsonSchemaItemsTrafficType
object
ApiV1DnsGetResponsesContentApplicationJsonSchemaItems
object
4 properties
ApiV1ServiceGetResponsesContentApplicationJsonSchemaItems
object
6 properties
ApiV1ServiceServiceIdTrafficLimitGetResponsesContentApplicationJsonSchemaItems
object
3 properties
ApiV1TrafficLimitGetResponsesContentApplicationJsonSchemaItems
object
4 properties
ApiV1ServiceServiceIdTrafficLimitGetResponsesContentApplicationJsonSchemaItemsPeriod
object
3 properties
ApiV1TrafficLimitGetResponsesContentApplicationJsonSchemaItemsService
object
ApiV1TrafficLimitGetResponsesContentApplicationJsonSchemaItemsPeriod
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emnify-subpackage-servicelookupsandconfiguration-api-openapi.yml Raw ↑

Other APIs emnify publishes across the network.

emnify GraphQL API
emnify Data Streamer
emnify Documentation MCP Server
emnify subpackage_applicationTokens API
emnify subpackage_authentication API
emnify subpackage_automations API
emnify subpackage_cloudConnect API
emnify subpackage_customEvents API
emnify subpackage_endpoint API
emnify subpackage_euicc API
emnify subpackage_euiccOperation API
emnify subpackage_events API
Where this information came from

This is an independent, third-party profile of emnify subpackage_serviceLookupsAndConfiguration API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.