Skip to main content
Connect Checkly with a user API key to sync account members, checks and check groups, and run access reviews. Read-only.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists the members of one Checkly account — the first account the key can see, unless you pin one — with their name, email, Checkly role, the date they were added and Checkly’s own active or inactive state. Checkly’s support-staff memberships are left out, and so is anyone whose membership record is not of type member. Checkly does report per-member MFA, so the MFA column shows Yes or No, and Unknown for a member whose MFA state Checkly omits.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Checkly account member roster — names, emails, roles, status, MFA state and join dates — which appears on your Access page; and your Checkly checks and check groups, which appear on your Inventory page with their type, run frequency, locations and whether they are active or muted. Check results and alerts are not read.It calls these Checkly endpoints:
  • /v1/accounts
  • /v1/accounts/me/members
  • /v1/checks
  • /v1/check-groups
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Checkly environment.

​
Troubleshooting

A user API key can see every account its owner belongs to, and DSALTA syncs the first one unless an Account ID was entered at connect time. To pin a different account, disconnect, then connect again with the Account ID filled in. Note that disconnecting permanently deletes the data already collected from Checkly.
The key is invalid or was deleted, or an Account ID was entered that the key cannot see. A user API key inherits its owner’s role, so a key from a Read Only user still works for DSALTA, which only reads.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.