Happy New Year! The API has been released in private beta

We're starting 2025 with the release of one of the most requested features: the API 🤓🎉
API in private beta
Our newly released API allows you to use Keypup programmatically. The API is composed of two endpoints:
- The Platform API: This endpoint is the general-purpose API used to manage dashboards, insights, projects, and users. It can be used to retrieve the list of team members, send team invites, edit dashboards, create insight configurations, etc.
- The Reporting API: This endpoint is the actual reporting engine used by insights to query the datasets. You can make listing or "group by" queries, such as counting the number of Pull Requests per month labeled as "bug", for the last 12 months.
The API can be used to incorporate engineering metrics into your existing workflows and systems, such as:
- Creating a Slack bot, to send a standup report every morning
- Configuring alerts, in your favorite monitoring system (Datadog, New Relic, and the like)
- Leveraging engineering metrics in your global DevOps flow, such as increasing the number of required reviewers when quality drops
The API is a self-documented GraphQL API, which you can easily try out using our API Explorer (see screenshot). The API powers our frontend, this means that you can simply look at the network requests while navigating the Keypup interface to get examples of GraphQL queries 💪
The API is currently in private beta. Access is provided on a per-user basis during the beta. Do not hesitate to contact our team via chat to get your access enabled.
If you want to learn more about our API, simply check out our dedicated article on the help center.
Other improvements and bug fixes
A few additional items worth mentioning 🥰
- Improvement: Dashboards added through the standalone "add Dashboard" flow are now automatically pinned
- Improvement: Array operators now consider null values as empty arrays to make the formulas on custom fields consistent across records from different applications
- Improvement: The number of displayed custom fields has been increased from 500 to 1000
- Improvement: The MIN and MAX operators now support string values on top of numbers
- Improvement: The platform's accessibility (WCAG 2.0) has been considerably improved. Work remains but this is a significant step forward.
- Improvement: Stick to integer ticks on the Y axis when values only contain integers. Decimal ticks may only appear if values contain decimals.
- Improvement: The TIMELINE_DURATION operator supports a boolean fourth argument to set the return value as "null if none". This is useful to ignore zeros in averages when issues have skipped the measured step in a flow.
- Bugfix: The selected drilldown data point is now reset when the insight configuration changes, in edition mode.
- Bugfix: Custom field cache (in custom formulas and filter box) is properly reset when apps are connected/disconnected
- Bugfix: Drilldown could not be activated on new "Report" insights (only after save + edit). This has been fixed.
- Performance: Jira issue descriptions are now limited to 10k characters. This limitation will be rolled out to all applications.
- Performance: The memory usage of the user interface has been reduced by around 60%, especially over long usages (memory leaks).