Braze Connected Content has 2 seconds: pre-render the Sume clip

Can Braze Connected Content call Sume directly?

No, not for a render. Braze's page says the server response has to arrive in under 2 seconds, or the content is not inserted. A Sume avatar video is a job: the default mode is async and returns a job envelope, and sync mode waits at most 30 seconds. Neither fits a 2 second budget.

The working shape is two steps. Render the clip ahead of the send. Then let Connected Content call a lookup you own, which answers from a stored video_url in a few milliseconds.

What does Braze say about the call?

Only the facts that matter for a video link are listed here, from Braze's own page.

How do I pre-render the clip?

Submit the avatar job when the campaign is approved, not when the message sends. Use mode: "webhook" so Sume calls you on job.completed, then save the video_url from the result next to the user or segment key. Each avatar job needs an Idempotency-Key.

Scripts must land in the 4 to 60 second window. At the plus tier with no product image the rate is $0.245 per second, so a 15 second clip is $3.675.

import json, os, urllib.request

def post(path, body, key):
    req = urllib.request.Request(
        "https://api.sume.com" + path,
        data=json.dumps(body).encode(),
        headers={
            "Authorization": "Bearer " + os.environ["SUME_API_KEY"],
            "Content-Type": "application/json",
            "Idempotency-Key": key,
        },
    )
    with urllib.request.urlopen(req) as r:
        return json.load(r)

job = post("/v1/avatar-1.0/talking-video", {
    "avatar_handle": "your_avatar_handle",
    "script": "Your cart is saved. Two more days at this price.",
    "aspect_ratio": "9:16",
    "mode": "webhook",
    "webhook_url": "https://example.com/hooks/sume",
}, "bf-reminder-segment-a")
print(job["status_url"])

What should the Connected Content endpoint return?

Return a 200 with the stored URL once the job is done. Do not answer a not-yet-ready clip with a 404, because Braze renders that as an empty string. The companion post on the 404 case covers the fallback.

Keep the webhook handler small as well. Verify the signature, acknowledge fast and do the storing after, as in acking a Sume webhook.