external_apis

To proxy external API requests with managed billing, invoke externalApi__<connector_name> from code_execution using a path, method, and optional query. The proxy layer handles authorization automatically via passthrough billing and returns a structured body.

No, you do not need to manage API credentials directly when making external web requests. The proxy-enabled billing layer handles authorization automatically, allowing you to securely access external APIs without direct credential management.

You call an external API connector from code execution by invoking externalApi__<connector_name> with a specified path, HTTP method, and an optional query. This retrieves data and returns results in a structured body suitable for parsing.

Yes, you can store and render media URLs retrieved from external APIs. Leverage attached_assets to store and render artifacts when needed, ensuring media retrieved through the connector is properly managed within your environment.

Passthrough billing for API connectors is a Replit-managed mechanism that automatically handles authorization. It applies to external API calls made through code_execution, ensuring secure access without requiring you to manually handle billing or credentials.

When using a proxy layer for external web requests, results are returned in a structured body suitable for parsing, but you are limited to the specific path, method, and optional query parameters defined for each externalApi__<connector_name> invocation.