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

Create a QR token

POST
{{base_url}}/v1/qr
Creates a signing request and returns the QR code.
Authorization: Bearer {access_token} of a Web SDK client.
sign_content is shown to the user in the RS-ID app and signed.
signers (PINFL / TIN) limits who can sign; COMPLETED when all have signed.
external_id must be unique per client.
After each signature RS-ID POSTs the PKCS#7 to callback_event.callback_url (see Callbacks). The callback is sent once, without retry — also poll the status.
Verify the PKCS#7 yourself: valid signature, signed content = your sign_content, expected signer.

Callbacks

signed

Request

Authorization
or
Body Params application/jsonRequired

Examples

Responses

🟢200
application/json
QR token created, or an error with a negative code.
Bodyapplication/json

🟠400
🟠401
🔴500
Request Request Example
Shell
JavaScript
Java
Swift
cURL
curl --location --globoff '{{base_url}}/v1/qr' \
--header 'Content-Type: application/json' \
--data '{
    "sign_content": "Contract No. A-7781 dated 09.11.2026. I agree to the terms of the service agreement.",
    "expire_time": 300,
    "sign_method": "RS_IMZO",
    "external_id": "CONTRACT-A-7781",
    "callback_event": {
        "callback_url": "https://shop.example.uz/webhooks/rsid/sign"
    },
    "qr_response_type": "ALL",
    "width": 256,
    "height": 256
}'
Response Response Example
200 - qr_response_type = ALL
{
    "data": {
        "qr_id": "9b2e6c1a-4f7d-4a3b-8e5c-1d2f3a4b5c6d",
        "qr_data": "https://auth.rsid.uz/9b2e6c1a-4f7d-4a3b-8e5c-1d2f3a4b5c6d",
        "qr_base64": "iVBORw0KGgoAAAANSUhEUgAAAQAAAAEAAQMAAABmvDolAAAABlBMVEX///8AAABVwtN+...",
        "expire_at": "2026-11-09 17:35:00",
        "qr_status": "ACTIVE"
    },
    "code": 0,
    "message": "Success"
}
Modified at 2026-11-10 09:18:58
Previous
refresh
Next
Get QR token status by qr_id
Built with