Service API Schedules
Instant delivery schedules which don't store data in the database
Documentation: https://docs.redeye.com/api/#Service
Service API schedules
Service API schedules send instantly. They're used for fire & forget communications such as transactional messaging or customer updates. You can set up either an Email, SMS or Push Service API schedule.
Key Features:
- Instant delivery
- Fire & forget schedules
- Only data/merges passed within the API call can be used in the Creative/SMS.
- Unable to reference segments, custom rules, or apply external Dynamic Content
Service API schedules DO NOT touch the databaseThe reason service API schedules can send so quickly is that the data passed within the Service API call doesn't get stored in the database. The data is added to the email creative and sent to the customer.
We retain records that a customer has been sent a Service API schedule, but any data passed within the API call cannot be used in segmentation or referenced elsewhere in the platform.
Setting up Service API Schedules
Service API schedules are set up in exactly the same way as a standard schedules of the same type, they don't require any recipients to be added as these are provided in the API call.
Key Differences:
- No recipients need be added to the schedule
- No Start Timer is required
- Cannot add delivery rules
- Able to edit the API schedule (Stop/make changes) while the existing API schedule remains live
Watch the videos below to learn how to set up your API schedule. The steps are exactly the same aside from the differences above!
Updated 10 months ago