How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tabby Webhooks API

Manage webhook endpoints.

Tabby Webhooks API is one of 4 APIs that Tabby publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include Webhook. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 7 JSON Schemas.

This API exposes 5 operations across 2 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.tabby.ai/, https://api.tabby.sa/.

5 operations 2 paths 13 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.tabby.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Tabby Webhooks API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — Bearer authentication header of the form Bearer , where is your secretkey.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Webhooks 5

Manage webhook endpoints.

POST
/api/v1/webhooks
Register a webhook
postWebhook 1 param body → 200400401404500
GET
/api/v1/webhooks
Retrieve all webhooks
getWebhooks 1 param → 200401404500
GET
/api/v1/webhooks/{id}
Retrieve a webhook
getWebhook 2 params → 200401404500
PUT
/api/v1/webhooks/{id}
Update a webhook
putWebhook 2 params body → 200400401403404500
DELETE
/api/v1/webhooks/{id}
Remove a webhook
deleteWebhook 2 params → 200401404500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are Webhook (4 properties), WebhookRegistrationResponse (4 properties), Error_401_authorization (3 properties), Error_400_bad_request (3 properties). Each schema is shown below with its type and property counts.

Error_500
string
Error_404_no_such_webhook
object
3 properties
WebhookRegistration
object
2 properties 1 required
WebhookUpdate
object
3 properties 2 required
WebhookRegistrationResponse
object
4 properties 2 required
Error_400_bad_request
object
3 properties
Error_401_invalid_secret_key
object
3 properties
WebhookResponseAll
Error_403
object
2 properties
Error_401_authorization
object
3 properties
Error_404
string
WebhookDelete
object
1 property
Webhook
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tabby-webhooks-api-openapi.yml Raw ↑

Other APIs Tabby publishes across the network.

Tabby Checkout API
Tabby Disputes API
Tabby Payments API
Where this information came from

This is an independent, third-party profile of Tabby Webhooks API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.