Regenerate consent link

POST /api/v1/external/public/consent-link/duplicate/{request_id}

Use this endpoint to issue a new magic link when the original link has expired and the data principal has not yet completed consent. Regenerating a link preserves the original request_id, so any downstream tracking or status checks continue to work without changes. The expired link is marked as regenerated and is no longer accessible to the data principal.

Authentication

Both headers are required.

Header	Type	Required	Description
X-Org-Id	string	Yes	Your organization slug
X-API-Key	string	Yes	Your tenant API key

Path parameters

Parameter	Type	Required	Description
request_id	string	Yes	The request_id returned when the original link was created

Body

Field	Type	Default	Description
expiryHours	integer	24	How many hours the new link remains valid. Between 1 and 24.
send_sms	boolean	true	Whether to send the new link via SMS to the original phone number.

Response

201 Created

Field	Type	Description
sourceRequestId	string	The original requestId that was duplicated
requestId	string	The new requestId for this duplicate link
eventId	string	A new unique identifier for this link instance
consentLink	string	The new magic link URL to share with the data principal
expiresAt	string	ISO 8601 timestamp of when the new link expires

Caution

Duplication is limited to 5 times per request. Once the limit is reached, no further links can be issued for that requestId and a 429 error is returned. If the data principal still needs to complete consent, create a new request using POST /api/v1/external/public/consent-link.

Errors

Status	Description
400	X-Org-Id could not be resolved
401	X-API-Key is invalid or missing
403	API key lacks the admin scope
404	No consent request found for the given request_id
409	Link is still active — duplication is only allowed after the link expires
410	The data principal has already completed consent for this request
422	Request body failed validation
429	Maximum duplication limit of 5 reached
500	Internal server error

Example

curl --request POST \
  --url 'https://truapi-dev.truconsent.io/api/v1/external/public/consent-link/duplicate/a1b2c3d4-e5f6-7890-abcd-ef1234567890' \
  --header 'X-Org-Id: acme' \
  --header 'X-API-Key: tck_live_xxxxxxxxxxxx' \
  --header 'Content-Type: application/json' \
  --data '{
    "expiryHours": 24
  }'

{
  "sourceRequestId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "requestId": "b3c4d5e6-f7a8-9012-bcde-f12345678901",
  "eventId": "11223344-5566-7788-99aa-bbccddeeff00",
  "consentLink": "https://collect.truConsent.io/acme/cp_onboarding_v2/11223344-5566-7788-99aa-bbccddeeff00",
  "expiresAt": "2026-04-22T10:00:00+00:00"
}