---
title: "Get Webhooks"
method: GET
path: "/v2/webhooks"
tags: ["Routes", "Webhooks"]
---

# Get Webhooks

`GET /v2/webhooks`

This request returns your Webhooks configured for Limble. 

Return data description

Property: webhhokID, Description: The ID of the Webhook
Property: endpoint, Description: The webhook URL.
Property: type, Description: The type of webhook. Webhooks can be of type task, po, poItem.
Property: enabled, Description: Determines if the webhook is enabled. 0 = Disabled 1=Enabled

## Query parameters

- `webhooks` integer
- `endpoint` string
- `type` string
- `enabled` integer
- `cursor` integer
- `limit` integer

## Response `200`

Get Webhooks

- object[]
  - `webhookID` integer
  - `endpoint` string, uri
  - `type` string
  - `enabled` 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)