Key Features
- All HTTP Methods - GET, POST, PUT, PATCH, DELETE
- Authentication - Bearer tokens, OAuth 2.0, Basic auth, custom headers
- Headers Control - Set custom headers, manage cookies
- Body Support - JSON, form data, raw text
- Error Handling - Response status codes, error messages
- Timeout - 30-second timeout with retry capability
How to Enable
For Agents
- Agents > Select Agent > Settings > Capabilities
- Attach HTTP Client
For MCP Gateways
- Gateways > Select Gateway > Capabilities
- Attach HTTP Client
Usage Examples
Simple GET Request
POST with JSON Body
Bearer Token Authentication
Custom Headers
Authentication Methods
No Authentication
Bearer Token
Basic Authentication
Custom Headers
OAuth 2.0
Handled via Connector authentication. For raw OAuth, include Authorization header with token.Request Methods
- GET
- POST
- PUT
- PATCH
- DELETE
Retrieve data
Response Handling
All responses return:Status Codes
Resource Limits
Configuration
Optional gateway specifications:Common Use Cases
Fetch Data from API
Submit Form
Update Remote Resource
Webhook Integration
Error Handling
If request fails:Common Errors
Cost
For current pricing details, see Pricing. Monitor in Account > Usage dashboard.Best Practices
Use Correct Content-Type
Check Response Status
Always verifystatus_code before processing response.
Handle Rate Limiting
If you receive429 Too Many Requests, wait before retrying.
Validate URLs
Ensure URLs are HTTPS and properly formatted.Use Pagination
For large datasets, use pagination to avoid timeouts.Troubleshooting
”Connection Refused”
- Check API endpoint is correct and online
- Verify firewall allows outbound HTTPS
- Try different endpoint if available
”SSL Certificate Error”
- URL should use HTTPS, not HTTP
- Verify certificate is valid
- Check server configuration
”Timeout”
- Request taking too long (>30 seconds)
- Simplify request or add pagination
- Check server performance
”Authentication Failed”
- Verify token/key is correct
- Check token hasn’t expired
- Ensure correct authentication method