Submit a DSR

Type of data subject request, can be any one of these events (https://docs.transcend.io/docs/receiving-webhooks#events).

Key-value pairs used to label data subject requests. These are Custom Fields in Transcend, and formerly known as Attributes.

The class of data subject, e.g. "customer", "subscriber".

Optional workflow configuration to submit this request against. Available for organizations on workflows v2. When set, the request is routed through that non-draft workflow. When omitted, Transcend may resolve a workflow via allowLegacyApiSubmission lookup on (type, subjectType), or fall back to legacy submission. type and subjectType remain required.

Specify the region that the request is submitting from. See https://github.com/transcend-io/privacy-types/blob/main/src/isoConstants/iso3166-1.ts

When true, no emails will be sent to the data subject (including confirmation emails).

When true, the request will be flagged as a test request. (useful for auditing purposes). Test requests still operate on your live integrations.

Language preference, defaults to English ('en').

Miscellaneous details about the request.

The date at which you received the request and the SLA for completion should begin.

The set of data system IDs that SHOULD be processed. When dataSiloIds is set, ONLY these data systems will be processed. dataSiloIds and ignoreDataSiloIds cannot both be set. When neither are set, the full set of data systems will be processed. When dataSiloIds is set, org-wide duplicate blocking is skipped.

The set of email addresses that should be included on CC for any outbound emails send to the data subject during the course of the request.

The set of data system IDs that SHOULD NOT be processed. dataSiloIds and ignoreDataSiloIds cannot both be set. When neither are set, the full set of data systems will be processed. When ignoreDataSiloIds is set, the full set of data systems except these data systems will be processed.

Specific email template to be sent to the end user upon request submission. When not provided, default template for workflow will be user.

When true, skip any waiting period associated with the workflow.

When true, do not send an email receipt. This is not needed if isSilent=true, but can be useful when isSilent=false but no email receipt is desired.

Specify the IDs of the enrichers/preflights that should be skipped when running this request. When omitted, all enrichers/preflight checks defined for the workflow will be run.

When restarting an existing request, specify the ID of the request to restart

When uploaded a backlog of past DSRs, use this field to upload a request directly into a completed state.

The partition key to associate with this request. Partitions separate requests by different data controllers or clients. You can find partition keys under Consent Management > Developer Settings.