Skip to main content

​
After this article

You’ll be able to connect Pingdom to Lumos and sync users and groups for visibility and Access Reviews.

​
Capabilities

This is a sync-only integration. Lumos reads users and groups from Pingdom and doesn’t provision or change anything in Pingdom.

​
Required plan and roles

  • Pingdom role: to generate the API token, you must be logged in to Pingdom with Owner as your Organization Role.
  • Token access level: the API token you provide must have the Read Access level.
  • No minimum Lumos plan is documented for this integration.

​
Read-only access vs provisioning

Is read-only possible? Yes, and it’s the only mode. Pingdom is a sync-only integration. The API token you generate is scoped to the Read Access level, and Lumos only reads users and groups. It never provisions or changes anything in Pingdom. What read-only requires. An API token generated by an account with Owner as the Organization Role, with its Access Level set to Read Access. Follow the steps below to generate and enter it. Watch out for. Only an Owner can generate the token, even though the token itself only grants read access. If the token is revoked or deleted, sync stops until you generate a new one. There’s no write-capable token to switch to, since provisioning isn’t supported for this integration.

​
Instructions

Phase 1: Create a Pingdom API token
  1. Log in to your Pingdom account with Owner as the Organization Role.
  2. In the left menu, go to Settings > Pingdom API.
  3. Click Add API token.
  4. Enter a name and set the Access Level to Read Access.
  5. Copy the token so you can paste it into Lumos.
Phase 2: Connect in Lumos
  1. Click the Pingdom card in your Lumos integrations. Reconnect an existing card or add a new one.
  2. Provide the API Token and Tenant Identification.
  3. Click Connect.

​
API Endpoints Used

​
Troubleshooting

Users aren’t syncing. Verify the API token can read user data and hasn’t been revoked or deleted in Pingdom. Make sure users have email addresses in their Pingdom profiles and that they’re active rather than pending invitations. Review the Lumos integration logs for specific error messages. “Invalid API token” or “Authentication failed”. Verify you copied the complete token without extra spaces and that it hasn’t been deleted or revoked. Confirm the token is tied to an active admin account and has the required read permissions. If the token still fails, generate a new one and confirm the Pingdom account isn’t suspended. Teams or contact groups are missing in Lumos. Verify the token can read team data and that teams exist in your Pingdom account with at least one member or contact. Review the Lumos integration logs for team sync errors. Sync fails with “Rate limit exceeded” or “Too many requests”. Pingdom enforces API rate limits that vary by plan. Wait for the rate-limit window to reset. Check whether multiple integrations share the same API token, and review the API usage limits for your plan. Contact Pingdom support if you consistently hit the limits.