Account labels give accounts more descriptive names that are displayed anywhere the accounts are referenced in the product and in reports. Account labels is an optional feature that must be enabled when configuring Accounts Payable.
Returns up to 100 object references from the collection with a key, ID, and link for each label. This operation is mostly for use in testing; use query to find objects that meet certain criteria and to specify properties that are returned.
Subscription | Accounts Payable |
---|---|
User type | Business |
Permissions | List account labels |
OK
Bad Request
{- "ia::result": [
- {
- "key": "32",
- "id": "Ref Matls",
- "href": "/objects/accounts-payable/account-label/32"
}, - {
- "key": "33",
- "id": "Rent",
- "href": "/objects/accounts-payable/account-label/33"
}, - {
- "key": "34",
- "id": "Repairs and Maintenance",
- "href": "/objects/accounts-payable/account-label/34"
}
], - "ia::meta": {
- "totalCount": 3,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}
Creates a new account label.
Subscription | Accounts Payable |
---|---|
User type | Business |
Permissions | Add account labels |
id required | string Name or other unique identifier for the account label. Example: "Benefits: Health" | ||||
description required | string A note about the purpose and use of the account label. Example: "Account for health benefit costs" | ||||
status required | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" | ||||
object The general ledger account to assign to the label. This is typically a revenue account. | |||||
| |||||
object The general ledger account where the system posts offsets to items posted to this label. This is typically a receivables account. | |||||
| |||||
object Form 1099 information. | |||||
|
Created
Bad Request
{- "id": "Sales",
- "description": "Sales team expenses",
- "status": "active",
- "glAccount": {
- "id": "4000--Sales"
}, - "offsetGLAccount": {
- "id": "4001--Miscellaneous - Sales"
}
}
{- "ia::result": {
- "key": "37",
- "id": "Sales",
- "href": "/objects/accounts-payable/account-label/37"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Returns detailed information for a specified account label.
Subscription | Accounts Payable |
---|---|
User type | Business |
Permissions | List, Edit account labels |
key required | string System-assigned key for the account label. |
OK
Bad Request
{- "ia::result": {
- "key": "8",
- "id": "Accounting Fees",
- "description": "Accounting Fees",
- "glAccount": {
- "id": "6600.01--Accounting Fees",
- "key": "318",
- "href": "/objects/general-ledger/account/318"
}, - "status": "active",
- "offsetGLAccount": {
- "id": null,
- "key": null
}, - "form1099Type": "DIV",
- "form1099Box": "1B",
- "href": "/objects/accounts-payable/account-label/8"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Updates an existing account label by setting field values. Any fields not provided remain unchanged.
Subscription | Accounts Payable |
---|---|
User type | Business |
Permissions | List, Edit account labels |
key required | string System-assigned key for the account label. |
description | string A note about the purpose and use of the account label. Example: "Account for health benefit costs" | ||||
status | string Default: "active" Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced. Example: "active" | ||||
object The general ledger account to assign to the label. This is typically a revenue account. | |||||
| |||||
object The general ledger account where the system posts offsets to items posted to this label. This is typically a receivables account. | |||||
| |||||
object Form 1099 information. | |||||
|
OK
Bad Request
{- "description": "This is Sales Account label",
- "status": "active",
- "offsetGLAccount": {
- "id": "4000.03--Sales-Others"
}
}
{- "ia::result": {
- "key": "37",
- "id": "Sales",
- "href": "/objects/accounts-payable/account-label/37"
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 1,
- "totalError": 0
}
}
Deletes an account label.
Subscription | Accounts Payable |
---|---|
User type | Business |
Permissions | List, Delete account labels |
key required | string System-assigned key for the account label. |
No Content
Bad Request
{- "ia::result": {
- "ia::error": {
- "code": "invalidRequest",
- "message": "A POST request requires a payload",
- "errorId": "REST-1028",
- "additionalInfo": {
- "messageId": "IA.REQUEST_REQUIRES_A_PAYLOAD",
- "placeholders": {
- "OPERATION": "POST"
}, - "propertySet": { }
}, - "supportId": "Kxi78%7EZuyXBDEGVHD2UmO1phYXDQAAAAo"
}
}, - "ia::meta": {
- "totalCount": 1,
- "totalSuccess": 0,
- "totalError": 1
}
}
Queries an object for filtered data.
object | string Object type to query, in the form Example: "accounts-payable/account-label" | ||||||||
fields | Array of strings List of fields to include in the response. Can be any combination of these:
Example: ["key","id","max:vendor.creditLimit"] | ||||||||
Array of equal (object) or not equal (object) or less than (object) or (less than or equal (object)) or greater than (object) or (greater than or equal (object)) or in (object) or not in (object) or between (object) or not between (object) or contains (object) or does not contain (object) or starts with (object) or does not start with (object) or ends with (object) or does not end with (object) Filter conditions to select the objects to return based on their field values. You use operators and conditions to build your filter, such as Example: [{"$eq":{"status":"active"}},{"$gt":{"totalDue":"1000"}},{"$contains":{"name":"Acme"}}] | |||||||||
Array Any of: Field value must be equal to this specified value. For date fields, you can use these macro values that are relative to the current date or the
These are most useful for queries that you want to save and use repeatedly, such as for views or reports. Just change the For example,
| |||||||||
filterExpression | string Default: "and" Logical operators to apply when there are multiple filter conditions. The conditions in the Shortcuts:
Example: "(1 and 2) or 3" | ||||||||
| |||||||||
Array of objects Set the order of the results by specifying field names to sort by and whether they should be in ascending or descending order. Example: [{"totalDue":"asc"},{"lastPaymentMadeDate":"desc"}] | |||||||||
Array
| |||||||||
start | integer First record of the result set to include in the response. Example: 1 | ||||||||
size | integer Number of records to include in the response. Example: 100 |
OK
Bad Request
{- "object": "accounts-payable/account-label",
- "filters": [
- {
- "$eq": {
- "status": "active"
}
}
], - "fields": [
- "key",
- "id",
- "description",
- "href"
], - "orderBy": [
- {
- "id": "asc"
}
]
}
{- "ia::result": [
- {
- "key": "16",
- "id": "HR",
- "description": "Product team expenses",
- "href": "/objects/accounts-payable/account-label/16"
}, - {
- "key": "17",
- "id": "Ops",
- "description": "Ops team expenses",
- "href": "/objects/accounts-payable/account-label/17"
}, - {
- "key": "15",
- "id": "Sales",
- "description": "Sales team expenses",
- "href": "/objects/accounts-payable/account-label/15"
}
], - "ia::meta": {
- "totalCount": 3,
- "start": 1,
- "pageSize": 100,
- "next": null,
- "previous": null
}
}