Website Enquiry API: Difference between revisions
From Standout Property Manager Wiki Help
imported>Standout documentation update (Update Standout help for Communications Centre, portal integrations, Customer Portal and Reports Centre changes through 5 September 2026) |
imported>Standout documentation update (Update Standout help for Sales Progression 2.0 and retain recent Communications Centre, portal, Customer Portal and Reports Centre documentation through 6 September 2026) |
(No difference)
| |
Latest revision as of 08:45, 6 September 2026
Website Enquiry API
The Website Enquiry API allows an agency website to send general enquiries, viewing requests, sales/rental enquiries and valuation requests directly into Standout's Communications Centre.
Where to configure it
Website enquiry sources are managed from the inbound-enquiry area in Administration → Feeds/Portals. Each source has a secret API key and can optionally be tied to a fixed Standout branch/origin.
The normal endpoint is:
POST https://YOUR-STANDOUT-HOST/api/v1/enquiries
Authenticate server-side using the source's X-Standout-Key. Never expose the key in browser JavaScript or public page source.
Important fields
A website submission can include:
external_id– strongly recommended unique submission ID;- enquiry type (general/viewing/valuation/sales/rental);
- customer name;
- email and/or telephone;
- message;
- property reference or Standout property ID;
- branch/office ID where allowed;
- source page URL;
- received timestamp.
Duplicate-safe retries
Generate external_id once, store it with the website form submission and reuse it on every retry. If the same source sends the same ID again, Standout returns the existing enquiry rather than creating a second communication.
Treat both HTTP 200 (duplicate/existing) and 201 (new enquiry) as successful outcomes.
What Standout does next
After accepting the enquiry Standout attempts to match the property, choose the branch, match an existing contact by email/telephone, assign the enquiry and retain the original payload. Staff can then correct matches and turn the enquiry into normal CRM actions from the Communications Centre.
Error handling
Typical responses include 401 for a missing/invalid API key, 403 for an origin restriction, 422 for invalid form data, 429 for rate limiting, 503 when the Communications Centre is unavailable and 500 for an unexpected server error.
Retry connection failures, 429 and temporary 5xx responses with increasing delays while keeping the same external_id. Do not repeatedly retry a 401/403/422 without correcting the cause.
Use HTTPS and a short overall request timeout, normally about 10–15 seconds.
A full developer guide can be generated/emailed from the Standout administration area where enabled.