Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

emnify subpackage_customEvents API

The subpackage_customEvents API from emnify — 4 operation(s) for subpackage_customevents.

emnify subpackage_customEvents 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_customEvents. 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 4 paths, and defines 9 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.

6 operations 4 paths 9 schemas 1 DELETE4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

emnify subpackage_customEvents 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 4 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_customEvents 6
GET
/api/v1/event/custom/configuration
List custom events
get-custom-events 1 param → 200
POST
/api/v1/event/custom/configuration
Deploy custom event
create-custom-event-instance 1 param body → 201
GET
/api/v1/event/custom/configuration/{custom_event_id}
Get a custom event by ID
get-custom-event 2 params → 200
DELETE
/api/v1/event/custom/configuration/{custom_event_id}
Delete custom event
delete-custom-event 2 params → 200
GET
/api/v1/event/custom/template
List custom event templates
get-custom-event-templates 1 param → 200
GET
/api/v1/event/custom/template/{template_id}
Get a custom event template by ID
get-custom-event-template 2 params → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are CustomEventTemplateOutputDto (9 properties), CustomEventOutputDto (7 properties), ConfigurationPropertiesDto (6 properties), SupportedTargetingParametersDto (4 properties). Each schema is shown below with its type and property counts.

SupportedTargetingParametersDto
object
4 properties 4 required
WithIdInputDto
object
1 property 1 required
Custom Events_deleteCustomEvent_Response_200
object
Empty response body
CustomEventTemplateOutputDto
object
9 properties 9 required
ValidatorDto
object
2 properties 2 required
ConfigurationInputPropertiesDto
object
3 properties 3 required
CustomEventOutputDto
object
7 properties 7 required
ConfigurationPropertiesDto
object
6 properties 6 required
CustomEventCreateDto
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emnify-subpackage-customevents-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_endpoint API
emnify subpackage_euicc API
emnify subpackage_euiccOperation API
emnify subpackage_events API
emnify subpackage_integrations API