canonical: https://jentic.com/apis/supabugs.io/supabugs

# Supabugs Public API

Supabugs public API for managing issues, comments, attachments, and projects in bug tracking workflows. The API exposes 13 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create issue, issues index for zapier. Covers 13 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Create Issue
- Issues Index for Zapier
- Search Issues
- Get Issue
- Update Issue
- Delete Issue
- Add Comment to Issue

## Use cases

### Analytics Operations

Use the Supabugs Public API to perform analytics operations programmatically. The API provides 13 endpoints covering core functionality including create issue, issues index for zapier, search issues.

Example prompt: Call POST /issues to create issue

### Automated Attachments Management

Automate attachments operations by combining multiple Supabugs Public API endpoints. Agents can issues index for zapier and then search issues in a single workflow.

Example prompt: Call GET /issues to issues index for zapier, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Supabugs Public API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create issue', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/issues` | Create Issue |
| GET | `/issues` | Issues Index for Zapier |
| POST | `/issues/search` | Search Issues |
| GET | `/issues/{id}` | Get Issue |
| PUT | `/issues/{id}` | Update Issue |
| DELETE | `/issues/{id}` | Delete Issue |
| POST | `/issues/{id}/comments` | Add Comment to Issue |
| DELETE | `/issues/{issueId}/comments/{id}` | Delete Comment |

## Key resources

- **Attachments** — Operations related to Attachments
- **Comments** — Operations related to Comments
- **Issues** — Operations related to Issues
- **Lov** — Operations related to Lov
- **Projects** — Operations related to Projects

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/supabugs.io/supabugs/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Supabugs Public API by hand means passing its API key as an Authorization header bearer token and handling retries yourself. Through Jentic you install once, import the Supabugs Public API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Supabugs Public API puts the issue id in the URL path (`/issues/{id}`), so a rule can pin your agent to one issue: it can read the issue and its comments and nothing else. You choose the operations it may call, so destructive ones like deleting an issue or a comment are not included unless you add them.
- **Credential handling:** Your Supabugs Public API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'create an issue' or 'search issues', and Jentic returns the matching Supabugs Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Supabugs Public API use?

The Supabugs Public API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create issue with the Supabugs Public API?

Yes. Use the POST /issues endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Supabugs Public API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create issue through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create issue'. Jentic returns the matching Supabugs Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Supabugs Public API have?

The Supabugs Public API exposes 13 endpoints covering attachments, comments, issues operations.

### Can I limit what my agent is allowed to do with the Supabugs Public API?

Yes. Because you run Jentic One yourself, your own rules decide which Supabugs Public API operations and credentials the agent may use. Since the issue id sits in the URL path (`/issues/{id}`), you can pin the agent to a single issue so it only reads that issue and its comments, and you pick exactly which operations it may call. Destructive calls like deleting an issue (DELETE `/issues/{id}`) or removing a comment stay off unless you add them.