Renta REST API
The Renta REST API allows you to manage three core ELT resources: Source, Destination, and Pipeline.
The Renta REST API supports CRUD operations, which allow you to fully manage all resources via the API.
The table below shows the available resources and their supported operations:
| Resource | Supported operations |
|---|---|
| Source | Create, list, update, delete |
| Destination | Create, list, update, delete |
| Pipeline | Create, list, update, delete, run |
Postmen collection
To simplify API exploration and integration, we provide a ready-to-use Postman collection. It includes pre-configured requests for all available endpoints and authentication setup.
We highly recommend using the Postman collection to streamline the implementation process, simplify testing, and accelerate your onboarding with the Renta API.
HTTP status codes
The API uses standard HTTP status codes to indicate the success or failure of a request.
| Code | Name |
|---|---|
| 200 | OK. The request was successful, and the server returned the expected response. |
| 400 | Bad Request. The request is invalid due to malformed JSON, missing, or invalid parameters. |
| 401 | Unauthorized. Authentication failed — typically due to a missing or invalid token. |
| 403 | Forbidden. The authenticated user does not have the necessary permissions to access the requested resource. |
| 500 | Internal Server Error. An unexpected error occurred on the server. Please get in touch with our support team if the issue persists. |
Rate Limiting
The API is rate-limited. Usage can be tracked through response headers such as X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.
For more details, see the Rate Limiting section.
Ready to get started?
Build your data pipeline today or get a personalized demo. Start free!
Need help?
Get expert support to ensure your project succeeds. We're here to help!
Feature requests?
Help shape our product! Share your ideas for new features and integrations.