Creating a REST Connector
Configure Base Settings
- Name - Identifier (e.g., “Stripe API”)
- Base URL - API root (e.g., https://api.stripe.com/v1)
- Description - What it does
Define Operations
Add each API endpoint as an operation:
- Click Add Operation
- Enter operation name
- Choose HTTP method (GET, POST, etc.)
- Enter path (e.g., /charges/)
- Define input JSON schema
- Click Save
Configure Authentication
- Click Authentication
- Choose method (Bearer, OAuth, API Key, etc.)
- Enter credentials or configure OAuth
- Test connection
Operation Definition
Each operation maps to an API endpoint:Parameter Mapping
Map input parameters to HTTP request parts:Path Parameters
Parameters in URL path (e.g.,/users/{id}):
Query Parameters
Parameters in URL query string:Body Parameters
Data in request body:Header Parameters
Custom headers:Request Body Strategies
Full Input
Use entire input as body:From Field
Extract specific field:Mapped
Map multiple fields:Response Handling
Control how responses are processed:| Option | Effect |
|---|---|
json_path | Extract nested data |
include_metadata | Include status code, headers |
strict_status_codes | Treat non-2xx as error |
Example Connectors
GitHub API
Stripe API
Common Headers
Set headers automatically on all requests:Rate Limits
Configure per-operation limits:Cost
For current pricing details, see Pricing. Monitor in Account > Usage dashboard.Best Practices
Be Specific with Parameters
Define exactly which fields are needed to reduce token usage.Use Appropriate HTTP Methods
- GET for retrieval
- POST for creation
- PATCH for partial updates
- DELETE for removal
Handle Errors
Configurestrict_status_codes to handle API errors properly.
Validate Input
Use JSON Schema to validate required parameters.Document Operations
Add clear descriptions for each operation.Testing
Use the Test tab to verify operations:- Select operation
- Enter sample input
- View request and response
- Check response format
- Verify no errors
Troubleshooting
”Connection Failed”
- Verify base URL is correct
- Check network connectivity
- Ensure authentication is set up
”Parameter Not Found”
- Verify parameter names match schema
- Check
from_fieldmappings - Ensure required parameters provided
”Invalid Response”
- Check API documentation for response format
- Verify
json_pathis correct - Try different response parsing options
Next Steps
- OpenAPI Import - Auto-generate from spec
- Authentication
- Parameter Mapping
- Attach to Agent