Datastores (Base Entity)

Entity›Datastore

Datastores are lookup tables that hold reference values used throughout TribeCRM — phases, countries, genders, payment methods, units, VAT groups, and many more. They provide the dropdown options and configuration values that other entities reference.

The Datastore endpoint provides a unified view across all datastore types. Use the subtype-specific endpoints (e.g., Datastore_Country, Datastore_Phase_ActivityInvoice) when you need to work with a single type.

Base Entity

Datastore is a base entity. Most datastore subtypes are read-only and managed through the Tribe CRM UI. See Subtypes for the full list.

Endpoints

List Datastores

Retrieve a paginated list of all datastore values across all types.

GET/v1/odata/Datastore

Single Datastore

GET/v1/odata/Datastore({id})

Subtypes

Datastore is the abstract parent type. All subtypes:

Subtype	OData Entity Set	Description
Address Types	Datastore_AdressType	Address type classification
Aggregates	Datastore_Aggregate	Aggregation methods
Alignments	Datastore_Alignment	Layout alignment options
Appointment Types	Datastore_AppointmentType	Appointment categories
Branches	Datastore_Branch	Industry branches
Calendar Attendee Statuses	Datastore_CalendarItemAttendeeResponseStatus	Calendar response statuses
Campaign Types	Datastore_Campagne	Campaign categories
Channels	Datastore_Channel	Communication channels
Contact Roles	Datastore_Role	Contact role definitions
Countries	Datastore_Country	Countries
Data Category Layouts	Datastore_DataCategory_Layout	Dataset category layouts
Education Levels	Datastore_Education	Education levels
Email Address Types	Datastore_EmailAddressType	Email address types
Emailing Categories	Datastore_EmailingCategory	Email subscription categories
Event Locations	Datastore_EventLocation	Event venues
Event Participation Statuses	Datastore_EventParticipationStatus	Event attendance statuses
Event Types	Datastore_EventType	Event categories
Functions	Datastore_Function	Job functions
Genders	Datastore_Gender	Gender options
General Ledger Accounts	Datastore_GeneralLedgerAccount	Accounting ledger accounts
Groups	Datastore_Group	Relationship groups
Identification Types	Datastore_KindOffIdentification	Identity document types
Industries	Datastore_Industry	Lead industry sectors
Involved Roles	Datastore_InvolvedRole	Activity participant roles
Languages	Datastore_Language	Languages
Legal Forms	Datastore_LegalForm	Legal forms (BV, NV, etc.)
License Contract Editions	Datastore_LicenseContractEdition	License editions
Lost Reasons	Datastore_LostReason	Opportunity lost reasons
Payment Methods	Datastore_PaymentMethod	Payment methods
Payment Statuses	Datastore_PaymentStatus	Payment statuses
Phone Number Types	Datastore_PhoneNumberType	Phone number types
Priorities	Datastore_Priority	Priority levels
Product Issue Causes	Datastore_ProductIssue_Cause	Product issue causes
Project Roles	Datastore_ProjectRole	Project roles
Reasons Lost	Datastore_ReasonLost	Additional lost reasons
Sales Categories	Datastore_SalesCategory	Sales categories
Sentiment Categories	Datastore_SentimentCategory	Sentiment classifications
Sentiment Topics	Datastore_SentimentTopic	Sentiment analysis topics
Skills	Datastore_Skill	Employee skills
Sources	Datastore_Source	Lead/opportunity sources
States	Datastore_State	States/provinces
Statuses	Datastore_Status	Relationship statuses
Task Types	Datastore_TaskType	Task categories
Trend Indications	Datastore_TrendIndication	Trend directions
Units	Datastore_Unit	Units of measure
Urgencies	Datastore_Urgency	Urgency levels
VAT Groups	Datastore_VatGroup	VAT groups

Phase Subtypes

Phases are a special category of datastores that define workflow stages for each activity type. See the dedicated Phases page for full documentation, fields, and usage examples.

Fields

Datastore Fields

Field	Type	Description
Name	String	Display name
Code	String	Unique code identifier
LocalizedName	String	Localized display name
IsDefault	Boolean	Whether this is the default value

Filtering Examples

warning

Filtering by _Type is not supported To narrow by datastore subtype, query that subtype's own entity set instead (e.g. /v1/odata/Datastore_Country, /v1/odata/Datastore_Phase). See Filtering by Type.

GET/v1/odata/Datastore?$filter=Name eq '{Name}'&$top={top}

GET/v1/odata/Datastore?$filter=Code eq '{Code}'&$top={top}

GET/v1/odata/Datastore?$filter=IsDefault eq {IsDefault}&$top={top}

GET/v1/odata/Datastore?$filter=contains(Name, '{Name}')&$top={top}

Custom Query

Build your own OData query against Datastore. Open Run and edit the whole request inline — swap the entity set, change the $filter, or add $expand, $select, $orderby, $top, $skip. Type $ for suggestions; use ↺ Reset to restore this example.

GET/v1/odata/Datastore?$top=10