ZEzeropath
Security Compass

Map an SD Elements project to a repository

Link one SD Elements project to one ZeroPath repository and automatically enqueue the first rule sync. If the integration is enabled and the repository already has a finished full scan, a findings push of that scan is enqueued too (it runs once the rule sync succeeds), so the mapping does not wait for the next scan. Multiple repositories can map to the same project and vice versa; adding a duplicate (project, repository) pair fails with 409. Requires the integration to exist (404 otherwise). Optionally set a per-project task status mapping; omitted means inherit the integration's default.

post/api/v2/securityCompass/addProjectMapping

Request

  • Base URL
    https://zeropath.com
  • Auth
    API key in header X-ZeroPath-API-Token-Id and API key in header X-ZeroPath-API-Token-Secret

Request body

organizationIdstring required

Organization that owns the integration.

sdeProjectIdstring required

SD Elements project id to link.

repositoryIdstring required

cuid of the ZeroPath repository to link. Obtainable via repositories.list.

Response

The created mapping with its (running) rule-sync state

idstring required
sdeProjectIdstring required
repositoryIdstring required
supportedTaskIdsstring[] required
lastPushAtstring date-time nullable
lastPushStatusstring nullable
createdAtstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.