[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own VaultRE API

> VaultRE: API access only after MRI approves your developer as an integrator. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/vaultre

VaultRE: no self-serve API key; your developer registers as an integrator and MRI reviews each request (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your VaultRE account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in VaultRE session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=vaultre)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by VaultRE. VaultRE is a trademark of its owner. If VaultRE's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/appraisals-without-follow-up" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"since": "2026-11-13"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/appraisals-without-follow-up";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ since: "2026-11-13" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/appraisals-without-follow-up",
headers={"Authorization": f"Bearer {key}"},
json={"since": "2026-11-13"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"date": "2026-11-13",
"address": "8 Ocean Rd",
"owner": "Tom H.",
"agent": "Kate",
"price": "$860k"
},
{
"date": "2026-11-14",
"address": "3/40 Bay St",
"owner": "Mia K.",
"agent": "Sam",
"price": "$640k"
}
]
}
```

01 Build

## How do you build a VaultRE endpoint with Cotlet?

1. 01  
login.vaultre.com.au  
Signed in  
### Sign in to VaultRE in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the appraisals since this date with no next step, with the owner, the agent and the appraised price.  
### Do the job once with your agent.  
For example: "List the appraisals since this date with no next step, with the owner, the agent and the appraised price."
3. 03  
Save endpoint  
Name  
appraisals-without-follow-up  
Input  
since  
Returns  
date, address, owner, agent, price  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or an agent, and the fields it returns.
4. 04  
$ POST /api/v1/custom/appraisals-without-follow-up  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in VaultRE session.

02 Endpoints

## Example endpoints you could build for VaultRE

Cotlet ships no fixed list of VaultRE endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/appraisals-without-follow-up`  
### Appraisals with no follow-up  
Date, address, owner, agent and price of each appraisal with no next step
- POST `/api/v1/custom/holding-area-enquiries`  
### Enquiries in the holding area  
Name, contact details, property and age of each waiting enquiry
- POST `/api/v1/custom/listings-by-status`  
### Listings by status  
Address, price, agent and days on market for each listing
- POST `/api/v1/custom/open-homes-for-week`  
### Open homes for a week  
Time, address and agent of each open home and viewing
- POST `/api/v1/custom/add-contact-note` writes  
### Add a contact note  
A note saved on a contact, with its date
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/appraisals-without-follow-up" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"since": "2026-11-13"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"date": "2026-11-13",
"address": "8 Ocean Rd",
"owner": "Tom H.",
"agent": "Kate",
"price": "$860k"
},
{
"date": "2026-11-14",
"address": "3/40 Bay St",
"owner": "Mia K.",
"agent": "Sam",
"price": "$640k"
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your VaultRE endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A Monday list in n8n or Make.  
Appraisals with no follow-up, sent to each agent by email or Slack.
- Website endpoint open homes  
### Your website's open home page.  
This week's open homes read from VaultRE when a visitor opens the page.
- Schedule endpoint Google Sheets  
### A sales dashboard.  
Listings and appraisals per agent pulled into Google Sheets or Looker Studio.
- Phone system endpoint contact note  
### A call notes flow.  
Notes from your phone system saved on the right VaultRE contact.

04 Access

## What can an endpoint see and change?

An endpoint works in your own VaultRE session, so it can read and change only what your VaultRE login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as adding a contact note, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/add-contact-note

would POST login.vaultre.com.au/... add a note to Tom H.

`add-contact-note`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does VaultRE have an official API?

VaultRE: the API "may be used by your developer to integrate your website (or other application) with your VaultRE account" once MRI approves that developer as an integrator; the agency then creates the token in VaultRE (checked 20 Nov 2026). VaultRE has a small Zapier app and a CSV export of property search results. The full picture with sources: [Does VaultRE have an API or MCP server?](https://cotlet.dev/api-status/vaultre.md)

Want ChatGPT or Claude to work in VaultRE instead of code? See the [VaultRE MCP server](https://cotlet.dev/integrations/vaultre-api-mcp-server.md).

1/3

Official API

By approval

[Full API & MCP report](https://cotlet.dev/api-status/vaultre.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## VaultRE API with Cotlet: questions

### Is this an official VaultRE API?

No. Cotlet is independent and not affiliated with VaultRE. The endpoints you build run in your own signed-in VaultRE account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when VaultRE changes its screens?

An endpoint works while VaultRE works the way it did when you built it. If VaultRE changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first VaultRE endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=vaultre)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
