Non-DottedSign members are allowed to sign tasks within DottedSign (referred to as Quick Sign) and related operations, such as reading tasks, adding signatures, and more. To accomplish these actions, users can authenticate using a JWT code (only for non-member users) when requesting the corresponding API, instead of an access token. The following APIs are allowed to be authenticated using a JWT code:

• Consent to quick sign
• Read a task
• Create and upload an image
• Create and upload a signature
• Change a signer of a task
• Sign a task

Ensure that non-member users have given their consent

Before initiating any operations using the JWT code, it is crucial to ensure that signers have read and agreed to the terms of service and privacy policy. Once confirmed, request the Consent to quick sign API to obtain a verify_token. Both the JWT code and the verify_token are required for subsequent operations. The request body (or query parameters) is as follows:

• Request Body

  JSON

  {
      "verify_info": {
          "verify_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c"
      }
  }
  

• Query Parameters

  ?task_id=37126&verify_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
  

Moreover, it is necessary to ensure that subsequent API requests adhere to the following conditions:

• The requesting IP address remains consistent.
• The signer refrained from accessing the task through any alternative methods, such as a web browser, following consent.