01
Create your connection
Sign in to RentorStay. Open your account menu → API & integrations. Managers can also open Settings → Security & privacy → API & integrations. Select your organization, name, permissions and expiration. Keys with read permissions cannot edit records.
02
Save the key in your integration
The key is shown once. Save it in the credential or secret manager of your integration. Use a separate key for each assistant. Copy the API endpoint displayed in your account. Never paste the key in prompts, shared documents, URLs or public code.
03
Connect an assistant or workflow
Use an HTTP-capable AI agent, n8n HTTP Request, a server-side script or an integration that accepts OpenAPI. Configure Bearer authentication with your key. A regular chat conversation without external API tools cannot operate RentorStay just by receiving a key.
04
Authorize the actions you need
The first version supports property lookup, materials and tools, work vehicles, Manager tasks, Owner notes and portfolio, Resident lease/rent summaries, Vendor work progress and property-thread messages. Availability depends on the selected permissions and current role access.
05
Monitor and revoke
Recent requests show their operation and result in API & integrations. Revoke a connection immediately if it is no longer needed, or revoke all connections. Keys expire after 7, 30 or 90 days. To rotate, create a replacement, update your integration and revoke the previous key.
First request
Read the endpoint and key from your integration secrets.
curl "$RENTORSTAY_API_BASE/me" \
-H "Authorization: Bearer $RENTORSTAY_API_KEY"
Create a task · Manager
POST /actions
Authorization: Bearer [credential from secret manager]
Content-Type: application/json
Idempotency-Key: task_inspection_20261008
{"operation":"tasks.create","payload":{"title":"Inspect water heater","description":"Document condition with photos","priority":"normal","property_id":"AUTHORIZED_PROPERTY_UUID"}}
Use a fresh Idempotency-Key for each intended change. Reuse the same key and identical body when retrying a failed connection.
Inventory example
{"operation":"inventory.save","payload":{"property_id":"AUTHORIZED_PROPERTY_UUID","action":"create","data":{"item_type":"material","name":"Silicone sealant","unit":"each","quantity":3,"new_location_name":"Maintenance cabinet","purchased_from":"Supplier name","purchase_date":"2026-10-08"}}}
Updates: use action update with data.item_id and name. Counts: use action count with data.item_id, location_id, quantity and a required note explaining the adjustment. Vehicles: vehicles.save accepts name, license_plate, odometer_unit (mile/km) and initial_odometer inside data. The app and API use the same inventory and fleet.
Operating limits
60 requests per minute and 10,000 per day for each key. Request bodies up to 32 KiB. 401: invalid or expired key. 403: access denied. 409: retry identifier conflict. 429: wait at least 60 seconds. Preserve request_id when contacting support.
Billing, security settings, access grants, contract signatures, payments and deletion remain outside this API. Bulk file migration and photo/file uploads continue through the app. This API does not create a built-in autonomous AI; it connects an assistant you configure.
Integration support