---
title: "New Webhook"
method: POST
path: "/v2/webhooks"
tags: ["Routes", "Webhooks"]
---

# New Webhook

`POST /v2/webhooks`

This requests creates a new Webhook.

Parameter
Type
Required?
Description

endpoint
URL
Required
The webhook URL.

type
String
Required
The type of webhook. Refer to GET webhooks for type values

enabled
Int
Optional
Should the webhook be enabled or disabled. It is enabled(1) by default.

## Request body

- object
  - `endpoint` string, uri
  - `type` string
  - `enabled` integer

## Response `201`

New Webhook

- object
  - `webhookID` 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.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `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)