Authentication

Create Sandbox API Token

Authenticate with the same email/password as POST /auth/token, but obtain a sandbox token instead (prefixed sandbox_...). Requests made with this token never send real SMS or emails (SMS are logged, emails go through the log mailer) and never deduct signature credits. To complete a sandbox signature, the test signer opens the signing link and enters the fixed sandbox OTP code 123456 (displayed on the signing page); the signed PDF and its proof file can then be downloaded as in production. Documents and signature requests created in sandbox mode are isolated from your organization's real data: they never appear in a normal (non-sandbox) request, and vice versa. A sandbox token can only be used with the sandbox_ prefix, and a normal token can never be used with it — mixing the two returns 401. Rate limited to 10 attempts per minute for the targeted account, and 60 per minute for the calling IP.

post/auth/sandbox-token

Request

  • Base URL: https://www.jurisign.fr/api/v1
  • URL: https://www.jurisign.fr/api/v1/auth/sandbox-token
  • Auth: none required

Request body

emailstring email required

Your account email address

passwordstring password required

Your account password

device_namestring

Optional device identifier. Tokens with the same device name will be revoked and replaced.

Example request

{
  "email": "user@example.com",
  "password": "your-password",
  "device_name": "my-app-sandbox"
}

Response

Sandbox token created successfully

tokenstring
token_typestring
sandboxboolean

Example response

{
  "token": "sandbox_1|abc123...",
  "token_type": "Bearer",
  "sandbox": true,
  "user": {
    "name": "Jean Dupont",
    "role": "admin",
    "organization": {
      "name": "My Company"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.