.DkNUKaKx_ZLAT4m.webp?dpl=dpl_F3AP8gE1CJj8GcfnTX9Puwbcey1S){kind=small}
Connectors / Developer tools · Connector
Call any API with the HTTP Client
Send GET, POST, PUT, PATCH, DELETE and HEAD requests to any API, and build your own connector when there isn't one.
Thanks — someone from our team will be in touch soon.
What can you do with the HTTP Client connector?
Not every app has a dedicated connector, and not every endpoint is covered by the one that does. The HTTP Client calls any API over HTTP, and it is the HTTP Connector named on our app pages. Paste a cURL command to fill in a request, reuse the authentication from an existing connector, and read the response as JSON, XML or text.
- Connects through
- Connector
Automate & integrate HTTP Client
Automating HTTP Client business processes or integrating HTTP Client data is made easy with Tray.ai.
Use case
Connect apps without a dedicated connector
For an app with a documented API, the HTTP Client is the connector. Set the method, URL, headers and body, keep credentials in a Tray authentication, and use the response in the next step.
- Any documented API
- Credentials never hard-coded
- JSON or XML responses
Use case
Fill gaps in an existing connector
When a dedicated connector doesn't cover an endpoint you need, call it with the HTTP Client and reuse that connector's authentication, so there's no second login to manage.
- Reuse existing authentications
- Reach any endpoint
- No second login
Use case
Send and receive files
Send binary bodies, or multipart form-data for file uploads, and treat a response as a file to pass to storage or document steps.
- Multipart file uploads
- Binary bodies streamed
- Responses saved as files
Ready to solve your HTTP Client integration challenges?
See how Tray.ai makes it easy to connect, automate, and scale your workflows.
Thanks — someone from our team will be in touch soon.
Challenges Tray.ai solves
Common obstacles when integrating HTTP Client — and how Tray.ai handles them.
Challenge
Large responses
Tray has a 1 MB limit on a response body, so a long list can fail in a single call.
How Tray.ai helps
Request one page at a time in a loop. The HTTP Client leaves the paging method to you, so it fits whatever scheme the API uses.
Challenge
Telling success from failure
APIs signal problems through status codes, and a workflow should stop or change course when one arrives.
How Tray.ai helps
The step fails on any status outside 2xx unless you list the codes you expect. Branch on the result, or use workflow error handling to send failures down their own path.
How Tray.ai makes this work
HTTP Client plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 700+ connectors with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in HTTP Client — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose HTTP Client actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →See HTTP Client working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.