Developer Tools · Integration
HTTP
Add HTTP to your product for your customers, and give your AI agents governed access to it.
Embed an HTTP integration so your product can call the APIs fastn does not have a named connector for, including your customers' own internal services. Each customer supplies their own base URL, headers, and credentials, so the call runs under their access rather than a shared key, and request and response mapping is configuration per customer rather than code. fastn handles credential storage, retries, and pagination patterns, so a customer with an unusual endpoint does not require a release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers point your product at their own internal API by supplying a base URL and credentials during setup.
Call a long-tail SaaS API that has no dedicated connector yet, without shipping a client library in your product.
Map request bodies, headers, and query parameters per customer so one flow serves many differently shaped endpoints.
Receive inbound webhooks from a customer's service and trigger your product when they arrive.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent calls a customer-approved endpoint within the methods and paths you allow, with every request logged.
An agent reads a JSON response and grounds its answer in the customer's own service data.
An agent reacts to an inbound webhook and runs the next step of a workflow.
Example prompt
Call the customer's inventory endpoint for SKU 4412 and tell me the stock level it returns.
Set up HTTP in 4 steps
- 01Open the HTTP connector from your fastn dashboard.
- 02Have each customer supply their base URL and authentication details for the API they want reached.
- 03Define the requests your product makes, map the responses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the HTTP integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an HTTP integration without building it. Your customers point it at their own endpoint and credentials and work their services, builds and deployments through it, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an HTTP update is not your on-call problem.
- One integration serves your product and your agents. The same governed HTTP connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHub
AWS Lambda
VercelOften used alongside
Tools the same teams tend to run next to HTTP, across other categories.
Slack
Snowflake
Airtable
PostgreSQLHTTP integration FAQ
How do I add an HTTP integration to my product?
Enable the HTTP connector in your fastn dashboard, then let each customer authenticate their own HTTP account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HTTP client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is an HTTP connection configured per customer?
HTTP is a specification rather than a service you sign up for, so there is no HTTP account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own services, builds and deployments. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this HTTP integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent calls a customer-approved endpoint within the methods and paths you allow, with every request logged.
Who maintains the HTTP integration?
fastn does. When HTTP changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to HTTP events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in HTTP?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the HTTP integration?
A common starting point: point your product at their own internal API by supplying a base URL and credentials during setup. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the HTTP integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HTTP does not change your per-connector cost. You can start free with 3 connected accounts.
Add HTTP to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.