PowerDMS

Record your PowerDMS connection as compliance as code evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In PowerDMS:

   1. PowerDMS documents no self-service token page: PowerDMS assigns developer credentials (for example client IDs) for its APIs. Contact PowerDMS to obtain them; using the APIs means agreeing to the PowerDMS API Terms and Conditions.
   2. Have a PowerDMS user grant your application access on the OAuth consent screen, then paste the resulting token into API token / Personal access token.

   Where to find the other values:

   • Base URL (optional): The API host given in the PowerDMS API documentation (apidocs.powerdms.com, referenced by the API terms).

   PowerDMS issues this credential through its API or its support team, not through its admin screens.

   Only the PowerDMS API Terms and Conditions could be read; apidocs.powerdms.com did not resolve on 2026-10-07. The request process, callback URLs and scope names are not confirmed. OAuth tokens expire, so the pasted token will need refreshing.

   Source: apidocs.powerdms.com, powerdms.com, checked 2026-10-07.

2. On Compliance › Connectors, open PowerDMS, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads PowerDMS yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Compliance As Code connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks