Macrometa Triggers API
This endpoint is designed for configuring triggers for a specific component. Triggers are essential for initiating actions within a component, as they define the specific conditions under which these actions are executed. Each trigger consists of one or more rules, known as Trigger Rules, which collectively determine when an action should be started. In the configuration process, you can define various types of Trigger Rules, each tailored to different conditions and scenarios. This flexibility allows for precise control over component behavior, enabling actions to be executed in response to defined events or states. It is crucial to accurately set up triggers to ensure the proper functioning of the component within your website's architecture. By using this endpoint, you can create, modify, or delete trigger configurations, thereby customizing how and when your component reacts to specific conditions or user interactions.
Macrometa Triggers API is one of 63 APIs that Macrometa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Triggers. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 5 operations across 2 paths. It is described by OpenAPI 3.0.0, at version 0.17.17.
Requests are made against a single base URL, https://api-play.paas.macrometa.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Macrometa Triggers API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (ApiKeyAuth).
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
ApiKeyAuth— Provide an API Key to the Authorization header, prefixed with "apikey". Example: Authorization: apikeyBearerAuth— Provide a JSON Web Token (JWT) to the Authorization header, prefixed with "bearer". Example: Authorization: bearer
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
This endpoint is designed for configuring triggers for a specific component. Triggers are essential for initiating actions within a component, as they define the specific conditio…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Macrometa 12
Other APIs Macrometa publishes across the network.
This is an independent, third-party profile of Macrometa Triggers 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.