Connect Sumsub to Rig

    Sync Sumsub KYC and KYB applicant status into Rig: review outcome, per-step completion and basic company and beneficiary details. Sumsub has no list-all API, so Rig reads an applicant when a Sumsub webhook fires for it.

    Before you start

    • You need a Sumsub role that can generate app tokens, which is the Manage application tokens permission.
    • Tokens are tied to a mode. A Sandbox token works in Sandbox and a Production token works in Production, so create the one that matches the data you want.
    • Each workspace can have one Sumsub connection.

    Step 1: Generate a Sumsub app token

    1. In the Sumsub Dashboard, go to Configurations then Developers then App tokens, and click Generate app token.
    2. Enter a name, such as Rig.
    3. Leave Whitelisted IPs on any address, which is the default. If you restrict it, contact us for the addresses Rig connects from.
    4. Set an expiry date only if you plan to rotate the token, then choose the permissions that let the token view applicants.
    5. Click Generate app token, then save the app token and the secret key.

    Settings cannot be changed later
    Sumsub shows the full token and secret key once, and you cannot edit a token after creation. If something is wrong, generate a new token.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Sumsub, open the card and click Connect.
    3. App token: paste the app token. It starts with prd: for Production or sbx: for Sandbox.
    4. Secret key: paste the secret key shown when you created the token.
    5. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Sumsub lands in its own sumsub schema in your warehouse:

    • Applicants: names, contact email, country, your external user ID, review status and result, and level.
    • Applicant steps: per-step completion for each applicant.
    • Beneficiaries: company registry basics and beneficiary name, role and email.

    Rig keeps this deliberately small. Document images, dates of birth, home addresses, document numbers and tax IDs stay in Sumsub.

    Good to know

    • Data arrives per applicant, when a Sumsub webhook for that applicant fires. A scheduled sync on its own finds nothing to read, which is expected.
    • To check that webhook delivery to Rig is set up for your workspace, contact us.
    • Sumsub requires requests to be signed within a minute of its own server time. Rig handles the signing for you.
    • To disconnect Sumsub, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Find where verification stalls
    • Compare verification outcomes by segment
    • Report on compliance without exporting personal data

    More ideas for using Sumsub

    Was this guide helpful?