# Retrieve a gateway account limit Retrieves a gateway account limit with a specified ID. Endpoint: GET /gateway-accounts/{id}/limits/{limitId} Version: latest Security: SecretApiKey, JWT ## Path parameters: - `id` (string, required) ID of the resource. - `limitId` (string, required) ID of the gateway account limit. Enum: "daily-money", "monthly-money", "daily-count", "monthly-count" ## Response 200 fields (application/json): - `id` (string) Unique resource ID. Example: "4f6cf35x-2c4y-483z-a0a9-158621f77a21" - `status` (string) Status of the gateway account limit. Enum: "monitoring", "reached" - `startTime` (string) Date and time when the gateway account limit starts. - `endTime` (string) Date and time when the gateway account limit ends. When a gateway account limit ends the limit resets. - `frequency` (string) Frequency at which the gateway account limit period resets. Enum: "daily", "monthly" - `type` (string) Type of gateway account limit. Enum: "money", "count" - `cap` (integer, required) Limits the maximum allowed value. If is set to , the currency is the report currency. only applies to approved transactions of type or . Example: 1000 - `usage` (integer) Usage of the gateway account limit during this period. Example: 375 - `createdTime` (string) Date and time which is set automatically when the resource is created. - `updatedTime` (string) Date and time which updates automatically when the resource is updated. - `_links` (array) Related links. - `_links.href` (string) Link URL. - `_links.rel` (string) Type of link. Enum: "self" ## Response 401 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 403 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. ## Response 404 fields (application/json): - `status` (integer) HTTP status code. - `type` (string) Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference. It should provide human-readable documentation for the problem type. When this member is not present, its value is assumed to be "about:blank". - `title` (string) Short, human-readable summary of the problem type. Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem. - `detail` (string) Human-readable explanation that is specific to this occurrence of the problem. - `instance` (string) URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.