Skip to main content
The API Call stage enriches documents by calling external HTTP APIs. This enables integration with third-party services like Stripe, GitHub, weather APIs, and more to augment documents with real-time data.
Stage Category: APPLY (1-1 Enrichment)Transformation: N documents → N documents (same count, expanded schema)

When to Use

When NOT to Use

Parameters

Required Parameters

Optional Parameters

Authentication Types

OAuth 2.0, JWT tokens - Most modern APIs (GitHub, OpenAI, Stripe)
Adds header: Authorization: Bearer {secret_value}

Error Handling

Configuration Examples

Security

SSRF Protection RequiredThis stage makes external HTTP requests which can be exploited for Server-Side Request Forgery attacks. Always use allowed_domains to whitelist permitted domains.

Security Best Practices

  1. Never use * in allowed_domains - Explicitly list each domain
  2. Never store credentials in configuration - Always use auth.secret_ref to reference vault secrets
  3. Set rate limits - Prevent abuse and excessive costs
  4. Use HTTPS - HTTP URLs are automatically upgraded
  5. Audit configurations - Review before deployment to prevent data exfiltration

Storing Secrets

Then reference in configuration:

Performance

Template Variables

URLs, headers, and body values support template variables: