Abilities
General Ledger
>
API Reference
>
v1
>
Abilities
openapi: 3.0.3
info:
title: General Ledger API - Abilities
version: v1
description: API to interact with General Ledger
contact:
name: General Ledger
url: https://www.jackhenry.com/
email: DC-LedgerServices-Product@jackhenry.com
servers:
- url: https://{API_ENDPOINT}
variables:
API_ENDPOINT:
default: digital.garden-fi.com
security:
- bearerAuth: []
tags:
- name: Abilities
description: APIs for user specific abilities in general ledger
paths:
/a/api/general-ledger/v1/{InstitutionUniversalId}/enterprise/{EnterpriseUserId}/abilities:
get:
operationId: GetAbilities
tags:
- Abilities
summary: Get abilities
description: Retrieve the abilities for the specified user.
parameters:
- name: InstitutionUniversalId
in: path
description: A unique identifier to establish the identity of an Institution/Environment/Brand combination
required: true
schema:
type: string
- in: path
name: EnterpriseUserId
required: true
schema:
type: string
format: uuid
description: The ID of the enterprise user.
responses:
'200':
description: A list of abilities
content:
application/json:
schema:
type: object
required:
- createAccounts
- editAccounts
- deleteAccounts
- readTransactions
- reverseTransactionSets
- postTransactionSets
- importTransactions
- importAccounts
- createLinks
- editLinks
- editSettings
- createTotalingGroups
- editTotalingGroups
- deleteTotalingGroups
- viewReports
properties:
createAccounts:
type: boolean
default: false
example: true
editAccounts:
type: boolean
default: false
example: true
deleteAccounts:
type: boolean
default: false
example: true
reverseTransactionSets:
type: boolean
default: false
example: true
postTransactionSets:
type: boolean
default: false
example: true
importTransactions:
type: boolean
default: false
example: true
importAccounts:
type: boolean
default: false
example: true
createLinks:
type: boolean
default: false
example: true
editLinks:
type: boolean
default: false
example: true
editSettings:
type: boolean
default: false
example: true
createTotalingGroups:
type: boolean
default: false
example: true
editTotalingGroups:
type: boolean
default: false
example: true
deleteTotalingGroups:
type: boolean
default: false
example: true
viewReports:
type: boolean
default: false
example: true
'400':
description: The server could not understand the request due to an invalid request.
content:
application/problem+json:
schema:
type: object
required:
- type
- title
- details
properties:
type:
description: A string path which uniquely classifies the domain of the error.
type: string
nullable: false
example: jackhenry/operation-failed
title:
description: A end-user readable string title of the error type.
nullable: false
type: string
details:
description: An array of end-user readable strings which provide additional details for the error message.
type: array
nullable: false
items:
type: string
data:
type: object
description: |
Additional data that could be useful to a developer or for handing the error programmatically. The schema for the data in this object is intentionally left undefined.
nullable: true
'401':
description: Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
'403':
description: The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the clients identity is known to the server.
'404':
description: The server can not find the requested resource. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client.
'500':
description: An unexpected internal server error occurred while processing the request.
content:
application/problem+json:
schema:
type: object
required:
- type
- title
- details
properties:
type:
description: A string path which uniquely classifies the domain of the error.
type: string
nullable: false
example: jackhenry/operation-failed
title:
description: A end-user readable string title of the error type.
nullable: false
type: string
details:
description: An array of end-user readable strings which provide additional details for the error message.
type: array
nullable: false
items:
type: string
data:
type: object
description: |
Additional data that could be useful to a developer or for handing the error programmatically. The schema for the data in this object is intentionally left undefined.
nullable: true
examples:
internalServerError:
summary: Internal server error
value:
type: general/internal-server-error
title: Internal server error
details:
- Unexpected internal server error
Did this page help you?
Why was this page helpful?
Why wasn't this page helpful?
Thank you for your feedback!
Last updated Mon Jan 5 2026