Skip to main content
Connect Buildkite to OPTIMAZE with an API token. Buildkite reports a monthly active user count but no dollar amount, so OPTIMAZE records the count daily with a cost of 0.
Buildkite is in beta. The tile on the Integrations page is marked Beta.

​
Prerequisites

  • A Buildkite user in the organisation you want to import.

​
Set up the Buildkite integration

1

Create an API token in Buildkite

  1. In Buildkite, open Personal Settings, then API Access Tokens.
  2. Create a token with the read_organizations scope for your organisation.
  3. Copy the organisation slug from the Buildkite URL.
2

Enter the details in OPTIMAZE

Under Data, select Integrations. On the Buildkite tile, select Connect, then fill in the form.
3

Connect

Select Connect.

​
What happens next

When you select Connect, OPTIMAZE runs a connection check before it starts importing. Each part of the check shows as passed, failed or not checked, and a later part is not checked when an earlier one fails. Once the check passes, the integration appears under Connected on the Integrations page. OPTIMAZE imports the previous six months of history on the first sync, and each later sync re-reads the last three days to pick up late changes. Buildkite exposes only the current monthly active user count, with no history. Unlike other integrations, history starts on the day you connect, and every record has a cost of 0.

​
Troubleshooting

  • Authentication fails: the token is wrong or revoked.
  • Access fails: the token is missing read_organizations, or Organisation slug is not an organisation the token can read.
  • No earlier months appear: buildkite has no usage history to import. Records start on the day you connected.
  • Data available fails: Buildkite has no cost data for the period yet. Wait for Buildkite to report usage, then connect again.