leads

Send a real enquiry to the CoworkingView team (single property or shortlist).

WRITE — creates a real lead: the enquiry is sent to the CoworkingView team and forwarded to the space operator, and a person will contact the email given. Call it only when the user has explicitly asked to enquire and has provided their own contact details; never to test the API or to "check availability". Create a lead for one space or a shortlist. This is the only write most agents need. Requires a Turnstile challenge token in production (CHALLENGE_FAILED if it is missing or invalid). CoworkingView forwards the enquiry to the operator; it does not broker the contract. Safe to retry: send an Idempotency-Key header (any unique string, e.g. a UUID per logical submission) and a retried request with the SAME key and body returns the original response without creating a second lead. The same key reused with a DIFFERENT body is a client bug and returns 422 IDEMPOTENCY_KEY_CONFLICT rather than guessing which body to honour. Omitting the header is fine — behaviour is unchanged and a request without one is executed every time.

post/v1/leads/inquiry

Request

  • Base URL: https://api.coworkingview.com
  • URL: https://api.coworkingview.com/v1/leads/inquiry
  • Auth: none required

Headers

Idempotency-Keystring

Optional client-chosen key that makes a retry safe. The same key with the same body replays the first response (header Idempotency-Replayed: true) instead of creating a second enquiry; the same key with a different body is rejected with 422 IDEMPOTENCY_KEY_CONFLICT. A 5xx is not stored, so it can be retried under the same key.

Request body

namestring required
emailstring email required
phonestring
companystring
messagestring
locale'en' | 'de' | 'es' required
challengeTokenstring
websitestring
propertiesstring[] required
desksinteger
moveInDatestring date
duration'hours' | 'days' | 'weeks' | 'months' | 'years'

Response

Success

Changes

No recorded changes to this operation across all 1 revision of this API.