At-Bay

Record your At-Bay connection as cyber insurance evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In At-Bay:

   1. You need two API tokens from At-Bay: one for the demo environment and one for the production environment.
   2. Send each request with the header Authorization: Bearer \{\{token\}\} (the token is about 150 to 200 characters). Paste the production token into Safeguard.

   Where to find the other values:

   • Base URL (optional): At-Bay's API Quickstart lists the base URLs: production https://api.at-bay.com/v2, testing https://api-demo.at-bay.com/v2.

   At-Bay's public documentation does not cover every step.

   The public docs do not say how a token is issued (no UI path). Ask your At-Bay contact for a production token.

   Source: developers.at-bay.com, at-bay.com, checked 2026-10-07.

2. On Compliance › Connectors, open At-Bay, 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 At-Bay yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Cyber Insurance 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