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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
emnify

emnify subpackage_authentication API

The subpackage_authentication API from emnify — 8 operation(s) for subpackage_authentication.

Documentation Provider Profile APIs.io OpenAPI GitHub

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.

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.2.0, at version 1.0.0.

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

8 operations 8 paths 21 schemas 2 DELETE3 GET1 PATCH2 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
Contact
emnify Developer Support
License
Proprietary
Resource Areas
1

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.

subpackage_authentication 8
POST
/api/v1/authenticate
Retrieve authentication token
authenticate body → 200400401404
POST
/api/v1/user/mfa
Create an MFA key
post-mfa 1 param body → 200409422
GET
/api/v1/user/mfa/status
List MFA key statuses
user-mfa-status-get 1 param → 200
GET
/api/v1/user/mfa/type
List MFA key types
user-mfa-type-get 1 param → 200
PATCH
/api/v1/user/mfa/{key_id}
Activate MFA key
user-mfa-by-id-patch 2 params body → 204404409422
GET
/api/v1/user/{user_id}/mfa/trusted_device
List trusted devices
user-mfa-trusted-device-by-user-id-get 2 params → 200404
DELETE
/api/v1/user/{user_id}/mfa/trusted_device/{device_id}
Delete a trusted device
user-mfa-trusted-device-by-user-id-and-device-id-delete 3 params → 204404
DELETE
/api/v1/user/{user_id}/mfa/{key_id}
Delete an MFA key
user-mfa-by-user-id-and-key-id-delete 3 params → 204404

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), PostMfaRequestUnprocessableEntityError (4 properties), ApiV1AuthenticatePostRequestBodyContentApplicationJsonSchemaTrustedDevice (4 properties), ApiV1UserUserIdMfaTrustedDeviceGetResponsesContentApplicationJsonSchemaItems (4 properties). Each schema is shown below with its type and property counts.

UserMfaByIdPatchRequestConflictError
object
3 properties
UserMfaByIdPatchRequestNotFoundError
object
3 properties
Authentication_postMfa_Response_200
object
6 properties
UserMfaTrustedDeviceByUserIdGetRequestNotFoundError
object
3 properties
PostMfaRequestConflictError
object
3 properties
PostMfaRequestUnprocessableEntityError
object
4 properties
AuthenticateRequestNotFoundError
object
3 properties
ApiV1UserMfaKeyIdPatchRequestBodyContentApplicationJsonSchemaStatus
object
The target status for the MFA key.
1 property 1 required
ApiV1UserMfaPostRequestBodyContentApplicationJsonSchemaType
object
ApiV1UserMfaTypeGetResponsesContentApplicationJsonSchemaItems
object
2 properties
UserMfaTrustedDeviceByUserIdAndDeviceIdDeleteRequestNotFoundError
object
3 properties
UserMfaByIdPatchRequestUnprocessableEntityError
object
3 properties
ApiV1AuthenticatePostRequestBodyContentApplicationJsonSchemaTrustedDevice
object
Device information to register as trusted (90-day MFA exemption)
4 properties
ApiV1UserMfaPostResponsesContentApplicationJsonSchemaType
object
2 properties
Authentication_Authenticate_Response_200
object
3 properties
ApiV1UserMfaPostResponsesContentApplicationJsonSchemaStatus
object
2 properties
ApiV1UserMfaStatusGetResponsesContentApplicationJsonSchemaItems
object
2 properties
AuthenticateRequestUnauthorizedError
object
3 properties
UserMfaByUserIdAndKeyIdDeleteRequestNotFoundError
object
3 properties
ApiV1UserMfaPostResponsesContentApplicationJsonSchemaErrorsItems
object
ApiV1UserUserIdMfaTrustedDeviceGetResponsesContentApplicationJsonSchemaItems
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs emnify publishes across the network.

emnify GraphQL API
AE Profile APIs.io
emnify Data Streamer
AE Profile APIs.io
emnify Documentation MCP Server
AE Profile APIs.io
emnify subpackage_applicationTokens API
AE Profile APIs.io
emnify subpackage_automations API
AE Profile APIs.io
emnify subpackage_cloudConnect API
AE Profile APIs.io
emnify subpackage_customEvents API
AE Profile APIs.io
emnify subpackage_endpoint API
AE Profile APIs.io
emnify subpackage_euicc API
AE Profile APIs.io
emnify subpackage_euiccOperation API
AE Profile APIs.io
emnify subpackage_events API
AE Profile APIs.io
emnify subpackage_integrations API
AE Profile APIs.io
← Back to E APIs
API Details
ID
emnify:emnify-subpackage-authentication-api
Server
https://cdn.emnify.net
Docs
https://docs.emnify.com/developers
Provider
emnify
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=emnify-subpackage-authentication-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/emnify-subpackage-authentication-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of emnify subpackage_authentication 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.