Better Stack

The platform reads members of a Better Stack team through UptimeAPIso that you can review who has access.

Attention

Create a Global API token in Better Stack > API tokens and enter into Team Name The endpoint of team members requires this name when a global token calls it. Team-based tokens tab holds per-team tokens instead: an Uptime API token, documented for uptime resources, and a Telemetry API tokenBetter Stack documents no prefix or format for any of them, so check which section a token came from instead of reading its value.

Prerequisites

• the platform organization administrator access
• The Admin Only administrators can edit tokens, and a team leader can only view them.
• The Team Name from the team that the platform should review, which the Connect dialog asks alongside the token. Settings > TeamsEnter the name exactly as Better Stack writes

Collected Fields

the platform field	Better Stack field	Notes
Name	first_name, last_name	The platform unites the two into a single name and throws a missing part. A waiting invitation does not carry either, so the name remains empty.
Email	email	the platform goes over a record that returns without an email address
Role	role	The platform displays admin, billing_admin, team_lead, responder and member as administrator, billing administrator, team leader, respondent and member. Any other value, including ___ZBT_I18N_RUNTIME_BLOCK_178__, appears as returned.
Admin	role	flagged as administrator when role is admin or team_lead. billing_admin is only billing and is not flagged nor is it a custom role
Status	type	The platform lists team_member as asset and team_member_invitation as inactive. Any other type leaves the state unknown
MFA	Not supported
Last login	Not supported
External ID	id	Stable ID used to track your account through reviews
Created at	created_at	When the member joins the team, the platform returns to invited_at when created_at is missing, as a waiting invitation

The platform lists the members who have been invited but have not yet accepted alongside the confirmed, labeled inactive members. The Better Stack returns role is the one that the member holds in the team you have appointed, not in any other team to which the same person belongs.

Step 1: Create a Global API Token

1. In Better StackSigned as Admin, go to API tokens and find Global API tokens A global token is valid for all teams, which is why team members take a team name.
2. Enter a Token name (e.g. Probo Access Review), leave the permission set to Read & write, and click Create.
3. Copy the token and store it securely. Existing tokens remain copyable from this screen so you can recover them later.

Step 2: Connect in the platform

1. On the platform, go to Access Reviews > Sources > Add Source.
2. Find Better Stack, click API KeyPut yourself in the box, enter Team Name, and click Connect.

the platform names the source after the team name you entered and attracts that team members to your campaigns.

Troubleshooting

• Token rejected. Confirm that the token comes from the Global API tokens section, which is the Better Stack document type alongside the team name parameter. Telemetry API token covers telemetry resources, including Errors, not UptimeAPI.
• No members appear. Check the Team Name against the Better Stack names Settings > Teams A global token selects the team by this name.
• Token creation is unavailable. Changing tokens is an administrator’s permission in Better Stack. A team leader can view the tokens but can’t create them, so ask an administrator.
• Roles do not match what the console displays. The end point reports the role the member holds in the listed team so that it can confirm Team Name Custom roles are an Enterprise feature and return as custom. the platform only marks admin and team_lead as administrators.