Z.ai (Zhipu GLM)

Connect Z.ai (Zhipu GLM) to record its access review and data terms as attested evidence. Z.ai (Zhipu GLM) offers no admin API for automated tests.

Connect with an API token

1. In Z.ai (Zhipu GLM):

   1. Sign in to the Z.AI Open Platform and open the API Keys management page (z.ai/manage-apikey/apikey-list).
   2. Create an API key and copy it.

   Where to find the other values:

   • Base URL (optional): Z.ai's quick start gives the API base URL https://api.z.ai/api/paas/v4/.

   Z.ai (Zhipu GLM)'s public documentation does not cover every step.

   The quick start names the API Keys page but not the exact create-button label, and does not say whether the key is shown once. No read-only or scoped key is documented.

   Source: docs.z.ai, checked 2026-10-07.

2. On Compliance › Connectors, open Z.ai (Zhipu GLM), 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

Z.ai (Zhipu GLM) publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

These tests are switched on per workspace by the Safeguard team.

Related

• Business Applications 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