canonical: https://jentic.com/apis/bugfender.com/bugfender

# Bugfender API

Jentic publishes the only available OpenAPI specification for Bugfender API, keeping it validated and agent-ready. Bugfender is a remote logging service for mobile and web applications that collects device logs, crash reports, and user feedback so engineering teams can debug issues from real user sessions. The API exposes read access to applications, devices, log streams, and issue records, plus the ability to mark issues as resolved or reopen them. Use it to pull device-level logs into your own observability stack, surface user feedback inside support tools, or programmatically triage crash issues across mobile fleets.

## For AI agents

Pull mobile and web app logs, crash issues, and user feedback from Bugfender, and update issue status across your registered applications.

## Scope

Does not handle log ingestion from SDKs, billing, or team member management - use for reading mobile app logs, issues, and feedback only.

## Capabilities

- List every application registered to the Bugfender account and read its metadata
- Retrieve the device roster for an application and inspect individual device profiles
- Pull raw log entries for a specific device to debug a real user session
- Browse and filter the issue list for an application to triage crashes
- Mark a Bugfender issue as resolved, in-progress, or reopened by updating its status
- Read user feedback submissions tied to an application for support workflows

## Use cases

### Crash Triage Automation

Automatically pull the open issue list for a mobile application, inspect issue details, and route them to the right engineer. Bugfender exposes per-application issue endpoints with status, occurrence counts, and links back to underlying device logs, making it straightforward to feed crashes into a triage bot. A nightly job can list issues, filter by severity, and update status to acknowledged once an engineer is assigned.

Example prompt: List all open issues for app_id 1234, fetch details for each, and update any older than 30 days to status resolved if no new occurrences.

### Support Ticket Enrichment

When a user files a support ticket, fetch their Bugfender device logs and feedback records to attach real diagnostic context to the case. The API returns logs scoped to a specific device, so an agent can grab the last session for the affected user and append a summary to the helpdesk ticket. This eliminates back-and-forth requesting reproduction steps.

Example prompt: Given device_id D-789 reported in Zendesk ticket 4521, retrieve the latest device logs from Bugfender and post a summarised log excerpt as an internal note.

### Release Health Dashboard

Build a release health view by polling applications and issue lists across your Bugfender account after each deploy. The API gives you device counts, issue counts, and feedback volume per application so you can compare crash rates between versions. Combine it with your CI metadata to flag regressions within the first hours of rollout.

Example prompt: For each application in the account, count open issues opened in the last 24 hours and post a summary to a Slack release channel.

### AI Agent Debug Assistant via Jentic

A coding agent built on Jentic can reach for Bugfender when a developer asks why a mobile build is crashing. The agent searches Jentic for log retrieval, loads the device logs operation schema, and executes against the developer's vault-stored Bugfender token. It returns a summarised log trace without exposing the raw API key or requiring the developer to copy logs from the dashboard.

Example prompt: Search Jentic for retrieve device logs, load the GET /apps/{app_id}/devices/{device_id}/logs schema, and fetch logs for the device referenced in the developer's prompt.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /apps | List applications registered to the account |
| GET | /apps/{app_id}/devices | List devices for an application |
| GET | /apps/{app_id}/devices/{device_id}/logs | Get logs for a specific device |
| GET | /apps/{app_id}/issues | List issues for an application |
| PUT | /apps/{app_id}/issues/{issue_id} | Update issue status |
| GET | /apps/{app_id}/feedback | List user feedback submissions |

## Key resources

- **Applications** — List and inspect Bugfender applications registered to the account
- **Devices** — Retrieve the device roster for an application and read individual device metadata
- **Logs** — Read raw log entries captured for a specific device session
- **Issues** — Browse the issue list, fetch issue details, and update issue status
- **Feedback** — Read user feedback messages submitted through Bugfender SDKs

## Why Jentic

- **Setup:** Wiring Bugfender by hand means learning its bearer token auth against dashboard.bugfender.com/api and threading the app id through every device, log, and issue call yourself. Through Jentic you install once, import Bugfender from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Bugfender puts the app id in the URL path (/apps/{app_id}/...), so a rule can pin your agent to one app: it can read that app's devices, logs, issues, and feedback and nothing else. You choose the operations it may call, so it can read logs without being able to update an issue unless you add that.
- **Credential handling:** Your Bugfender bearer token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get crash logs' or 'list mobile issues', and Jentic returns the matching Bugfender operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Bugsnag API** — Bugsnag focuses on stability monitoring and error grouping with deeper release tracking than Bugfender.
- **BugHerd API** — BugHerd captures user-reported visual bugs on web pages while Bugfender captures runtime logs on mobile clients.
- **Buildkite API** — Buildkite handles CI/CD pipelines that ship the mobile builds Bugfender then monitors in the wild.

## FAQ

### Why is there no official OpenAPI spec for Bugfender API?

Bugfender does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Bugfender API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Bugfender API use?

Bugfender uses HTTP bearer authentication. Each request must include an Authorization header with a token generated from your Bugfender dashboard settings. When called through Jentic, the token is stored in your Jentic One instance and never enters the agent's context - Jentic injects it at execution time.

### Can I retrieve raw device logs through the Bugfender API?

Yes. The GET /apps/{app_id}/devices/{device_id}/logs endpoint returns log entries for a specific device under a given application. Use the application listing and device listing endpoints first to discover the IDs, then call the logs endpoint to pull the captured session output.

### Can I mark a Bugfender issue as resolved through the API?

Yes. The PUT /apps/{app_id}/issues/{issue_id} endpoint accepts an updated status payload, so an agent can resolve, reopen, or change the state of an issue after a fix is deployed. Pair it with GET /apps/{app_id}/issues to discover open issues first.

### What are the rate limits for the Bugfender API?

Bugfender does not document explicit rate limits in the OpenAPI spec. Their dashboard tier governs request throughput in practice, so production agents should add retry-with-backoff handling for HTTP 429 responses and avoid tight polling loops on the device logs endpoint.

### How do I pull Bugfender logs from an AI agent through Jentic?

Run pip install jentic and authenticate with your ak_* key. Use a search query like fetch device logs from bugfender, then load the GET /apps/{app_id}/devices/{device_id}/logs operation and execute it with the relevant app_id and device_id. Jentic handles the bearer token injection and returns the structured response.

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

Yes. Because you run Jentic One yourself, your own rules decide which Bugfender operations and which stored token your agent may use. Since Bugfender carries the app id in the URL path (/apps/{app_id}/...), you can pin the agent to a single application so it only reads that app's devices, logs, issues, and feedback and nothing else. You also choose the operations it can call, so it can read logs with GET /apps/{app_id}/devices/{device_id}/logs without being able to change an issue via PUT /apps/{app_id}/issues/{issue_id} unless you grant that.