A WireMock simulation of Tavily's REST API — covering batch generation of development and production keys, key info lookups, and deactivation of single keys or whole batches.
A shared instance of this template runs on a public endpoint — call it right now from curl, an SDK, or an AI agent. Responses are fixed examples and behavior can't be changed; rate limits apply.
Jump to the endpoints ↓Run this template as a mock API in WireMock Cloud for a private instance you control — edit stubs, add stateful scenarios, use dynamic response templating, and inspect requests in the log.
Open in WireMock Cloud (free) →Live sandbox · no signup, no API key
A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.
Endpoints
POST Generate API Keys [generateKeys]
curl -s -X POST 'https://g47yr6.wiremockapi.cloud/generate-keys' \
-H 'Content-Type: application/json' \
-d '{}'GET Get Key Info [getKeyInfo]
curl -s -X GET 'https://g47yr6.wiremockapi.cloud/key-info'POST Deactivate API Keys [deactivateKeys]
curl -s -X POST 'https://g47yr6.wiremockapi.cloud/deactivate-keys' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Tavily Enterprise API Key Generator (1.0.0) · 3 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /deactivate-keys | Deactivate API Keys |
| POST | /generate-keys | Generate API Keys |
| GET | /key-info | Get Key Info |
Unauthenticated WireMock Cloud demo sandbox for Tavily — not an official Tavily sandbox, and it returns simulated example data only.
The template simulates Tavily's enterprise service for issuing API keys programmatically. A generate call returns a batch of keys in the tvly-dev- or tvly-prod- format, an expiry derived from ttl_hours and a request_id for the batch. Every key is remembered, so key-info reports its name, type and status, and deactivating the batch shows up on its next lookup. Provisioning code that hands out short-lived keys to users or agents can run the whole cycle against it.
A batch's keys take the batch name with a suffix, so a two-key batch called probe yields probe-#1 and probe-#2. Without a name, each key gets the key type and expiry with the same numbering, as Tavily's spec describes.
After its batch or the key itself is deactivated, or once its TTL has passed. Before that key-info reports it active, which makes expiry logic testable by generating a key with a short ttl_hours.
It returns default info: name default, expires_at never, and a type read from its prefix. Invalid admin keys aren't rejected either, because Tavily's documentation doesn't define those errors.
No, it's a separate host. Search, extract and research calls live in the Tavily Search and Extract template.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.