canonical: https://jentic.com/apis/re-leased.com/re-leased

# Re-Leased API

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.

## For AI agents

Programmatically retrieve accounts list, retrieve all companies. Covers 21 operations with oauth2 authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Retrieve accounts list
- Create a contact
- Update a contact
- Access Re-Leased API payments resources via REST API

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'retrieve accounts list', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Accounts** — Operations related to Accounts
- **Companies** — Operations related to Companies
- **Contacts** — Operations related to Contacts
- **Credit Notes** — Operations related to Credit Notes
- **Inspections** — Operations related to Inspections

## Why Jentic

- **Setup:** Wiring the Re-Leased API by hand means running its OAuth2 flow, refreshing tokens before they expire, and paging through accounts, companies, contacts, and credit notes yourself. Through Jentic you install once, import the Re-Leased API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** With the Re-Leased API you limit the agent to the operations it needs, such as listing accounts or reading a company, since most writes like creating a contact or a credit note post to collection endpoints rather than a single pinned resource. It only calls the operations you allow, so creation stays out of scope unless you add it.
- **Credential handling:** Your Re-Leased API OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve the accounts list' or 'get a company by id', and Jentic returns the matching Re-Leased API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Re-Leased API?

Yes. Because you run Jentic One yourself, your own rules decide which Re-Leased API operations and credentials the agent can use, so you can allow only read calls such as GET `/api/accounts` to list accounts or GET `/api/companies/{id}` to read a single company. Write operations like creating a contact or a credit note post to collection endpoints such as POST `/api/contacts` and POST `/api/credit-notes`, so they stay out of scope unless you explicitly add them. The agent only ever calls the operations you permit, and the stored OAuth credential is injected at execution time rather than exposed to the agent.