For Agents
Subscribe, update, and remove webhook endpoints that receive Tolstoy interactive-video events such as lead form submissions and viewer responses.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tolstoy Webhooks API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgotolstoy.com%2Ftolstoy" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgotolstoy.com%2Ftolstoy" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Tolstoy Webhooks API.
Register a webhook URL to receive Tolstoy lead form submission events
List all webhook subscriptions configured on a Tolstoy account
Retrieve a single webhook subscription by webhook ID
GET STARTED
Use for: I need to subscribe a Slack relay to Tolstoy lead form submissions, List all Tolstoy webhook subscriptions on the account, Update the callback URL on an existing Tolstoy webhook, Delete a stale Tolstoy webhook subscription
Not supported: Does not handle video upload, video playback, or analytics queries - use for managing Tolstoy webhook subscriptions only.
The Tolstoy Webhooks API lets developers register, list, update, and delete webhook subscriptions for Tolstoy interactive video events such as viewer responses, lead form submissions, and product clicks. Tolstoy is a video marketing platform and this API is the integration surface for piping Tolstoy events into CRMs, marketing automation, and analytics systems. Subscriptions are managed by webhook ID, secured by a bearer token, and scoped per Tolstoy account.
Update the URL or event types attached to an existing webhook
Delete a webhook subscription when the downstream consumer is decommissioned
Patterns agents use Tolstoy Webhooks API for, with concrete tasks.
★ Lead Capture Pipeline
When viewers submit a lead form embedded in a Tolstoy interactive video, route the lead in real time to a CRM or marketing automation platform. The Tolstoy Webhooks API registers the receiving URL via POST /webhooks/, and Tolstoy delivers each lead event to that endpoint as it happens. Setup time is under 30 minutes once the receiving endpoint is in place.
Register a webhook with URL https://example.com/tolstoy and confirm the returned webhook ID is stored for later updates.
Webhook Inventory Audit
Periodically list all webhook subscriptions on the Tolstoy account to find dead URLs, duplicates, or unintended subscriptions added during testing. GET /webhooks/ returns every active subscription so an operations agent can reconcile the list against an internal source of truth and remove orphans.
List all Tolstoy webhook subscriptions and return a summary of each webhook ID with its target URL.
Subscription Lifecycle Management
Manage the full webhook lifecycle from creation through to retirement. The Tolstoy Webhooks API exposes PUT /webhooks/{webhookId}/ to update an endpoint when downstream URLs change and DELETE /webhooks/{webhookId}/ to remove subscriptions cleanly. This avoids piling up dead subscriptions that fire to non-existent listeners.
Update webhook ID abc123 to point at https://new.example.com/tolstoy and verify the change took effect by re-fetching the webhook.
AI Agent Webhook Operations
An AI ops agent built on Jentic uses the Tolstoy Webhooks API to keep marketing event delivery healthy: it lists webhooks weekly, deletes stale ones, and re-registers any that fail health checks. The agent searches Jentic for 'manage tolstoy webhooks', loads the right operation, and executes it without holding the bearer token directly.
Use Jentic to search 'list tolstoy webhooks', load the operation, and return any webhooks whose URL host is unreachable.
5 endpoints — the tolstoy webhooks api lets developers register, list, update, and delete webhook subscriptions for tolstoy interactive video events such as viewer responses, lead form submissions, and product clicks.
METHOD
PATH
DESCRIPTION
/webhooks/
Register a new webhook subscription
/webhooks/
List all webhook subscriptions
/webhooks/{webhookId}/
Retrieve a single webhook subscription
/webhooks/{webhookId}/
Update an existing webhook subscription
/webhooks/{webhookId}/
Delete a webhook subscription
/webhooks/
Register a new webhook subscription
/webhooks/
List all webhook subscriptions
/webhooks/{webhookId}/
Retrieve a single webhook subscription
/webhooks/{webhookId}/
Update an existing webhook subscription
/webhooks/{webhookId}/
Delete a webhook subscription
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Tolstoy Webhooks API by hand means implementing its bearer auth and managing the webhook subscription lifecycle across create, read, update, and delete calls yourself. Through Jentic you install once, import Tolstoy from the API Directory, store the token once, and your agent calls it.
Permission scoping
Tolstoy puts the webhook id in the URL path (/webhooks/{webhookId}/), so a rule can pin your agent to one webhook subscription: it can read and update that subscription and nothing else. You choose the operations it may call, so deleting a webhook is not included unless you add it.
Credential isolation
Your Tolstoy bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list tolstoy webhooks' or 'register a webhook for video events', and Jentic returns the matching Tolstoy operation with its input schema so the agent calls the right endpoint immediately.
Alternatives and complements available in the Jentic catalogue.
Specific to using Tolstoy Webhooks API through Jentic.
What authentication does the Tolstoy Webhooks API use?
The Tolstoy Webhooks API uses HTTP bearer authentication. Each request must carry an Authorization: Bearer header with a Tolstoy account token. When called through Jentic, the bearer token is held in Jentic's encrypted vault and is injected at request time so the agent never sees the raw token.
Can I update the callback URL on an existing Tolstoy webhook?
Yes. PUT /webhooks/{webhookId}/ accepts an updated payload for an existing subscription, so you can point the same webhook at a new URL without losing the subscription ID. This is useful when migrating receivers between environments.
What are the rate limits for the Tolstoy Webhooks API?
Rate limits are not declared in the OpenAPI spec. Webhook management calls are typically infrequent compared to event delivery, so a small handful of requests per minute is expected to be safe. Back off on HTTP 429 responses if encountered.
How do I register a Tolstoy webhook through Jentic?
Search Jentic for 'subscribe to tolstoy events', load the POST /webhooks/ operation, and execute with the target URL in the request body. With pip install jentic, registering a webhook is a three-step search, load, execute flow with no need to manage the bearer token in agent code.
Does the Tolstoy Webhooks API send the events themselves, or only manage subscriptions?
This API only manages webhook subscriptions. Once a webhook is registered, Tolstoy itself delivers event payloads to the URL you provided. The API surface here covers create, read, update, and delete operations on the subscription records.