BugShot API

Name: BugShot API API
Brand: BugShot API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject ManagementapiKey24 EndpointsREST

For Agents

Create and update BugShot bugs, fetch project and user data, and subscribe to bug-event webhook triggers across 24 action and trigger endpoints.

Quickstart

Get started with BugShot 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:
"create a bug in BugShot"

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

Capabilities

What an agent can do with BugShot API API.

Create new bugs in a BugShot project with title, description, and assignee

Filter and search bugs by status, free-text query, or status name

Read comment threads on a bug and update individual comments

Update bug fields including info, status, and screenshot attachment

List project members and invite new users by email

GET STARTED

Start building with BugShot API API

Explore with Jentic

View OpenAPI Document

Use for: I need to file a new bug in BugShot from a chat command, Search for BugShot bugs that contain a particular keyword, List all BugShot bugs currently in the In Review status, Update the screenshot attached to an existing BugShot bug

Not supported: Does not handle billing, the BugShot dashboard UI, or browser-side screenshot capture — use for programmatic bug, comment, project, and webhook management only.

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

Jentic publishes the only available OpenAPI specification for BugShot API, keeping it validated and agent-ready. BugShot is a bug tracking platform exposed through a Zapier-style action and trigger surface — every operation is a POST endpoint that takes a structured JSON action payload. The API covers creating and updating bugs, listing bugs by status, managing comments and screenshots, inviting users, and subscribing to webhook triggers for project and bug events. Use it to embed BugShot inside automation flows, sync bug data into other tools, or push BugShot events into chat and ticketing systems.

Use Cases

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

★ Chat-Driven Bug Filing

Let teammates file BugShot bugs from Slack or Teams without leaving the conversation. The agent posts to /api/zapier/action/create-bug with a title and description gathered from the chat thread, then echoes back the created bug ID and direct link. Pair it with /api/zapier/action/update-bug-sc to attach the screenshot a tester just shared.

Create a BugShot bug titled Login button broken on iOS with the user's description, then attach the uploaded screenshot to the new bug.

Bug Status Sync Across Tools

Mirror BugShot status changes into a master ticketing system. Subscribe a webhook to /api/zapier/trigger/bug-updated-status, then on each event use /api/zapier/action/get-status-of-bug to confirm the new state and update the corresponding ticket in your engineering tracker. This keeps QA and engineering boards aligned without manual triage.

Register a webhook for the bug-updated-status trigger and, on each event, update the linked Jira issue to match the new BugShot status.

Tester Onboarding Automation

When a new tester joins a project, automate their access. The agent calls /api/zapier/action/get-users to confirm they are not already added, then /api/zapier/action/invite-users with their email. The full project payload from /api/zapier/action/get-whole-project lets you pre-build a welcome message that lists the open bugs they should review.

Invite tester@example.com to the BugShot project and post the open bug count from the project payload to a welcome Slack DM.

AI Agent Bug Assistant via Jentic

An agent built on Jentic can take a natural-language bug report from a non-technical stakeholder, classify it, and file it cleanly in BugShot. The agent searches Jentic for create a bug, loads the create-bug action schema, and executes the call with credentials drawn from the vault. It then polls the bug status to confirm engineering picked it up.

Search Jentic for create a BugShot bug, load the schema, and file a bug using the user's description; then call get-status-of-bug to monitor it.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/zapier/action/create-bug

Create a bug

POST

/api/zapier/action/search-bug

Search bugs by query

POST

/api/zapier/action/update-bug-status

Update bug status

POST

/api/zapier/action/update-bug-sc

Update bug screenshot

POST

/api/zapier/action/invite-users

Invite users to a project

POST

/api/zapier/subscription/{action}

Subscribe to a webhook trigger

POST

/api/zapier/trigger/bug-created

Fires when a bug is created

POST

/api/zapier/action/create-bug

Create a bug

POST

/api/zapier/action/search-bug

Search bugs by query

POST

/api/zapier/action/update-bug-status

Update bug status

POST

/api/zapier/action/update-bug-sc

Update bug screenshot

POST

/api/zapier/action/invite-users

Invite users to a project

Why though Jentic?

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

Credential isolation

Your BugShot x-api-key is stored encrypted in the Jentic vault. Agents never see the raw value — Jentic injects the header at execution time and returns only the response body.

Intent-based discovery

Agents search Jentic with phrases like file a new bug or subscribe to bug events, and Jentic returns the matching BugShot action or trigger operations with full input schemas.

Time to first call

Direct BugShot integration: a couple of hours to map the Zapier-style action endpoints. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BugHerd API

BugHerd is a visual feedback tracker focused on pinning bugs onto live web pages, while BugShot wraps a Zapier-style action surface.

Choose BugHerd when feedback comes from clients reviewing a website; choose BugShot when bug filing is automation-driven.

Alternative

Bugsnag API

Bugsnag automatically captures runtime errors from deployed apps; BugShot is for human-filed bug reports.

Pick Bugsnag for unattended crash collection and BugShot for human-curated bug filing flows.

Complementary

Buildkite API

Buildkite builds the artefacts whose bugs end up filed in BugShot.

Correlate a Buildkite build with a BugShot bug to identify which deploy introduced a regression.

FAQs

Specific to using BugShot API API through Jentic.

Why is there no official OpenAPI spec for BugShot API?

BugShot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BugShot 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 BugShot API use?

BugShot uses an API key passed in the x-api-key header on every request. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the agent never sees the raw key in its context.

Can I subscribe to bug events through the BugShot API?

Yes. POST /api/zapier/subscription/{action} subscribes a webhook URL to a trigger such as bug-created, bug-updated-status, bug-updated-comment, bug-updated-info, bug-updated-sc, or project-updated-info. DELETE on the same path removes the subscription.

How do I create a bug with a screenshot?

It takes two calls. First post to /api/zapier/action/create-bug with title and description to create the bug, then call /api/zapier/action/update-bug-sc with the bug identifier and the screenshot payload. Run both in a single agent flow for a one-shot bug filing.

What are the rate limits for the BugShot API?

The OpenAPI spec does not document explicit rate limits. Treat the Zapier action endpoints as fair-use and add retry-with-backoff for HTTP 429 responses; rely on triggers and webhooks for change detection rather than polling search-bug.

How do I file a BugShot bug from an AI agent through Jentic?

Run pip install jentic and authenticate with your ak_* key. Search Jentic with create a BugShot bug, load the POST /api/zapier/action/create-bug operation, and execute it with title and description. Jentic injects the x-api-key header from your stored credential.