FOfourthline
Qualified Electronic Signature

Test signature flow

Changed on

Sandbox environment only: Use this endpoint to start the signature flow for a test signature with a target status, using any successfully completed verificationId. <br /><br /><img src="https://files.readme.io/310d4d3-Inline_Caution.svg" align="left" alt="Important" /> Important: <code>signatureId</code> and <code>workflowId</code> are string identifiers that can be used interchangeably.

post/v1/testendpoint/signatures/{signatureId}

Request

  • Base URL
    https://api.ext-sandbox.fourthline.com
  • URL
    https://api.ext-sandbox.fourthline.com/v1/testendpoint/signatures/{signatureId}
  • Auth
    OAuth 2
    Client credentials
    Token URL: https://example.com/token

Path parameters

signatureIdstring required

Our unique identifier for the signature. <br /><br />Format: uuid string <br /><br />Example: 790f325a-48c9-4b82-bb53-c0ea128236f0 <br /><img src="https://files.readme.io/8eb9022-Inline_Tip.svg" align="left"/>Tip: This is the same value as the workflowId returned in the Create workflow response.

Headers

Authorizationstring required

The access_token returned in your most recent Create access token response.

Request body

mobilePhoneNumberstring

The client’s mobile phone number, which you have ensured is valid. <br /><br />Format: +{prefixNumber} {phoneNumber} <br /><img src="https://files.readme.io/ad2486a-Inline_Note.svg" align="left"/> Notes: <br />• Always include a space between the prefix and phone number. <br />• The prefix can contain a maximum of 4 digits. <br /><br />Example: +31 612345678

Response

Request accepted for processing; response body is empty

Changes