Dubble API

Name: Dubble API API
Brand: Dubble API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbearer17 EndpointsREST

For Agents

Read, organise, and export Dubble guides, and subscribe to webhooks for guide events. Useful for agents that surface walkthroughs in support or onboarding flows.

Quickstart

Get started with Dubble API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"export a Dubble guide as Markdown"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Dubble API API.

List and read guides via GET /guides and GET /guides/{guideId}

Export guides as HTML or Markdown via /guides/{guideId}/html and /guides/{guideId}/markdown

Organise guides into collections via /collections and the collection-membership endpoints

Update or delete guides via PUT and DELETE on /guides/{guideId}

GET STARTED

Start building with Dubble API API

Explore with Jentic

View OpenAPI Document

Use for: I need to fetch a Dubble guide as Markdown for a docs site, List all guides in a specific collection, Create a new collection of guides for an onboarding flow, Subscribe to webhook events when a guide is updated

Not supported: Does not handle video recording, screen capture, or live editing — use for managing and exporting Dubble step-by-step guides only.

Jentic publishes the only available OpenAPI document for Dubble API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Dubble API, keeping it validated and agent-ready. Dubble is a step-by-step guide and documentation platform that captures workflows from a browser and turns them into shareable how-to articles. The API exposes 17 endpoints to manage guides and collections, retrieve guides as HTML or Markdown for embedding, and configure webhooks at the workspace or collection level. Authentication uses an OAuth-style bearer token.

Use Cases

Patterns agents use Dubble API API for, with concrete tasks.

★ Embed Dubble Guides in a Help Center

Pull Dubble step-by-step guides into a help center or in-app onboarding panel. The agent calls GET /guides to discover available content, then GET /guides/{guideId}/html to render the guide directly inside the support widget. This avoids re-authoring the same workflow content in two places.

Call GET /guides to list guides, then GET /guides/{guideId}/html for the chosen guideId and inject the HTML into the in-app help drawer

Sync Dubble Guides into a Static Docs Site

Mirror Dubble guides into a static documentation site by exporting each as Markdown on a schedule. The agent reads GET /guides for the current list, fetches /guides/{guideId}/markdown for content, and commits each file to a docs repository. Dubble webhooks let the sync run reactively when a guide changes.

On the guide.updated webhook, call GET /guides/{guideId}/markdown and commit the file to the docs/walkthroughs/ folder

Collection-Based Onboarding

Group guides into ordered collections that match an onboarding sequence. POST /collections creates the container and PUT /guides/{guideId}/collections/{collectionId} attaches a guide. The agent then surfaces the collection in the product, walking new users through one guide at a time and tracking completion via webhooks.

POST /collections to create 'New Customer Onboarding', then for each onboarding guideId call PUT /guides/{guideId}/collections/{collectionId}

Agent-Driven Documentation via Jentic

Wire Dubble into agent workflows that retrieve, transform, and publish how-to content. Through Jentic the agent searches by intent, loads the schema for /guides or /webhooks, and executes — the bearer token stays in the Jentic vault, not the agent's prompt context.

Search Jentic for 'export Dubble guide as Markdown', load the schema for GET /guides/{guideId}/markdown, and execute for each guide returned by GET /guides

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for dubble api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/guides

List guides

GET

/guides/{guideId}

Get a guide

GET

/guides/{guideId}/html

Get a guide rendered as HTML

GET

/guides/{guideId}/markdown

Get a guide rendered as Markdown

POST

/collections

Create a collection

POST

/webhooks

Create a webhook subscription

GET

/guides

List guides

GET

/guides/{guideId}

Get a guide

GET

/guides/{guideId}/html

Get a guide rendered as HTML

GET

/guides/{guideId}/markdown

Get a guide rendered as Markdown

POST

/collections

Create a collection

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Dubble bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access at execution, so the raw token never enters the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent (for example 'export a guide as Markdown' or 'list Dubble guides') and Jentic returns the matching Dubble operation with its input schema.

Time to first call

Direct Dubble integration: half a day for auth and content sync. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Loom API

Async video walkthroughs instead of step-by-step screenshots

Choose Loom when the workflow needs video; choose Dubble when guided clickable screenshots are the right format

Complementary

Rebrandly API

Branded short links for shared guide URLs

Pair with Dubble when the agent shares guide URLs in branded links across email or chat

Complementary

Dub API

Track clicks and conversions on shared guide links

Pair with Dubble when the agent measures engagement on guide URLs by wrapping them in trackable Dub links

FAQs

Specific to using Dubble API API through Jentic.

Why is there no official OpenAPI spec for Dubble API?

Dubble does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dubble API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Dubble API use?

Dubble uses an OAuth-style bearer token in the Authorization header. Through Jentic the token is stored in the encrypted vault and injected at execution, so it never enters the agent's prompt context.

Can I export a Dubble guide as Markdown?

Yes. GET /guides/{guideId}/markdown returns the guide rendered as Markdown, suitable for committing into a static docs site. GET /guides/{guideId}/html returns the same content as HTML.

What are the rate limits for the Dubble API?

The OpenAPI spec does not declare rate limits. Confirm your plan's quota with Dubble support and have your agent handle 429 responses with exponential backoff.

How do I subscribe to guide updates through Jentic?

Search Jentic for 'create a Dubble webhook', load the schema for POST /webhooks, and execute with the target_url and event filter. Install with pip install jentic.

Can I scope a webhook to a single collection?

Yes. POST /webhooks/{collectionId} creates a webhook that fires only for events on guides in that collection, which is useful for routing onboarding events separately from internal SOPs.