Skip to content
WeZend

Customer Data Platform

Objects: companies and accounts for your contacts

Model a company, account, subscription or course with its own attributes, relate contacts to it, and use it in segments, messages and journeys.

An object is anything a contact belongs to that has data of its own: a company, an account, a subscription, a course. An object is identified by its type (a lower-case key you choose, such as company) and an external id, the id from your own system, so saving the same one again updates it. A contact can belong to many objects and an object can hold many contacts, with an optional role such as owner or member.

Attributes are scalars only (text up to 1,000 characters, number, boolean or null), at most 50 per object; names become snake_case. Nested values are refused rather than silently dropped.

API

/v1/objects works with an API key or a login (read and write capabilities).

CallWhat it does
GET /v1/objectsthe types you have, with a count of each
GET /v1/objects/:typethe objects of a type (limit up to 200, offset)
PUT /v1/objects/:type/:externalIdcreate or update; attributes are merged, null removes a key, replace: true replaces all
GET / DELETE /v1/objects/:type/:externalIdread or delete one (its links go with it)
GET / POST /v1/objects/:type/:externalId/contactslist who belongs to it, or relate a contact (contact_id or email, optional role)
DELETE /v1/objects/:type/:externalId/contacts/:contactIdremove a link
GET /v1/objects/by-contact/:contactIdthe objects one contact belongs to

In messages

{{ objects.company.name }} is the first company the contact belongs to; object_lists.company is all of them, for a loop (see Liquid). A contact with no object of a type prints nothing.

In segments

The builder lists every object type under "Companies and objects": "Belongs to a <type>" and one condition per attribute seen on that type. A condition matches when some object of that type the contact belongs to matches.

In journeys

A change is recorded as an event for each contact in the object: object_updated (with the names that changed, never the values), object_linked and object_unlinked. A journey whose trigger is one of these starts for those people. A Segment-compatible source group call creates a company object and links the person.

Erasure

Erasing a contact deletes their links to objects. The object stays: it is your record of a company, not that person's data.

One platform. Every customer interaction.

Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.

No credit card required · EU data residency · 99.99% uptime SLA