Precoro
Connect Precoro to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Precoro connection as vendor procurement evidence. Automated collection is not available for this provider yet.
| Category | Vendor Procurement |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Precoro:
- Sign in to Precoro as the user the key should belong to. API data is limited by that user's role and its Locations, Departments and Projects permissions, so Precoro recommends a user with the broadest access.
- If your account has several companies, switch to the company you want to connect first (the list of available companies is in Account Settings); each company needs its own key.
- Open the API Access Keys page (https://app.precoro.com/manage/user/apitokens, or https://app.precoro.us/manage/user/apitokens for precoro.us accounts).
- Click Generate API Key.
- Copy the key immediately and store it safely. It is shown only once, at the moment of generation.
Where to find the other values:
- Base URL (optional): Precoro's API documentation uses https://api.precoro.com as the API base.
- Account / Org / Workspace (optional): Precoro API requests identify the user by the email of the account that generated the key (sent alongside the X-AUTH-TOKEN header); the company is the one active when the key was generated. Your companies are listed in Account Settings.
Precoro shows the secret only once, so copy it before you leave the page.
Precoro API keys are user-specific and company-specific, with no separate read-only scope: access follows the generating user's role and Location/Department/Project permissions. Requests send the key in the X-AUTH-TOKEN header together with an email header. To turn a key off, press the red cancel button next to it on the API Access Keys page. Precoro limits API use to 60 requests per minute, 1,500 per hour and 3,000 per day. The precoro.us API base host is not stated on the article; only the precoro.us key page link is.
Source: help.precoro.com, checked 2026-10-07.
-
On Compliance › Connectors, open Precoro, 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) — -
Click Connect with token.
Frameworks
Precoro 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vendor Procurement 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