TracePass
Regulatory assistant

Delete compliance profile

Removes the entire `complianceProfile` sub-document from the company record, including all stored facts (role, categories, markets, products, and all learned values). Returns `{ "deleted": true }` on success. After deletion, `GET /api/v1/company/compliance-profile` returns an empty profile (`{ "complianceProfile": {} }`). The DPP Assistant tools will then have no saved defaults and will ask for the relevant facts fresh on the next question.

DELETE/api/v1/company/compliance-profile
Download OpenAPI 3.1
DELETE/api/v1/company/compliance-profile

Delete compliance profile

Removes the entire `complianceProfile` sub-document from the company record, including all stored facts (role, categories, markets, products, and all learned values). Returns `{ "deleted": true }` on success. After deletion, `GET /api/v1/company/compliance-profile` returns an empty profile (`{ "complianceProfile": {} }`). The DPP Assistant tools will then have no saved defaults and will ask for the relevant facts fresh on the next question.

Auth: an API key or OAuth with `passports:write`. For OAuth principals, the user must have the `admin` or `owner` role. Counts no scope answer.

Headers

  • Authorizationrequired

    string

    `Bearer <token>` — either a `tp_` API key (Developer → API Keys; simplest, for server-to-server) or an OAuth 2.0 access token (Developer → OAuth Apps; for user-authorized apps, scoped + revocable). The Authentication page has the full OAuth flow and scope list.

    e.g. Bearer tp_REDACTED_xxxxxxxxxxxx

Request

curl -sS https://app.tracepass.eu/api/v1/company/compliance-profile \
  -X DELETE \
  -H "Authorization: Bearer tp_REDACTED_xxxxxxxxxxxx"

Response

{ "deleted": true }