Updated 28 October 2026. Full technical documentation is at developer.resimpli.com.
The Open API has grown from 34 endpoints at launch to 54. This article covers what is new, what changed, and what still is not available.
The headline
You can now change records, not just create and read them. At launch the API could add a record or delete it, with nothing in between. You can now move a record through your pipeline, tag it, log activity against it, and manage the contacts attached to a lead.
New: update a record's status
Four new endpoints move a record from one status to another — the most requested capability since launch. They exist for leads, buyers, vendors and agents, and each takes the record's ID, the target pipeline and the target status.
The lead version also decides what happens to open tasks on the record when its status changes: leave them alone, complete them all, or complete only yours.
Important: a status change made through the API does fire your Status Change automations, exactly as a manual change does. If an outside system will be moving records at volume, check which automations are listening before you switch it on.
What this unlocks: when a deal closes in another tool, that tool can move the matching lead here, instead of someone doing it by hand.
New: tags
Nine new endpoints. Tags can now be applied, removed and created through the API.
Add tags to a lead, buyer, vendor or agent
Remove tags from any of the four
Create new tags, for leads, buyers, vendors, dispo, agents, inventory or list stacking
What this unlocks: incoming leads can be tagged by source, campaign or score at the moment they are created, so they land in the right place rather than needing sorting later.
New: log activity on a record
Two new endpoints, one of which is the first genuine write into a record's history. You can write an activity comment onto a lead, buyer, vendor or agent, and read activity back.
What this unlocks: an outside system can leave a trail. A call service can log that it reached the seller; an AI tool can write its summary straight onto the lead, where your team will actually see it.
New: contacts
Five new endpoints. Contacts are now something you can work with directly, rather than something buried inside a lead.
Search all contacts by name, phone number or email
Attach an existing contact to a lead
Add a phone number or email to a contact on a lead
Remove a contact from a lead
Change which contact is primary
What this unlocks: properties with several parties — co-owners, heirs, an attorney — can be modelled properly from an outside system.
Two things that were fixed
The base URL now points at production. Code samples in the documentation previously used the staging server. They now use api.resimpli.com. If you copied a sample before late October, check the URL in your integration.
The authentication header is now consistent. The documentation and the code samples previously disagreed about whether the key needed a "Bearer" prefix. The answer is no prefix — send your key on its own in the Authorization header. If your integration sends "Bearer" and is getting 401 errors, that is why.
What has not changed
Rate limit: 500 requests per minute per API key, across the whole API. Raised from 100 on 1 October 2026.
Every endpoint is a POST request.
Status IDs still come from the pipeline list. There is no standalone endpoint listing statuses — they come back inside the pipeline list response.
Still not available
Being direct about the gaps, because these are the most common questions.
Webhooks cannot be managed through the API. Webhooks themselves do exist — you set them up inside REsimpli as an action on an automation, up to 10 per account on any plan, fired from any automation trigger. What you cannot do is create or manage them programmatically.
No SMS or email sending. Call logs and activity are readable, but the API cannot send a text or an email.
No automation endpoints. Automations are built inside REsimpli and cannot be created or edited through the API.
No file upload. Documents and photos can be listed and downloaded, not uploaded.
Records still cannot be fully edited. You can change status and tags. Other fields — a property address, a buyer's target cities, custom fields, assignment — still have to be edited in REsimpli.
Responses are not documented. Endpoint pages list what you send, not what comes back. Use the "Try it out" button on the documentation to see the shape of a real response before you build against it.
One thing to know when creating records
The marketing campaign field on the create endpoints is spelled marketingCampignId — missing the "a" in "campaign". That is the real field name and your request must use that exact spelling.
Where to go next
Every endpoint is documented at developer.resimpli.com, with an interactive request builder and code samples in cURL, Python, Node and C#.
If you are building an integration and something here is not clear, contact support — and tell us what you are trying to connect. That feedback shapes what gets built next.