Connecting REST APIs

How external APIs get connected — in the generated backend code, not through a connector.

Overview

Airbuild has no separate REST connector to configure. You describe the external API in chat, and the agent writes the client for it into your Web App's Python FastAPI backend.

How to connect an API

• Add the credential in the Environment tab (for example CRM_API_KEY), with separate values for Dev and Prod
• Tell the agent what to call: "Fetch the open invoices from https://api.example.com/invoices and authenticate with CRM_API_KEY as a Bearer token"
• The agent is instructed to read the value with os.getenv() rather than writing it into the code

Authentication

Whatever scheme the API expects — an API key in a header or query parameter, a Bearer token, Basic auth, an OAuth 2.0 client-credentials exchange — is written into the generated code. There is no connector screen that stores the scheme for you.

Keep credentials in the backend

Calls that carry a credential belong in the backend. Ask the agent for a backend route that the frontend calls instead of putting the key into browser code — a Website project has no backend of its own, and anything the browser sends is visible to the visitor.