Dokobit Documents Gateway PHP Example

• Check more documentation at https://gateway-sandbox.dokobit.com/api/doc
• Request access token here.
• Check Mobile ID and Smart-ID test data here.

Example configuration

• Copy config.php.dist to config.php.
• Set $accessToken variable in config.php.

Flow

Upload file

• Upload file you want to sign* and get uploaded file token.
• Check file upload status. If status uploaded**, continue.

* You should provide file['url'] which would be accessible for Documents Gateway or Base64 encoded file['content'] could be used instead.
** File status must be checked before creating signing.

upload-file.php - PHP code example for uploading file. Could be run from web or CLI.

Create signing

• Use file token provided with file upload response.
• Add as many signers as you need.

create-signing.php - PHP code example for creating signing. Could be run from web or CLI. Before running: edit file, and change $file['token'] value, with token you get after running upload-file.php.

Sign

Signing URL formation: https://gateway-sandbox.dokobit.com/signing/SIGNING_TOKEN?access_token=SIGNER_ACCESS_TOKEN. URL is unique for each signer.
SIGNING_TOKEN: token received with signing/create API call response.
SIGNER_ACCESS_TOKEN: token received with signing/create API call response as parameter signers.
Signers represented as associative array where key is signer's unique identifier - personal code.

Navigate to signing URL, sign document.

Retrieving signed document

After successful signing, you have two ways to get the signed file.

Via postback url

Postback calls are trigered, if postback_url was set while creating signing.

There are four types of postback calls:

1. signer_signed - after signer has signed document.
2. signing_completed - after signing has been completed (all signers successfully signed).
3. signing_archived - after document was archived (for signings with PADES-LTV and XADES-XL levels only).
4. signing_archive_failed - after document couldn't be archived (for signings with PADES-LTV and XADES-XL levels only).

postback-handler.php - PHP code example for handling postback calls. File should be placed in public web directory, accessible for Documents Gateway.

To retrieve signed document using these examples, your will need:

• Put postback-handler.php in public web directory, accessible for Documents Gateway.
• Set $postbackUrl parameter in config.php with URL where the postback-handler.php will be available. For eg. http://your-public-host/postback-handler.php.
• Create signing.
• Sign.
• Information about signed document will be sent to postback URL. postback-handler.php will handle postback and signed file will be stored in directory where postback-handler.php is located.
• Log file postback.log containing postback information, will be placed in the same directory as postback handler.

Via JavaScript callback

If you want to have JavaScript events, add its support by following the instructions here.

After receiving "onSignSuccess" callback, you can request signing status from your backend by making GET request to /api/signing/SIGNING_TOKEN/status.json and fetch signed document by using "file" parameter in the response.