[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.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)

# Process enquiry

> Add a Holding Area enquiry to the database as a contact, with its note and optional buyer requirement. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/vaultre/process_enquiry

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add a Holding Area enquiry to the database as a contact, with its note and optional buyer requirement.

VaultRE API: https://cotlet.dev/docs/api/vaultre.md

`POST https://cotlet.dev/api/v1/vaultre/enquiries/{enquiry_id}/process`

Access: write. Confirm: waits for the user's OK before it runs.

Does what Review and Create Enquiry does. Without contact_id, Vault's suggested match is used if there is one; set create_new_contact to true when the enquiry is a different person. Vault writes the enquiry as a note on the contact, and with create_buyer_requirement it links a requirement to the property asked about. Office automations in Vault can react to the new contact. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `enquiry_id` | string | yes | Enquiry ID from list_enquiries. |
| `contact_id` | string | no | Add the enquiry to this existing contact. |
| `create_new_contact` | boolean | no | Create a new contact even if Vault suggests a match. Default: false. |
| `categories` | array | no | Contact categories to apply. |
| `create_buyer_requirement` | boolean | no | Add a buyer requirement for the property asked about. Default: false. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/vaultre/enquiries/enq_80412/process \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_id":"51377","create_buyer_requirement":true}'
```

**Python**

```python
result = client.call("vaultre", "process_enquiry", {"enquiry_id":"enq_80412","contact_id":"51377","create_buyer_requirement":True})
```

**Node.js**

```js
const result = await cotlet.call('vaultre', 'process_enquiry', {"enquiry_id":"enq_80412","contact_id":"51377","create_buyer_requirement":true});
```

**CLI**

```bash
cotlet call vaultre process_enquiry --data '{"enquiry_id":"enq_80412","contact_id":"51377","create_buyer_requirement":true}'
```

## Example response

```json
{
  "enquiry_id": "enq_80412",
  "status": "processed",
  "contact_id": "51377",
  "contact_created": false,
  "note_added": true,
  "buyer_requirement_created": true
}
```

Previous: [List calendar events](https://cotlet.dev/docs/api/vaultre/list_calendar_events.md)
Next: [Ignore enquiry](https://cotlet.dev/docs/api/vaultre/ignore_enquiry.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.