engineer-api-data

Diagnose Braze API, webhook, and Connected Content failures with HTTP error analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers and integrators diagnose and resolve programmatic issues with Braze, including API errors, webhook and Connected Content failures, user deletion and blocklisting decisions, and data schema or identifier mismatches across Liquid, REST API, and Currents.

Core Features & Use Cases

  • Webhook & Connected Content Troubleshooting: Interpret HTTP error codes, unhealthy host detection, retry behavior, and actionable steps to fix authentication, payload, or endpoint issues.
  • User & Custom Data Management: Explain consequences of deleting vs blocklisting attributes/events, how to change custom data types safely, and how deletions affect downstream exports and counts.
  • Identifier & Dispatch Tracing: Map campaign/canvas attribute names and IDs across Liquid, REST API, and Currents; explain dispatch_id behavior for scheduled vs triggered sends and how to template it.
  • Use Case Example: Given a failing Connected Content call that returns 598 and high 5xx rates, use this skill to determine whether the target host is unhealthy, recommend retry or :retry usage, and point to the appropriate Help Center articles.

Quick Start

Diagnose a webhook 500 error and provide prioritized troubleshooting steps with relevant Help Center references.

Frequently Asked Questions about engineer-api-data

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

FAQPage Schema
How do I troubleshoot a Braze Connected Content call returning a 598 error?

Braze webhooks support unhealthy host detection and specific retry rules. You interpret HTTP error codes, apply :retry parameters for transient 5xx failures, and follow documented retry behavior to recover failing webhook data dispatches.

What is the difference between blocklisting and deleting custom data attributes in Braze?

Deleting custom data attributes permanently removes them from Braze and downstream Currents exports, while blocklisting stops processing without full removal. Choosing between them affects data lifecycle behaviors and downstream count accuracy across your integration.

How does dispatch_id work across scheduled and triggered Braze campaign sends?

The dispatch_id correlates campaign and canvas sends in Braze. Scheduled sends share a single dispatch_id, while triggered sends generate unique dispatch_ids, allowing you to template and trace message attribution across Liquid, REST API, and Currents data.

Can I safely change custom data types for existing Braze attributes?

Changing custom data types in Braze requires understanding data lifecycle behaviors and identifier mappings. You must verify attribute name and ID mappings across Liquid, REST API, and Currents to ensure existing integrations and downstream exports remain consistent.

How do I map campaign attribute names and IDs across Braze Liquid, REST API, and Currents?

Mapping Braze campaign attribute names and IDs requires tracing identifiers across Liquid, REST API, and Currents. You correlate dispatch_id behavior and attribute mappings to ensure consistent user data tracking and resolve schema mismatches in programmatic integrations.

Why do Braze webhook payloads fail with high 5xx rates from the target endpoint?

High 5xx rates on Braze webhooks indicate the target endpoint is returning server errors or is unhealthy. You diagnose authentication, payload structure, and endpoint availability, then apply retry rules or :retry usage to restore Connected Content data flows.