REsimpli Open API: what it can and cannot do

The Open API launched with REsimpli 6.0 in September 2026. Before that, outside tools connected through Zapier and an API token in the profile menu. The new API opens a real door, with real limits. This is what the documentation and REsimpli’s help center say it does, as of September 2026.

From REsimpli's developer portal and help center, September 2026. Response fields are not documented for any endpoint.

Data	Read	Create or delete	Update
Leads	List and details	Yes	Planned
Buyers, agents, vendors	List and details	Yes	Planned
Call logs	Per record	No	No
Activity and conversations	Per record	No	No
Appointments	By date range	No	No
Files and photos	List and download	Upload planned	No
Notes and tasks	No endpoint	No endpoint	Planned
Status, tags, assignment	Filters and tag list	No	Planned
Dashboards and accounting	No endpoint	No	No

Which REsimpli plans include API access?

All of them. REsimpli’s help center says Open API access “is included on every plan,” and the pricing page adds that there are no usage fees. The catch is the version: REsimpli states plainly that the Open API does not work with the old version of the platform, so an account has to be on 6.0 to use it.

Where is the API key, and how do you use it?

Keys live under Settings, then API and Webhooks. Each account gets one, and REsimpli says restricted keys with narrower permissions are planned. Requests go to https://api.resimpli.com/api/v6/openapi with the key in the Authorization header, and every endpoint is a POST with a JSON body. The developer portal’s tester checks a key by calling getUserInfo.

What are the limits?

• 100 requests a minute per key, shared across every endpoint, with HTTP 429 past it. The limit is the same on every plan.
• Pages of up to 100 records, requested by page number. There is no cursor.
• No changed-since filter on any endpoint, so a sync cannot ask for only what changed. Every pull is a full pull.
• Call logs and activity are per record. Reading history means one request per lead, buyer, agent or vendor, which works out to about a hundred records a minute.
• Responses are not documented. The portal describes request bodies only, so field names come from a live test, not from the docs.
• No sandbox. One production base URL is documented.

What about webhooks and Zapier?

Webhooks in 6.0 are actions inside REsimpli’s automations: an automation trigger fires, and a webhook step calls an outside URL. REsimpli’s help center says “Basic and Pro include one webhook; Enterprise is unlimited,” and that changes made through the API deliberately do not fire automations at launch. Status changes cannot be made through the Open API or Zapier.

Zapier has a new REsimpli 6.0 app, and old zaps must be reconnected to it. Zapier’s listing shows actions that create agents, buyers, vendors, leads and list stacking records.

Is the API enough to migrate off REsimpli?

For records, yes: leads, buyers, agents, vendors, appointments and files all read cleanly in principle. For history it depends on what the per-record activity feed returns, since there is no notes or tasks endpoint, and that is the first thing to test with a read-only key. The throughput is fine for a one-time move: a few thousand leads is hours of extraction, not days. The export guide covers the routes for everything the API does not reach, and the migration page shows how we sequence it.