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

Vibes Platform Event-Triggered Campaign API

The Event-Triggered Campaign API API from Vibes Platform — 2 operation(s) for event-triggered campaign api.

Vibes Platform Event-Triggered Campaign API is one of 30 APIs that Vibes Platform publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event-Triggered Campaign API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against 2 base URLs: https://public-api.vibescm.com, https://public-api.eu.vibes.com/.

5 operations 2 paths 9 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://public-api.vibescm.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Vibes Platform Event-Triggered Campaign API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 5

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

Event-Triggered Campaign API 5
POST
/companies/{company_key}/mobiledb/event_triggered_messages
Create an event-triggered campaign
3 params body → 200202
GET
/companies/{company_key}/mobiledb/event_triggered_messages
Get event-triggered campaigns
5 params → 200
GET
/companies/{company_key}/mobiledb/event_triggered_messages/{event_triggered_message_id}
Get event-triggered campaign info
4 params → 200404
PUT
/companies/{company_key}/mobiledb/event_triggered_messages/{event_triggered_message_id}
Update an event-triggered campaign
4 params body → 200404422
DELETE
/companies/{company_key}/mobiledb/event_triggered_messages/{event_triggered_message_id}
Cancel an event-triggered campaign
4 params → 200404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are eventTriggeredResponse (8 properties), eventTriggeredRequest (5 properties), eventTriggeredRequestMMS (5 properties), eventTriggeredRequestPush (5 properties). Each schema is shown below with its type and property counts.

filters-number
number
eventTriggeredRequestPush
object
5 properties 4 required
eventTriggeredRequestMMS
object
5 properties 4 required
filters-string
string
eventTriggeredRequest
object
5 properties 4 required
mmstext
object
2 properties
eventTriggeredResponse
object
8 properties
eventTriggeredsResponse
array
mmsurl
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vibes-platform-event-triggered-campaign-api-api-openapi.yml Raw ↑

Other APIs Vibes Platform publishes across the network.

Vibes Platform Acquisition Campaigns API
Vibes Platform Broadcasts API
Vibes Platform Callbacks API
Vibes Platform Carrier Lookup API
Vibes Platform Events API
Vibes Platform Inbound Messages API
Vibes Platform Messages API
Vibes Platform Persons API
Vibes Platform Subscription Lists API
Vibes Platform Wallet Passes API
Vibes Platform Acquisition Campaign API
Vibes Platform Android Wallet Templates API
Where this information came from

This is an independent, third-party profile of Vibes Platform Event-Triggered Campaign 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.