Safeguard Docs
Compliance ConnectorsSetup by categoryCompliance As Code

Archer

Connect Archer to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

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

CategoryCompliance As Code
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In Archer:

    1. Archer's RESTful API has no token page: a session token is issued by an API call. Use an Archer user account (ideally a dedicated one with read-only access) for this.
    2. Send POST https://<your Archer host>/platformapi/core/security/login with a JSON body containing InstanceName, Username, UserDomain and Password.
    3. Copy the SessionToken value from the response and paste it into API token / Personal access token. Archer expects it in the header Authorization: Archer session-id="<token>".
    4. If Single Sign-on is enabled, an Archer administrator must first select Allow manual bypass in the Archer Control Panel for the RESTful API to issue a session token.

    Where to find the other values:

    • Base URL (optional): The address of your Archer instance (the host in front of /platformapi/...).
    • Account / Org / Workspace (optional): The Archer instance name, the same value sent as InstanceName in the login call.

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

    Session tokens are tied to a login session; Archer's docs do not state the session lifetime, so the token may expire. Archer documents no read-only API role; access follows the Archer user's access roles. The Web Services API can also issue a session token usable with the RESTful API even without manual bypass.

    Source: help.archerirm.cloud, checked 2026-10-07.

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

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

  3. Click Connect with token.

Frameworks

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

Apptega

Connect Apptega to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

AuditBoard

Connect AuditBoard to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

On this page

Connect with an API tokenFrameworksRelated