Skip to main content
PATCH
Link User to Consent Set

Overview

Links a permanent userId to an existing consent set that was created during onboarding. This endpoint completes the consent onboarding process by associating consent records with a user account.
Call this endpoint after user account creation is complete (e.g., after email verification, KYC completion, or registration finalization).

When to Use

1

After User Account Creation

Once you have a permanent userId from your system
2

After Email Verification

When user verifies their email and account is activated
3

After KYC Completion

When identity verification finalizes
4

Registration Complete

When the full registration workflow finishes

Endpoint

Headers

Path Parameters

Request Body

Example Request

Response

200 OK

400 Bad Request

404 Not Found

409 Conflict

A consent set can only be linked to one user. Attempting to link again will result in a 409 Conflict error.

Code Examples

TypeScript

Python

cURL

Integration Workflow

Best Practices

Store the consentSetId in your session or database until user registration completes:
Check if linking has already occurred before attempting:
Remove temporary data after successful linking:

Important Notes

One-Time Operation: Each consent set can only be linked once. The linking action is recorded in the audit trail and cannot be undone.
Audit Trail: The linking action is automatically recorded in the user’s consent audit trail with timestamp and metadata.

Create Onboarding Consent

Create the initial consent set

Get User Consent Status

Check user’s consent status after linking

Get Consent Set by ID

Retrieve consent set details

Implementation Guide

Full integration guide