Run customer API calls through one attributable relay

Where it goes wrong

Per-customer endpoints mean per-customer hostnames, TLS quirks and outages. Without attribution, one customer's broken integration looks identical to a platform-wide failure in your dashboards.

What Backfire handles

• Target host, status, duration and trips are recorded per call, so one customer's traffic is separable from the rest.
• A shared guard blocks internal ranges no matter which customer supplied the endpoint.
• Byte counts in the envelope make per-customer data volume visible without extra instrumentation.
• Revoke a shared key and every integration stops on the next request — useful during an incident.

The request

await fetch('https://backfireapi.base44.app/functions/forward', {
  method: 'POST',
  headers: { Authorization: `Bearer ${process.env.BACKFIRE_KEY}`, 'Content-Type': 'application/json' },
  body: JSON.stringify({
    url: tenant.endpoint_url,
    method: 'GET',
    headers: { Accept: 'application/json' },
    timeout_ms: 10000,
  }),
});
// correlate tenant -> call with your own request id in a custom header
// the activity log keeps the full detail for later reconciliation

All use cases