Object reference

This page provides a reference for all of the different objects that the Baack APIs return. These reference docs are intended to provide detailed information on the different representations sent by endpoints.

Address V1

Postal or location address used by CRM and identity representation

API Client V1

Representation of an API client

API Client Bearer Token V1

Representation of a bearer token used to authenticate an API request

OAuth Token V1

Representation of an OAuth token. These are typically granted during oauth flows and may include access and refresh tokens.

Boolean Item V1

A boolean content item associatedwith a content entity

Boolean item history V1

Representation of the history of a boolean (truthy) content item value

Client Context V1

Representation of the client context metadata to allow callers to understand the current client session state. The client context may be using a regular web session (in the case of your client accessing content via a logged in user session), a bearer token either from a secure server to server context or a bearer token from an insecure browser client. The response JSON will let you understand your session state in order to trigger experiences like logging in a user to allow them to use client features like the Editor or Tasks clients.

Client Identifier V1

Client identifiers are associated with identities and are typically used to uniquely identify a particular identity in the scope of a particular domain e.g. Google SignIn profile ID or other platform user identifier.

Company Page V1

A page of companies

Company V1

Representation of a company object which may have a parent company (in structured companies), an owner, if this company represents some CRM company owned by a customer company and an organisation for which this company and associated accounts are provisioned.

Date Time Item V1

Date time represented as ISO 8601 with milliseconds

Date / Time item history V1

Representation of a date / time timestamp (UTC) item value history

Double Item V1

A double precision content item associated with a content entity

Double Item History V1

The history of values of a double item

Email V1

Representation of an email address associated with an identity

Entity V1

A content entity, similar to a page with a collection of content items of differing types

Entity List V1

Entity list for a collection of entity references. Note that the returned entity list on read will respect the natural ordering of the entity order sort order field

Entity List Item V1

Entity list item reference and sorting order

Error V1

General API error object representation

Group V1

A group of identities (people) which can be used for various purposes like permissions or collections of identities like a mailing list or a community

Group Membership V1

Representation of a group membership configuration. Note that the presence of a membership does not imply that the membership is active. Review the state for details of the current state. To support opt out and other negative preferences the state includes options for opt out of a group either by the member or the owner.

Identity V1

Identity encapsulates all information associated with a person's identity like their contact details, associated addresses etc. The identity representation is used in multiple contexts and use cases like the identity of people in CRM as well as in the context of other use cases like role based access control or group membership.

Image Item V1

Object representing an image resource

Image item history V1

Representation of the history of an image content item

Image Item File V1

Image files are transferred using multipipart/form-data which is widely supported by HTTP clients and browsers to submit files. The endpoint allows upload of a single 'src' file which will be associated with either the default, large or medium format file according to the value of the imageItemFormat

JSON Item V1

Representation of a JSON content entity for arbitrary JSON values

Json item history V1

Representation of the history of a JSON item

Markdown Item V1

A markdown item value associated with a particular entity

Markdown item history V1

Representation of the markdown item history. Note that the history is ordered from newest to oldest and may be paginated.

Message Thread V1

Representation of a message thread which can be used for general chat or discussions associated with other concepts.

Money Item V1

A money value item in the context of a content entity

Money item history V1

Representation of a money content item history

Latitude / Longitude item V1

Latitude / Longitude content item associated with an entity

Lat / Long item history V1

Representation of the history of lat / long content item history

Long item V1

Representation of a long integer item

Long item history V1

Representation of the history of a long integer content item. Note that history is returned from newest to oldest value

Organisation V1

Representation of an organisation which holds multiple account related companies which own data regarding other companies in the platform etc.

Payment Invoice Identifier V1

Payment invoice identifier e.g. invoice ID

Payment Invoice V1

Representation of a payment invoice

Payment Invoice Line V1

Payment invoice line item

Permission V1

Representation of a permission grant. Permissions are fail closed so if an object requires a permission it must be present for the subject with the given label.
Permissions represent directed edges granting a subject(type) [label] to object(type). When applied to an object the permissions will be checked for an exists style relationship from the subject scope.

Role V1

A role in role based access control context which can be associated with various actors

Person V1

Representation of a person associated with an identity

Person Name V1

Name associated with a person (may be an alias)

Project V1

Representation of a project which can be used to collect a set of tasks with workflows.

Recipient V1

The recipient representation is used to model a payment invoice recipient either as a company or identity.

Remitter V1

The remitter or payee is the company or identity which is making the payment in the context of a payment or invoice

Search Item V1

A search result item

Subject V1

A subject reference typically used in the context of a task activity log e.g. when a task is assigned the subject would be the assignee

Task V1

Representation of a task with references to associated concepts as well as baseline fields for managing tasks

Task Log V1

Representation of a single task log entry related to a tasks history of activities

Telephone V1

Representation of a telephone number

Template Item V1

Object representing a template content item associated with a content entity

Template item history V1

Representation of the history of a template item values

Text Item V1

A text content item associated with a content entity

Text Item History V1

Representation of the history of a text item including all of the revisions stored which may be paged if they exceed the maximum per response.

Thread post V1

Representation of a post or message in a thread of messages

User V1

Representation of a session user returned in contexts like the API client context when user based authentication is being used

Webhook Event V1

The webhook event representation is used for webhook message delivery acting like an envelope for the event.

Webhook Event Target V1

Representation of the concept that a webhook trigger event relates to

Webhook Subscription V1

Representation of a webhook subscription to listen for events supported by the given subject

Webhook Trigger V1

Representation of a unique webhook trigger event

Workflow V1

Workflow representation which holds a collection of stages

Workflow Stage V1

A single stage in a workflow