Skip to main content
POST
Get GL accounts by UUIDs for a facility

Headers

x-api-key
any
required

Api key required to authenticate your request. Please reach out to monument for a key.

Example:

"monument-2230012-2312321"

Path Parameters

facilityUuid
string
required

Body

application/json
glAccountUuids
string<uuid>[]
required

Array of GL account UUIDs to retrieve data for

Example:

Response

200 - application/json

Successfully retrieved GL account data

glAccountUuid
string<uuid>
required

UUID of the GL account. It is the same identifier the ledger entries route reports per movement.

Example:

"9a1b2c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d"

facilityUuid
string<uuid>
required

UUID of the facility the account was requested for. Accounts are held by the organization behind the facility, not by the facility itself; this echoes the facility in the request path so a chart of accounts pulled facility by facility stays keyed.

Example:

"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"

glCode
string | null
required

GL code of the account, as entered by the operator in Settings → Billing & Taxes → GL Accounts. Null until they enter one; it is the field to map against an external chart of accounts.

Example:

"4000"

accountName
string
required

Name of the GL account. The accrual and cash accounts of the same item usually share this name, so read accountingBasis to tell them apart.

Example:

"Revenue - Rent"

accountCategory
enum<string>
required

Chart-of-accounts category the account falls under, which decides whether it is debited or credited by a movement.

Available options:
Asset,
Liability,
Revenue,
Expense,
Equity,
Contra-Revenue,
Contra-Liability
Example:

"Revenue"

accountingBasis
enum<string>
required

Accounting basis the account belongs to. ACCRUAL recognises the amount when the invoice is issued, CASH when the money is received.

Available options:
ACCRUAL,
CASH
Example:

"ACCRUAL"