Cloudcheck Forms API1.0

Overview

Cloudcheck Forms allows end-to-end onboarding with customisable application forms integrated with Cloudcheck Go.

Create

Path /forms/create/ Method POST

Creates a new Forms request. You must include the following parameters as part of the call. Please note all these parameters must be posted as URL encoded form data. As such, the request should contain a Content-Type header of application/x-www-form-urlencoded.

Parameter Required Description
key true

Your API Key.

signature true

An HMAC SHA-256 signature of request data for call validation. See details on generating a request signature.

nonce true

A single-use key generated for this request. Note that each nonce may only be used once for each access key.

timestamp true

The system timestamp when the request was created in milliseconds since the Epoch (timezone independent). Note Unix time is in seconds and will need to be multiplied by 1000. Requests with old timestamps will be rejected.

data true

A JSON string containing the details of the Forms request.

Request

An example of the JSON in the data parameter is shown below.

Example

Data Element Notes

Element Notes
reference A reference that you provide to identify this Forms request. Optional but recommended.
emailAddress Address used to send the email asking for the initial form to be completed. Both emailAddress and givenName must be supplied if an email is to be sent, otherwise these fields will be ignored and a link will be generated instead.
givenName The given name of the person the initial email is sent to.
emailCcAddress Added as a cc address for the email asking for the initial form to be completed. Also receives an email when the last person verifies themselves.
notificationUrl A notification is sent to this URL when the form is submitted, as well as when the last person verifies themselves. Two parameters are added to this URL: reference - identifies the forms request, and status - indicates the status of the forms request, e.g. SUBMITTED or COMPLETED.

Response

An example of the JSON returned in the response is shown below:

Example

The formsReference is a unique identifier for this forms request and is used in the other Forms API calls.

The emailSent is a boolean parameter indicating whether an email was automatically sent or not. An email is only sent if both emailAddress and givenName was supplied in the request.

The link is the URL that was sent in the email. If an email wasn't automatically sent it is up to you to send this link to the person who will be responsible for filling out the initial form.

Resend

Path /forms/resend Method POST

Allows a Forms request to be resent. You must include the following parameters as part of the call. Please note all these parameters must be posted as URL encoded form data. As such, the request should contain a Content-Type header of application/x-www-form-urlencoded.

Parameter Required Description
key true

Your API Key.

signature true

An HMAC SHA-256 signature of request data for call validation. See details on generating a request signature.

nonce true

A single-use key generated for this request. Note that each nonce may only be used once for each access key.

timestamp true

The system timestamp when the request was created in milliseconds since the Epoch (timezone independent). Note Unix time is in seconds and will need to be multiplied by 1000. Requests with old timestamps will be rejected.

data true

A JSON string containing the details of the Forms request.

Request

An example of the JSON in the data parameter is shown below.

Example

The formsReference is mandatory and identifies the Forms request to resend.

The givenName and emailAddress of the user receiving the email request are optional but can be supplied if changes are required. 

Response

An example of the JSON returned in the response is shown below:

Example

Result

Path /forms/result/ Method GET

Fetches the current result of the forms request.

Parameter Required Description
key true

Your API Key.

signature true

An HMAC SHA-256 signature of request data for call validation. See details on generating a request signature.

nonce true

A single-use key generated for this request. Note that each nonce may only be used once for each access key.

timestamp true

The system timestamp when the request was created in milliseconds since the Epoch (timezone independent). Note Unix time is in seconds and will need to be multiplied by 1000. Requests with old timestamps will be rejected.

reference true

A unique identifier for the forms request, returned as formsReference in the Create API response.

Response

An example of the JSON returned in the response is shown below:

Example

The values of status can be:

  • PENDING - the forms request has been created however the form hasn't been filled out yet
  • SUBMITTED - the form has been filled out and submitted, or
  • COMPLETED - all recipients have verified themselves

One or more goRequests may exist. Use the goApiReference to fetch the details of the Go request using our Go APIs.

Download

Path /forms/download/ Method GET

Fetches a download link for this forms request.

Parameter Required Description
key true

Your API Key.

signature true

An HMAC SHA-256 signature of request data for call validation. See details on generating a request signature.

nonce true

A single-use key generated for this request. Note that each nonce may only be used once for each access key.

timestamp true

The system timestamp when the request was created in milliseconds since the Epoch (timezone independent). Note Unix time is in seconds and will need to be multiplied by 1000. Requests with old timestamps will be rejected.

reference true

A unique identifier for the forms request, returned as formsReference in the Create API response.

Response

If this request is successful the response JSON will looks something like this:

Example

The downloadUrl is a short-lived URL that you can call to download the complete results of the Forms request at this point in time.

This file is usually a zip file for a completed request, containing the intial form, each verification result, as well as any other supporting documentation and files that were uploaded during the process. However, for simple form requests, or incomplete requests, the download file may be a single PDF.