Re-Leased API
✓ Official Vendor SpecPaymentsBilling Subscriptionsoauth221 EndpointsREST
For Agents
Programmatically retrieve accounts list, retrieve all companies. Covers 21 operations with oauth2 authentication.
Use for: I need to accounts list, I want to all companies, Search for single company, Find all a contact
Not supported: Does not handle communications, crm, or developer tools — use for payments only.
Re-Leased is a property management API for managing accounts, companies, contacts, credit notes, invoices, inspections, and maintenance records. The API exposes 21 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the Re-Leased API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Re-Leased API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Re-Leased API.
Retrieve accounts list
Create a contact
Update a contact
Access Re-Leased API payments resources via REST API
Use Cases
Patterns agents use Re-Leased API for, with concrete tasks.
★ Payments Operations
Use the Re-Leased API to perform payments operations programmatically. The API provides 21 endpoints covering core functionality including retrieve accounts list, retrieve all companies, retrieve single company.
Call GET /api/accounts to retrieve accounts list
Automated Accounts Management
Automate accounts operations by combining multiple Re-Leased API endpoints. Agents can retrieve all companies and then retrieve single company in a single workflow.
Call GET /api/companies to retrieve all companies, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Re-Leased API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'retrieve accounts list', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
21 endpoints — re-leased is a property management api for managing accounts, companies, contacts, credit notes, invoices, inspections, and maintenance records.
METHOD
PATH
DESCRIPTION
GET
/api/accounts
Retrieve accounts list
GET
/api/companies
Retrieve all companies
GET
/api/companies/{id}
Retrieve single company
POST
/api/contacts
Create a contact
GET
/api/contacts
Retrieve contacts
PUT
/api/contacts
Update a contact
POST
/api/credit-notes
Create credit note
GET
/api/credit-notes
Retrieve credit notes
GET
/api/accounts
Retrieve accounts list
GET
/api/companies
Retrieve all companies
GET
/api/companies/{id}
Retrieve single company
POST
/api/contacts
Create a contact
GET
/api/contacts
Retrieve contacts
PUT
/api/contacts
Update a contact
POST
/api/credit-notes
Create credit note
GET
/api/credit-notes
Retrieve credit notes
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Re-Leased API oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'retrieve accounts list') and Jentic returns the matching Re-Leased API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Re-Leased API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Re-Leased API through Jentic.
What authentication does the Re-Leased API use?
The Re-Leased API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I retrieve accounts list with the Re-Leased API?
Yes. Use the GET /api/accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Re-Leased API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I retrieve accounts list through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'retrieve accounts list'. Jentic returns the matching Re-Leased API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Re-Leased API have?
The Re-Leased API exposes 21 endpoints covering accounts, companies, contacts operations.
GET STARTED