# Mobile SDK

MSDK Screenshot

# SDK Resources

Documentation for iOS MobileSDK
- Demo Source Code
Documentation for Android MobileSDK
- Demo Source Code

When using our demo source code, make sure to keep both URLs in sync:

test-api.sumsub.com and test-msdk.sumsub.com for test environment
api.sumsub.com and msdk.sumsub.com for production environment

# Backend routines

Please contact the Sum&Substance tech team for MobileSDK credentials.

In order to embed our MobileSDK you have to perform a couple of preparation steps and use their results to pass into the MobileSDK initialization:

[Backend] Create an applicant and record its applicantId for the next steps.

# Creating an applicant

Copy
curl -X POST \
  'https://test-api.sumsub.com/resources/applicants' \
  -H 'Authorization: Bearer 5sV7LOpJReqUKaZNy1bC2NpZXhm+rmg4J+6Rq/cSavI8I2fdBTuOWw==' \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "requiredIdDocs": {
    "externalUserId": "UserIdInYourSystem"
    "docSets": [
      {
        "idDocSetType": "IDENTITY",
        "types": [
          "PASSPORT",
          "DRIVERS",
          "ID_CARD"
        ]
      },
      {
        "idDocSetType": "SELFIE",
        "types": [
          "SELFIE"
        ]
      }
    ]
  }
}'

# Applicant creation response

Copy
{
  // note this ID to pass on MobileSDK Initialization
  "id": "5a8154fd0a975a33d32cfa0c"
  // ....
}

Please note that the userId in the request to create an access token is a client-side ID.

[Backend] Generate an access token associated with applicantId (in order to limit the access token to exactly that applicant). You can customize required document set for your purposes. The minimum set is IDENTITY and SELFIE.
[Mobile] Initialize MobileSDK with
- applicantId
- accessToken Environment url: test-msdk.sumsub.com when integrating, and msdk.sumsub.com when going live