---
title: "Retrieve build information"
method: GET
path: "/info"
tags: ["info"]
---

# Retrieve build information

`GET /info`

## Response `200`

Successful response

- BuildInformationResponseMessage — The current version number and build time for the SheerID server application
  - `sheeridVersion` string — The version of SheerID deployed on the server
  - `sheeridGitCommit` string — The Git SHA1 hash for the last commit in this build
  - `puppetGitCommit` string — The Git SHA1 hash for the last commit in the puppet configuration realm at deployment time
  - `buildTimestamp` string — The timestamp of the build which produced the version of SheerID deployed on the server

## Other responses

- `429` — Too many requests. A `429` can mean one of two things — inspect the response body's `errorIds` before retrying: - A transient rate limit applied at the platform edge. If a `Retry-After` header is present, wait that many seconds (using exponential backoff) and retry. - A program/consumer limit such as `verificationLimitExceeded`, `reverificationDailyLimitExceeded`, or `docReviewLimitExceeded` — the consumer has exhausted an allowance defined by the program's limiting policy. This is a permanent rejection (`currentStep: error`, no `Retry-After`); do not retry.
- `500` — Internal server error.
- `503` — Service temporarily unavailable. The request can be safely retried after the interval given in the `Retry-After` header.

---

[API](https://skmtc.dev/sheerid/apis/sheerid-api.md) · [All operations](https://skmtc.dev/sheerid/apis/sheerid-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sheerid/sheerid-api/revisions/dc7f4e84f543/schema)