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_automations API

The subpackage_automations API from emnify — 6 operation(s) for subpackage_automations.

emnify subpackage_automations 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 9 operations across 6 paths, and defines 20 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.

9 operations 6 paths 20 schemas 1 DELETE5 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
Resource Areas
1

Authentication & Security 1

emnify subpackage_automations 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 9

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

subpackage_automations 9
GET
/api/v1/automation
List configured automations
list-automations 1 param → 200
POST
/api/v1/automation
Create an automation
create-automation 1 param body → 201
GET
/api/v1/automation/action
List available actions
list-action 1 param → 200
GET
/api/v1/automation/action/{id}
Get an action by ID
get-action-by-id 2 params → 200
GET
/api/v1/automation/log
List action logs
list-action-logs 3 params → 200
POST
/api/v1/automation/recipient/email/verification
Verify an automation recipient's email address
verify-automation-recipient-email 1 param body → 200
GET
/api/v1/automation/{id}
Get configured automation by ID
get-automation 2 params → 200
DELETE
/api/v1/automation/{id}
Delete a configured automation
delete-automation 2 params → 204
PATCH
/api/v1/automation/{id}
Update an automation
update-automation 2 params body → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are AutomationOutputDto (12 properties), SystemEventOutputDto (10 properties), AutomationActionLogOutputDto (10 properties), AutomationActionOutputDto (9 properties). Each schema is shown below with its type and property counts.

AutomationUpdateDto
object
5 properties 5 required
WithUuidInputDto
object
1 property 1 required
ConfiguredActionRecipientOutputDto
object
1 property 1 required
AutomationRecipientEmailVerificationInputDto
object
1 property 1 required
Automations_verifyAutomationRecipientEmail_Response_200
object
Empty response body
SystemEventOutputDto
object
10 properties 10 required
WithStringIdInputDto
object
1 property 1 required
AutomationActionOutputDto
object
9 properties 9 required
ConfiguredActionOutputDto
object
3 properties 3 required
AutomationOutputDto
object
12 properties 12 required
ConfiguredActionCreateDto
object
2 properties 2 required
ConfiguredActionReferenceDto
object
2 properties 1 required
WithIdInputDto
object
1 property 1 required
AutomationActionLogOutputDto
object
10 properties 10 required
ActionableEventCreateDto
object
2 properties 2 required
CustomEventOutputDto
object
7 properties 7 required
ConfigurationParameterDto
object
3 properties 3 required
AutomationCreateDto
object
6 properties 6 required
ActionableEventOutputDto
object
2 properties 2 required
ConfigurationInputPropertiesDto
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emnify-subpackage-automations-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_cloudConnect API
emnify subpackage_customEvents API
emnify subpackage_endpoint API
emnify subpackage_euicc API
emnify subpackage_euiccOperation API
emnify subpackage_events API
emnify subpackage_integrations API
Where this information came from

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