1. Auth and Qr identification
RSID docs
English
  • English
  • Russian
  • Uzbek
  • Integration Overview
  • Web SDK
    • Usage guide
    • sign-in
      POST
    • refresh
      POST
    • create-session
      POST
    • user-info
      GET
  • Mobile SDK
    • Usage guide
    • sign-in
      POST
    • refresh
      POST
    • create-session
      POST
    • user
      GET
  • Backend with information
    • Usage guide
    • sign-in
      POST
    • refresh
      POST
    • Option 1 — compare photo with passport photo
      POST
    • Option 2 — compare two photos with citizen data
      POST
    • Option 3 — compare two photos without citizen data
      POST
    • Get result
      GET
  • Backend without information
    • Usage guide
    • sign-in
    • refresh
    • Option 1 — compare photo with passport photo
    • Option 2 — compare two photos with citizen data
    • Option 3 — compare two photos without citizen data
  • Auth and Qr identification
    • Sign with RS-ID (Oauth2 style)
    • Qr Sign/Identification process
    • Get user info by code
      POST
    • sign-in
      POST
    • refresh
      POST
    • Create a QR token
      POST
    • Get QR token status by qr_id
      GET
    • Get QR token status by external_id
      GET
  • Schemas
    • ErrorResponse
    • AuthCodeRequest
    • ClientCredentials
    • Token
    • UserInfo
    • TokenResponseEnvelope
    • DocumentInfo
    • Signer
    • StringResponseEnvelope
    • ContactInfo
    • CallbackEvent
    • UserProfile
    • QrTokenCreateRequest
    • PhotoItem
    • Address
    • UserProfileResponseEnvelope
    • AdditionalParams
    • WebSessionCreateRequest
    • QrToken
    • UserProfileResponse
    • CompareFaceRequest
    • UserResponseEnvelope
    • CompareImagesWithInfoRequest
    • QrTokenResponseEnvelope
    • CompareImagesRequest
    • SignCallback
    • ComparisonResult
    • MobileSessionCreateRequest
    • ComparisonResultEnvelope
  1. Auth and Qr identification

Get user info by code

POST
{{base_url}}/v1/user/by-code
Exchanges the one-time authorization code (received on your redirect_uri after the user signs in on the RS-ID auth page) for the user's verified profile.
Call from your backend only — the request contains client_secret.
Authorization header: not required; the client is authenticated by client_id / client_secret in the body.
The client must be registered in RS-ID as an AUTH project.
The code is valid for 5 minutes and can be used once. If it fails, start the sign-in again.
Use user_info.pinfl as the stable user identifier. Addresses are not returned in this flow (null).

Request

Body Params application/jsonRequired

Examples

Responses

🟢200
application/json
Verified user profile.
Bodyapplication/json

🟠400
🔴500
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --globoff '{{base_url}}/v1/user/by-code' \
--header 'Content-Type: application/json' \
--data '{
    "client_id": "shop-example-auth",
    "client_secret": "s3cr3t-value",
    "code": "Zx81kQ2mP0aB7cD9eF1gH3",
    "grant_type": "authorization_code"
}'
Response Response Example
200 - Success
{
    "data": {
        "user_info": {
            "first_name": "ALISHER",
            "last_name": "KARIMOV",
            "middle_name": "BAXTIYOROVICH",
            "pinfl": "12345678901234",
            "gender": "MALE",
            "birth_date": "1990-01-01",
            "birth_place": "TOSHKENT",
            "birth_country": null,
            "nationality": null,
            "citizenship": null
        },
        "document_info": {
            "document": "AA1234567",
            "type": "PASSPORT",
            "issued_by": "IIV 26283",
            "issued_at": "2018-05-10",
            "expiry_at": "2028-05-09"
        },
        "contact_info": {
            "phone": "998901234567",
            "email": "alisher.karimov@example.uz"
        },
        "permanent_address": null,
        "temporary_address": null
    },
    "code": 0,
    "message": "Success"
}
Modified at 2026-11-09 12:08:31
Previous
Qr Sign/Identification process
Next
sign-in
Built with