Scripted API pulls and backfills through one key

Where it goes wrong

Bulk jobs are where outbound code gets sloppiest: ad-hoc timeouts, no size bounds, and a credential copied into five scripts. When a run misbehaves there is rarely a single place to look.

What Backfire handles

• One key for the whole pipeline, revocable independently of your other jobs.
• Bounded per-call payloads and enforced timeouts keep a bad run from snowballing.
• Prepaid packs are cheaper per 1,000 trips as volume grows, with no expiry and no seats.
• Export the activity log as CSV or JSON to reconcile a run against your own records.

The request

#!/usr/bin/env bash
set -euo pipefail

for id in $(seq 1 500); do
  curl -sS https://backfireapi.base44.app/functions/forward \
    -H "Authorization: Bearer $BACKFIRE_KEY" \
    -H "Content-Type: application/json" \
    -d "{\"url\":\"https://api.example.com/items/$id\",\"method\":\"GET\",\"timeout_ms\":10000}" \
    | jq -e '.ok and .upstream.status == 200' >/dev/null || echo "failed: $id"
done

All use cases