Schedule API Triggered Canvases in Braze Endpoints
A documented Braze Endpoints operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Schedule API Triggered Canvases
- POSTChanges data · Messaging
rest.iad-01.braze.com/canvas/trigger/schedule/create
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Braze Endpoints operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Braze Endpoints operations
- Query Hard Bounced EmailsGET · reads data
- Query List of Unsubscribed Email AddressesGET · reads data
- List User's Subscription Group Status - SMSGET · reads data
- List User's Subscription Group - SMSGET · reads data
- Custom Events ListGET · reads data
- Campaign ListGET · reads data
- Send AnalyticsGET · reads data
- List Available Email TemplatesGET · reads data
Questions
- Can HumDay schedule api triggered canvases in Braze Endpoints?
- Yes. This operation is published in Braze Endpoints's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Braze Endpoints data?
- Yes — this is a POST operation, so it changes something in Braze Endpoints. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Braze Endpoints account.
Where this came from
Read from a published API description for Braze Endpoints at www.getpostman.com/collections/29baa41d7ba930673ef0. The description above is the provider’s own wording, not ours. Last published 2021-06-21.