Skip to main content
POST
Create a custom object

Authorizations

x-conveyour-token
string
header
required

Your API key token. Contacts endpoints require a Server-only — Full API key — see Authentication.

Query Parameters

teams[]
string[]

Team scope for the request, as one or more team ObjectIds. The brackets are required: PHP keeps only the last value for a repeated plain key, so teams=A&teams=B silently resolves to B alone. On requests with a JSON body you may send teams (no brackets) in the body instead.

Values that are not valid ObjectIds are silently ignored — a mistyped team ID behaves as if no team was sent. See the teams section of the API conventions guide.

Body

application/json
name
string
required

Short, singular identifier for this object type (e.g. "vehicle") — think of it like a tag. Must be unique within your org.

label
string
required

The singular human-readable label (e.g. "Vehicle"). Must be unique.

label_plural
string
required

The plural human-readable label (e.g. "Vehicles"). Must be unique.

schema
object

A map keyed by field name — each key is the field's identifier and each value is { "title": "...", "type": "..." }. title and type are required per field; type must be a StudlyCase value (see GET /api/custom/objects/schema). This is an object, not an array — passing an array creates fields named 0, 1, 2.

Response

Success.

The common response envelope shared by all ConveYour endpoints.

status
enum<string>

ok on success, failed on error.

Available options:
ok,
failed
message
string

Human-readable description of the result.

data
object

A custom object definition. Reads the schema off the stored record, so the field set varies per organization.