A real API, not a bolt-on
Most rental software offers an API the way a hotel offers a gym — technically present, rarely fit for serious use. A handful of endpoints, undocumented errors, and a sales call to get a key.
The Renttix API is the platform. More than 600 versioned operations cover the whole rental domain — customers, quotes, rentals, assets, dispatch, invoicing, payments, and maintenance — with the conventions serious APIs share: cursor pagination, idempotency keys for safe retries, a standard error envelope with request IDs, and tiered rate limits that are published rather than discovered.
Access is properly governed. Scoped test and live API keys separate experiments from production, and a full OAuth2 authorisation server handles the rest — authorisation code with PKCE for user-facing apps, client credentials for servers, and a device grant for tools without a browser. Hosted consent screens show users exactly which resource-level scopes an app is asking for, client secrets can be rotated, and API keys revoked at any time.
Every account includes an isolated sandbox: one call seeds a realistic set of customers, assets, and rentals, and the seeder refuses live keys, so test data cannot land in production. The platform is also run in the open — a public status page, a dated changelog that flags additions, changes, deprecations, and security fixes, and a support and community hub for when the docs are not enough.
Events pushed to you, not polled for
Integration usually fails in the second system. The CRM that finds out about a new customer a day late. The alerting job that polls every five minutes and still misses the moment that mattered.
Renttix pushes instead. Subscribe an endpoint to platform events and it receives HMAC-signed deliveries as they happen. Failures are retried on an escalating backoff schedule, exhausted deliveries move to a dead-letter queue instead of vanishing, any event can be replayed, and full delivery logs show what was sent, when, and what came back.
What arrives is typed, not guessed. Ten versioned event types — spanning rentals, payments, invoices, assets, and maintenance — ship with published JSON Schemas and a documented envelope, so consumers validate every payload against a contract instead of reverse-engineering one. That includes a live GPS telemetry stream: vehicle position events arrive as locations change, turning tracking into something your own systems can subscribe to.
For the systems nobody wants to write code for, the official Zapier app connects Renttix to more than 8,000 tools. Twelve instant triggers — new orders, accepted quotes, an asset leaving its site geofence, a service interval falling due — plus create and search actions, with no code required. Under the hood the triggers are REST hooks riding Renttix's signed webhooks; Zapier is simply the friendliest door into them.
Tooling for developers — human and AI
Official SDKs for TypeScript and Python handle the plumbing — automatic retries, auto-pagination, webhook signature verification — and everything is generated from an OpenAPI 3.1 contract that ships alongside a Postman collection. create-renttix-app scaffolds a working project in one command, and the renttix CLI signs in with a device code and works against sandbox or production from the terminal.
The developer portal carries 48 guides, an auto-generated API reference with curl, TypeScript, and Python samples for every operation, and an in-browser playground for trying calls before writing any code. A dashboard manages keys, webhook subscriptions, usage charts, and team access in one place.
AI-assisted development is treated as the norm, not a novelty. An MCP server gives Claude, Cursor, and other agent tools live, typed access to the whole API. llms.txt bundles make the documentation loadable into any model's context, and AGENTS.md briefs ship in every package, so an agent dropped into your codebase knows the conventions before its first call. BYOK AI endpoints go further — bring your own key and ask questions or forecast demand over your own account data.
And what you build does not have to stay yours. Any tenant can register as a partner, create OAuth apps, submit them for review, and publish to a public directory that every other Renttix tenant can install from with one click. An integration built for one rental business becomes a product for the whole ecosystem — build once, serve many.
Try this feature in the live demo
Explore the full Renttix platform. No signup required.
Developer platform FAQ
Every account has an isolated sandbox with its own test keys. One call seeds realistic customers, assets, and rentals — and the seeder refuses live keys, so test data cannot land in production. The in-browser playground offers ready-to-run calls for the most common operations, and the renttix CLI makes the same calls from the terminal. Nothing touches production until you switch to live keys.
Ten versioned event types covering rentals, payments, invoices, assets, and maintenance — including a live GPS telemetry stream — each with a published JSON Schema. Deliveries are HMAC-signed, retried with backoff, logged in full, and replayable. The official Zapier app adds twelve instant triggers of its own — orders, customers, products, quotes, and asset alerts — across more than 8,000 tools.
Yes, deliberately. An MCP server gives Claude, Cursor, and similar tools live typed access to the API, llms.txt bundles make the docs loadable into a model's context, and AGENTS.md briefs ship in the SDKs and project template. Agents get the same sandbox as humans, so experiments stay away from live data.
Register as a partner from the developer dashboard, create an OAuth app with the scopes it needs, and submit it for review. Approved apps are published to the public directory, where any tenant can install them with one click — and deprecations are announced in the dated changelog rather than discovered in production.
Ready to modernize your rental operations?
Payments + deposits enabled • Quick setup • No credit card trial