canonical: https://jentic.com/apis/realeflow.com/realeflow

# Realeflow API

Realeflow CRM API for managing contacts, properties, and contact-property relationships in the real estate investment platform. The API exposes 6 endpoints secured with basic authentication.

## For AI agents

Programmatically get account status, create a contact. Covers 6 operations with basic authentication.

## Scope

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

## Capabilities

- Get account status
- Create a contact
- List contacts
- Access Realeflow API crm resources via REST API

## Use cases

### CRM Operations

Use the Realeflow API to perform crm operations programmatically. The API provides 6 endpoints covering core functionality including get account status, create a contact, list contacts.

Example prompt: Call GET `/account/status` to get account status

### Automated Account Management

Automate account operations by combining multiple Realeflow API endpoints. Agents can create a contact and then list contacts in a single workflow.

Example prompt: Call POST `/contact/create` to create a contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Realeflow 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 basic tokens manually.

Example prompt: Search Jentic for 'get account status', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account/status` | Get account status |
| POST | `/contact/create` | Create a contact |
| GET | `/contact/list` | List contacts |
| POST | `/contact/propertyrelation` | Create contact-property relation |
| POST | `/property/create` | Create a property |
| GET | `/property/list` | List properties |

## Key resources

- **Account** — Operations related to Account
- **Contacts** — Operations related to Contacts
- **Properties** — Operations related to Properties

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 40 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/realeflow.com/realeflow/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Realeflow API by hand means encoding your key as HTTP basic auth, coordinating the contact and property create and list calls, and relating contacts to properties yourself. Through Jentic you install once, import the Realeflow API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Realeflow API creates contacts and properties through collection endpoints with data in the request body, so you limit the agent to the operations it needs, such as listing contacts or checking account status. It only calls the operations you allow, so creating a contact or property is out of scope unless you add it.
- **Credential handling:** Your Realeflow API basic 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 'get account status' or 'list contacts', and Jentic returns the matching Realeflow API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Realeflow API use?

The Realeflow API uses HTTP Basic authentication. 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 get account status with the Realeflow API?

Yes. Use the GET `/account/status` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Realeflow 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 get account status through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account status'. Jentic returns the matching Realeflow API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Realeflow API have?

The Realeflow API exposes 6 endpoints covering account, contacts, properties operations.

### Can I limit what my agent is allowed to do with the Realeflow API?

Yes. Because you self-host Jentic One, your own rules decide which Realeflow operations the agent may call and which credential it uses. You can allow read-only operations such as GET `/account/status`, GET `/contact/list`, and GET `/property/list` while withholding the write operations. That means POST `/contact/create`, POST `/property/create`, and POST `/contact/propertyrelation` stay out of scope unless you explicitly grant them.