---
title: "Get General Ledgers"
method: GET
path: "/v2/gl"
tags: ["Routes", "General Ledgers"]
---

# Get General Ledgers

`GET /v2/gl`

This request returns your GLs in Limble. 

Return data description

Property: glID, Description: The GL's unique identifier.
Property: abbr, Description: An abbreviation for the GL.
Property: name, Description: The full name of the GL.
Property: locationID, Description: Which Location this GL belongs to.
Property: description, Description: An optional bit of descriptive text for the GL.
Property: assetID, Description: Which Asset this GL belongs to.

## Query parameters

- `cursor` integer
- `limit` integer
- `name` string
- `abbr` string
- `locations` string
- `gls` string
- `assets` string

## Response `200`

Get General Ledgers

- object[]
  - `glID` integer
  - `abbr` string
  - `name` string
  - `locationID` integer
  - `description` string
  - `assetID` integer

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/revisions/20801e23f7f2/schema)