SPEND: Spend types
The SPEND entity: A spend type category used to classify costs on project forecasts, such as hardware, software, internal labour, external labour, or 3rd party services.
Default definition. This article describes the default
SPEND definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches SPEND.Entity properties
| Property | Value |
|---|---|
| Entity code | SPEND |
| Display name | Spend types |
| Plural | Spend types |
| Level | 210 |
Use cases
SPEND is a simple configuration entity at level 210 with bulkActions enabled. The General panel has a single 33-width column with one form section containing just a name field. Used as a lookup value by project forecast line items to categorise spend.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
Relationships
- No declared relationships in the default definition.
Creating a Spend types via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SPEND",
"level": 210,
"comboKey": "SUB:|ENT:",
"name": "Example name"
} Listing Spend types records
GET /v1/entities/SPEND/SUB