engineer-rest-api

Build and integrate Braze REST API endpoints for messaging, SMS, email, and reminders.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-rest-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-rest-api
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-rest-api
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-rest-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a clear, implementable pattern for building, sending, scheduling, and debugging Braze REST API messages so backend teams can reliably deliver email, SMS, reminders, and product recommendations without guessing payload shapes or error handling.

Core Features & Use Cases

  • Endpoint selection & payload construction: Maps channel-specific message objects to the correct /messages/send and scheduling endpoints with required fields.
  • Authentication and rate management: Shows how to include workspace REST API keys, handle 429 rate limits with exponential backoff, and batch recipients for high-volume sends.
  • Personalization and recommendations: Demonstrates storing recommendation IDs on profiles, using Liquid or Catalogs/Connected Content at send time, and patterns for reminder workflows.
  • Debugging & verification: Describes response handling (dispatch IDs, 4xx/5xx parsing), delivery checks in the dashboard, and common causes of suppressed sends.

Quick Start

Call the engineer-rest-api skill to construct a /messages/send payload for a transactional email including authentication, campaign_id, app_id, and Liquid personalization.

Frequently Asked Questions about engineer-rest-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I construct a Braze REST API payload for transactional email and SMS?

To construct a Braze REST API payload for transactional email and SMS, map channel-specific message objects to the /messages/send endpoint using required fields, workspace REST API keys, and app_id for authentication and routing.

What's the best way to handle Braze REST API rate limits and 429 errors?

Handling Braze REST API rate limits and 429 errors requires implementing exponential backoff and batching recipients for high-volume sends to manage throughput and avoid hitting the API rate ceiling.

How do I send personalized Braze messages using Liquid and Catalogs?

Sending personalized Braze messages with Liquid and Catalogs involves using Liquid personalization tags or Connected Content at send time, and storing recommendation IDs on user profiles via /users/track before dispatch.

How do I debug suppressed sends and parse 4xx/5xx errors from the Braze REST API?

Debugging suppressed sends and parsing 4xx/5xx errors from the Braze REST API involves examining response dispatch IDs, parsing error codes, and checking delivery logs in the dashboard for common suppression causes.

Can I schedule Braze reminder workflows and write custom attributes via the REST API?

You can schedule Braze reminder workflows using scheduling endpoints and write custom reminder attributes to user profiles via the /users/track endpoint, enabling automated message triggers based on profile data.

How do I retrieve product metadata for Braze messages using Connected Content and Catalogs?

Retrieving product metadata for Braze messages using Connected Content and Catalogs requires calling the appropriate endpoints at send time to fetch dynamic content, then injecting it into the message payload for delivery.