Zube

About Zube

Zube's API provides programmatic access to a project and issue tracking system built around GitHub integration. Authentication uses a private key (RS256-signed JWT) exchanged for a short-lived access token: a client generates a refresh JWT signed with their private key, exchanges it at the tokens endpoint for an access JWT valid for 24 hours, and includes that token with a client ID in headers on subsequent requests.

The API organizes data into projects, which contain sources (linked GitHub repositories) and workspaces. Endpoints that return lists support pagination (page, per_page), ordering (order[by], order[direction]), filtering (where), and field selection (select), and most list responses include ETag headers for conditional requests to avoid re-fetching unchanged data.

This is aimed at developers integrating Zube's issue/project tracking into other tools or workflows, such as pulling card and project data, filtering or sorting results programmatically, or building custom clients against Zube's data.

Key features

• RSA key pair authentication with RS256-signed JWTs for API access
• Access tokens valid for 24 hours, refreshed via short-lived signed refresh JWTs
• Paginated list endpoints with configurable page and per_page parameters
• Sortable list endpoints via order[by] and order[direction] parameters
• Filterable list endpoints using where[] query parameters
• Selectable response fields via the select[] parameter and ETag-based conditional requests

Frequently asked questions