Before starting, you should be familiar with the event-driven microservices pattern and async/parallel programming.
When you sign up at the platform, you'll be asked to set your API's base URL that is your namespace. So if you set your namespace as "my-awesome-product," all your API calls should be sent to:
An event is a message sent to our Event API and it's primarily composed of 4 properties:
Unique Name: the path parameter sent to the event API.
Filters: create conditionals based on your event models using query syntax.
Actions: perform actions according to each event filter.
A service account is a Cloud Service integrated at our platform; it could be:
Google Cloud Platform Project
Amazon Web Services Account
SaaS accounts such as Stripe, Slack and more
Custom APIs hosted on any private or public cloud servers such as Digital Ocean.
To integrate a Cloud Service check the configuration section for each service type.
A trigger runs whenever the Event API is called.
Messages published to your service accounts (database inserts, API calls) or requests count as an outgoing event.
Each subscription plan has its daily free quotas that if exceeded create additional billing at each metric quota range:
Incoming Events: Exceeded quota create additional billing at each 100K requests.
Outgoing Events: Exceeded quota create additional billing at each 100K requests.
Data Transferred: Quota creates additional billing at each GB transferred.