Create a site
Create a new site for the partner the API key belongs to. The public site contract maps onto the internal Address-backed create flow. customProperties accepts the custom properties defined for your partner, keyed by property id; send null to clear one. Requires the site:write scope. Supports include=clients to expand the created site.
Authorizations
Send the API key in the x-api-key header.
Query Parameters
Comma-separated relations to expand on the response
"clients,projects"
Body
1"1234 Elm Street"
1"Austin"
1"TX"
11^ovcid-.*$essentials_plus, priority, security_only, proactive, signature Platform user id. Newer ids are ovuid-<uuid>; legacy users may have bare (e.g. numeric) ids.
1"ovuid-2b6d4d8e-9f1a-4b2c-8d4e-5f6011223344"
Custom property values, keyed by property id. Ids and value types come from the properties defined for your partner, so this object cannot be described field by field here: an unknown id or a value that does not match the property type is rejected with 400. Only the ids you send are modified — omit a property to leave it untouched. To clear one, send null; a blank string and an empty array count as empty too, for every property type alike.
^ovcid-.*$Response
Created site
Inactive, Non-Member, Warranty Essentials, CPP Essentials Plus, Essentials Plus, CPP Priority, Priority, CPP Proactive, Proactive, CPP Signature, Signature, Secure, OV - Internal, Legacy Custom property values, keyed by property id. Ids and value types come from the properties defined for your partner, so this object cannot be described field by field here — call the custom-property list endpoint to resolve an id to its name and type. A property never given a value takes the default configured for it, and is left out rather than returned as null when there is no default either. A value stored before its property was changed — an option renamed or removed, the type switched — is returned as stored, so it may not match the type the property has today; an absent key is the only reliable sign that nothing is set.