Skip to main content
This walkthrough uses a tb_test_ key, which reads your sandbox company of sample employees. Every request works unchanged with a tb_live_ key once you go live.
1

Get a test key

Keys are issued by TeamBuilder during onboarding. Email contact@teambuilder.ge from your company domain and ask for a test key; a live key follows when you are ready.The key is shown once. Put it in an environment variable rather than in code:
2

Verify the key

GET /v1/ping works with any key and tells you which company it reads, its scopes and its mode.
Response
A 401 means the key is missing, mistyped, revoked or expired. See Authentication.
3

Read the leaderboard

Fetch the top ten for the current month:
Each row has the employee’s company-wide rank, their xp for the period, their all-time level and their department.
4

Render it

Turn the rows into markup on your server, then cache the result: rankings can be up to 30 seconds old, so polling more often gains nothing.
name can be null for someone who has not signed in to TeamBuilder yet and was not added by a roster sync. Always render a fallback.
Call the API from your server only. Keys grant access to employee names and emails, so they must never reach a browser, a mobile app or a public repository. The API does not accept cross-origin browser requests, so browser calls fail by design.

Where next

Leaderboards guide

Periods, department views and refresh strategy.

Roster sync guide

Keep employees, departments and job titles in sync.