Where to make each key
The page in each tool where its key or token is made, what to give it, and what it looks like.
When you add one of these tools, Roster shows the same link and steps on the form, checks what you paste as you type, and then checks the key with the tool itself, showing whose account it is. Tools with a guide of their own (Stripe, GitHub, Zoho Books…) explain their key there. See Adding a tool for how it works.
| Tool | Where | What to do | Give it | Looks like |
|---|---|---|---|---|
| Adobe Commerce (Magento) | On your own address: {baseUrl}/../../admin/admin/integration/new/ | Name it Roster, give it the resources hires need under API, save, then Activate and copy the access token. | ||
| Adyen | ca-live.adyen.com | In your Customer Area: Developers → API credentials → Create new credential (web service), give it the roles below, then Generate API key. | Checkout webservice role, Management API — Account read | |
| Akaunting | On your own address: {baseUrl}/../ | Create a user just for Roster (Settings → Users → Add new) with the role hires need, then use its email and password. | ||
| BigCommerce | login.bigcommerce.com | In the control panel: Settings → Store-level API accounts → Create API account (V2/V3 API token), set the scopes below, save, and copy the access token. | Orders: read-only, Products: read-only, Customers: read-only, Information & settings: read-only | |
| Bird | app.bird.com | In Bird, open Settings → Security → Access keys → Add new key, copy it and enter it as AccessKey <your key>. | AccessKey … | |
| Bitbucket | id.atlassian.com | Click Create API token, name it Roster and copy it. Use it with your Atlassian account's email. | ||
| Buildkite | buildkite.com | Name it Roster, choose your organization and the scopes below, create it and copy the token. | read_pipelines, read_builds, read_build_logs, read_user | bkua_… |
| Chargebee | app.chargebee.com | Sign in to your site, then Settings → Configure Chargebee → API Keys → Add API key (the MCP key type), and copy it. | Read-only access | |
| Copper | app.copper.com | In Copper, open Settings → Integrations → API Keys → Generate API key, and copy it. | ||
| Crisp | app.crisp.chat | Open your workspace's settings → Advanced → MCP, create a token and copy it. | ||
| Deel | app.deel.com | Open Access tokens → Generate new token (organization token), choose the scopes below, and copy it. | organizations:read, people:read, contracts:read | |
| Discord | discord.com | Open your application (or make one) → Bot → Reset Token, copy it, and enter it as Bot <token>. Invite the bot to your server. | View Channels, Send Messages, Read Message History | Bot MTk4… |
| Docker Hub | app.docker.com | Name it Roster, choose Read-only (or Read & Write), click Generate and copy the token. | Read-only | dckr_pat_… |
| Dolibarr | On your own address: {baseUrl}/../../user/list.php | Open the user Roster acts as, click Modify, generate the API key field, save and copy it. | ||
| Dropbox Sign | app.hellosign.com | Under API key, click Generate key (or Reveal on an existing one) and copy it. Paste it as the username; the password is any single character. | ||
| ERPNext | On your own address: {baseUrl}/../app/user | Open the user Roster acts as → Settings → API Access → Generate Keys. Paste "token <api key>:<api secret>". | token <api key>:<api secret> | |
| Figma | www.figma.com | Open Security, click Generate new token under Personal access tokens, pick the scopes below and copy it. | File content: Read-only, Comments: Read and write | figd_… |
| Firefly III | On your own address: {baseUrl}/../../profile | Under OAuth → Personal access tokens, click Create new token, name it Roster and copy it. | ||
| Fly.io | fly.io | Create an org token named Roster (or run fly tokens create org) and copy all of it. | ||
| folk | app.folk.app | In folk, open Settings → API → Generate a new key, and copy it. | ||
| Forgejo | On your own address: {baseUrl}/../../user/settings/applications | Under Access tokens, name it Roster, pick the permissions below, then Generate token and copy it. | repository: Read and Write, issue: Read and Write, user: Read | |
| Gitea | On your own address: {baseUrl}/../../user/settings/applications | Under Manage access tokens, name it Roster, pick the permissions below, then Generate token and copy it. | repository: Read and Write, issue: Read and Write, user: Read | |
| Gumroad | app.gumroad.com | Under Applications, create an application named Roster, then click Generate access token and copy it. | ||
| HCP Terraform | app.terraform.io | Click Create an API token, name it Roster, choose how long it lasts, and copy it. | xxxxxxxxxxxxxx.atlasv1.… | |
| HiBob | app.hibob.com | In Bob: Settings → Integrations → Service users → New, add it to a permission group with the access below, and copy its ID and token. | People's data: view (the fields hires need), Time off: view | |
| Hugging Face | huggingface.co | Choose the Read role (Write if hires should push), name it Roster, create it and copy it. | Read | hf_… |
| incident.io | app.incident.io | Click Add new, name it Roster, tick what hires should do, create it and copy the key. | View data, like public incidents and organization settings | |
| Invoice Ninja | app.invoicing.co | Settings → Account management → Integrations → API tokens → Add token. Self-hosted: the same page on your own address. | ||
| Kubernetes | kubernetes.io | Run kubectl create serviceaccount roster, bind it to the view role, then kubectl create token roster --duration=8760h and copy the token. | ClusterRole view (read only) | |
| Lemon Squeezy | app.lemonsqueezy.com | Click the + next to API keys, name it Roster, and copy the key (it's shown once). | ||
| Lever | hire.lever.co | Under API credentials, click Generate new key, tick the endpoints below, and copy it. Paste it as the username; the password is any single character. | Opportunities: read, Postings: read, Users: read | |
| Mailgun | app.mailgun.com | Click Add new key, copy it (it's shown once), and sign in with username api and the key as the password. | ||
| Matomo | matomo.org | In your Matomo: Administration → Personal → Security → Auth tokens → Create new token, describe it as Roster and copy it. | ||
| Medusa | On your own address: {baseUrl}/../app/settings/secret-api-keys | Click Create, name it Roster, save, and copy the key. Paste it as the username; the password is any single character. | sk_… | |
| OpenProject | On your own address: {url}/../my/access_token | Under API, click Generate (or + API token), name it Roster and copy it. | ||
| Outline | On your own address: {url}/../settings/api | Click New API key, name it Roster and copy it. | ol_api_… | |
| Paddle | vendors.paddle.com | Click New API key, name it Roster, give it the permissions below, and copy it (it's shown once). | Customers: read, Subscriptions: read, Transactions: read | pdl_live_apikey_… or pdl_sdbx_apikey_… |
| Postmark | account.postmarkapp.com | Open the server hires should send from, then API Tokens, and copy its Server API token. | ||
| Recurly | app.recurly.com | Sign in, then Integrations → API credentials → Add private API key. Paste it as the username; the password is any single character. | ||
| Remote | employ.remote.com | In Remote: Company settings → Integrations & API → API tokens → Generate token, and copy it. | ||
| Render | dashboard.render.com | Under API Keys, click Create API Key, name it Roster and copy it. | rnd_… | |
| Rippling | app.rippling.com | In Rippling: Tools → Developer → API Tokens → Create API token, tick the scopes below, and copy it. | companies.read, workers.read, departments.read | |
| Saleor | On your own address: {baseUrl}/../dashboard/apps/ | Install a local app named Roster with the permissions hires need, then create a token for it and copy it. | MANAGE_ORDERS, MANAGE_PRODUCTS | |
| SendGrid | app.sendgrid.com | Click Create API Key, choose Restricted Access, give it the access below and copy the key (it's shown once). | Mail Send: Full Access, Stats: Read Access, Suppressions: Read Access | SG.… |
| Smartsheet | app.smartsheet.com | Open Account → Personal settings → API access → Generate new access token, name it Roster and copy it. | ||
| Snyk | app.snyk.io | Under API Token, click to show it and copy it. Paste it as "token <your token>". | token 1a2b3c… | |
| SonarQube Cloud | sonarcloud.io | Under Generate Tokens, name it Roster, click Generate and copy the token. | ||
| Taiga | docs.taiga.io | Taiga has no key page: get a token by signing in through POST /auth (or an application token) and paste the auth_token. | ||
| Twenty | app.twenty.com | Under API, click + Create key, give it a name and copy it (it's shown once). Self-hosted: the same page on your Twenty. | ||
| Umami | cloud.umami.is | Click Create key, copy it. Self-hosted: use the token /api/auth/login gives you instead. | ||
| Uptime Kuma | On your own address: {baseUrl}/manage-status-page | Create a status page with the monitors hires should see and publish it. No key is needed. | ||
| Vikunja | On your own address: {baseUrl}/../../user/settings/api-tokens | Click Create a token, name it Roster, tick the permissions hires need and copy it. | ||
| Vonage | dashboard.nexmo.com | Under API settings, copy the API key (the username) and the API secret (the password). | ||
| WordPress (self-hosted) | On your own address: {baseUrl}/../../../wp-admin/profile.php#application-passwords-section | Under Application Passwords, name it Roster and click Add New. Sign in with your username and that password. | abcd efgh ijkl mnop qrst uvwx | |
| Wrike | www.wrike.com | Create a new API app (or open one), then Obtain token under Permanent access token, and copy it. | ||
| Zammad | On your own address: {baseUrl}/../../#profile/token_access | Click Create, name it Roster, tick the permissions below, copy the token and enter it as Token token=<your token>. | ticket.agent | Token token=… |