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

Zelto Buckets API

Reviewer routing — group conversations for batched review.

Zelto Buckets API is one of 11 APIs that Zelto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Buckets. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 6 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.zelto.ai.

6 operations 4 paths 4 schemas 1 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Zelto Buckets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Send Authorization: Bearer YOURAPIKEY. The key resolves to a single organization.

Paths & Operations 6

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

Buckets 6

Reviewer routing — group conversations for batched review.

GET
/v1/buckets
List buckets
listBuckets 3 params → 200401
POST
/v1/buckets
Create a bucket
createBucket body → 200400401403
GET
/v1/buckets/{id}
Get a bucket
getBucket 1 param → 200401404
GET
/v1/buckets/{id}/conversations
List conversations in a bucket
listBucketConversations 3 params → 200401404
POST
/v1/buckets/{id}/conversations
Add a conversation to a bucket
addConversationToBucket 1 param body → 200400401404
DELETE
/v1/buckets/{id}/conversations/{conversationId}
Remove a conversation from a bucket
removeConversationFromBucket 2 params → 204401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Conversation (10 properties), Bucket (8 properties), Error (3 properties), PageEnvelope (2 properties). Each schema is shown below with its type and property counts.

Bucket
object
8 properties 8 required
Conversation
object
10 properties 6 required
Error
object
3 properties 1 required
PageEnvelope
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zelto-buckets-api-openapi.yml Raw ↑

Other APIs Zelto publishes across the network.

Zelto Action checks API
Zelto Agents API
Zelto Companies API
Zelto Conversations API
Zelto Customer Metrics API
Zelto Experiments API
Zelto Findings API
Zelto Organizations API
Zelto Reports API
Zelto Reviews API
Where this information came from

This is an independent, third-party profile of Zelto Buckets 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.