API Reference (v2.1)

INTRO

The Intercheck API is used to submit background checking requests and built using RESTful endpoints and standard HTTPS verbs. Here is a quick summary of the existing API:

  • Authentication to the API is performed via Token-based auth.
  • Requests to our API should be made as JSON, except when uploading documents.
  • JSON is returned on all our API responses, including errors, with a consistent structure for all messages. The Response codes are used to indicate the status of the message and any error codes.

The API endpoints in this reference are for the Production API. Change the hostname to showcase.policecheckexpress.com.au when accessing the Sandbox (Showcase) API.

This is the current (latest) version of our API v2.1

GET SECURITY TOKEN

A security token must be provided in every request made to the API. All API requests must be made over HTTPS.

Get your (Production) Token

Login to the Business Portal > click menu Administration > Business Setting > API

For the Sandbox (showcase) environment, use the (test) token provided by our IT team instead.

Whitelisting IP addresses

For additional security, you can restrict the source IP addresses allowed to call the API.

API DOCUMENTATION

GET APPLICANT'S INFORMATION API

BY EMAIL:

Get application’s information by using email as the parameter

HTTP Request

GET: https://secure.policecheckexpress.com.au/api/policeCheck

Parameters

Parameter Type Description Required?
token string Security Token Yes
applicant string Applicant’s email Yes

Response

The API will respond with an HTTP 200 and the applicant's information object.

        
HTTP/1.1 200 Success
Content-Type: application/json
        
        
{
  “id”: APPLICANT_REFERENCE_NO,
  “firstName”: APPLICANT_FIRST_NAME,
  “lastName”: APPLICANT_LAST_NAME,
  “email”: APPLICANT_EMAIL,
  “purpose”: APPLICANT_PURPOSE,
  “status”: (YES/NO/PENDING),
  “error”: (true/false),
  “errorMessage”: (if error = true , it shows error message)
}
        
      

Errors

Message Description
Miss Parameters When The parameter is incorrect
The Token is not valid When The Secure Token is incorrect
IP Restriction When request sent from an IP that is not included in the saved list of safe IP addresses
The Applicant not found When we cannot find Reference number you sent or you don’t have access to police check for this applicant
General Exception When Something wrong happens to the system

BY REFERENCE NUMBER:

Get application’s information by using Application Reference Number as the parameter.

HTTP Request

GET: https://secure.policecheckexpress.com.au/api/policeCheck/reference

Parameters

Parameter Type Description Required?
token string Security Token Yes
applicant string Application reference number Yes

Response

The API will respond with an HTTP 200 and the applicant's information object.

        
HTTP/1.1 200 Success
Content-Type: application/json
        
        
{
  “id”: APPLICANT_REFERENCE_NO,
  “firstName”: APPLICANT_FIRST_NAME,
  “lastName”: APPLICANT_LAST_NAME,
  “email”: APPLICANT_EMAIL,
  “purpose”: APPLICANT_PURPOSE,
  “status”: (YES/NO/PENDING),
  “error”: (true/false),
  “errorMessage”: (if error = true , it shows error message)
}
        
      

Errors

Message Description
Miss Parameters When The parameter is incorrect
The Token is not valid When The Secure Token is incorrect
IP Restriction When request sent from an IP that is not included in the saved list of safe IP addresses
The Applicant not found When we cannot find Reference number you sent or you don’t have access to police check for this applicant
General Exception When Something wrong happens to the system

CREATE CHECK API

Invited Check:

Send an invitation to the Applicants to do the Police Check

HTTP Request

POST: https://secure.policecheckexpress.com.au/api/policeCheck/invite

Parameters

Parameter Type Description Required?
token string Security Token Yes
checkType number 1 for Standard, 2 for Volunteer Yes
paidInvite number 1 for PrePay, 0 for PassPay Yes
department string Department name No
email string Applicant’s email Yes
surname string Applicant’s surname Yes
givenName string Applicant’s first name Yes
userFullname string Business representative's full name Yes
purchaseOrder string Applicant purchase order No
reminderCount number Applicant’s reminder count No
phone number Applicant’s phone number No
empId number Applicant’s employee ID No
purpose string Applicant’s purpose Yes
childVul boolean If applicant has direct contact with any Children, Elderly, Vulnerable or Disabled Persons Yes

Response

The API will respond with an HTTP 200 and the created check object.

        
HTTP/1.1 200 Success
Content-Type: application/json
        
        
{
  "token": xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx,
  "checkType": 1,
  "paidInvite": 1,
  "department": DEPARTMENT_NAME,
  "email": APPLICANT_EMAIL,
  "surname": APPLICANT_SURNAME,
  "givenName": APPLICANT_GIVEN_NAME,
  "phone": APPLICANT_PHONE,
  "empId": APPLICANT_EMPLOYEE_ID,
  "reminderCount": APPLICANT_REMINDER_COUNT,
  "purchaseOrder": APPLICANT_PURCHASE_ORDER,
  "purpose": APPLICANT_PURPOSE,
  "childVul": true,
  "error": false,
  "message": "New Check Created successfully"
}
        
      

Errors

Message Description
Miss Parameters When The parameter is incorrect
The Applicant Email is not valid When The Format of Email is incorrect
The Token is not valid When The Secure Token is incorrect
IP Restriction When request sent from IP that is not defined
Given Name is required! When Given Name is Empty
Surname is required! When Surname is Empty
User FullName is required! When user’s full name is missing
The Applicant Phone is not valid! When Phone is not valid
CheckType is not valid! When Check Type is not 1 Or 2
Paid Invite is not valid! When Paid Invite is not 1 Or 0
The Department is not valid! When the name of the department is not defined in the system
Insufficient credit to do volunteer check When you have Insufficient credit for volunteer
Insufficient credit to do standard check When you have Insufficient credit for standard
The Purchase Order is not valid-Max Length Exceed! When the Purchase Order is more than 100 characters
The Employee ID is not valid-Max Length Exceed! When the Employee ID is more than 100 characters

Portal Check:

The Business has an option to vet for the Applicant from their end

This is used by Direct Business only.

HTTP Request

POST: https://secure.policecheckexpress.com.au/api/portalCheckDirect/new

Parameters

Parameter Type Description Required?
token string Security Token Yes
checkType number 1 for Standard, 2 for Volunteer Yes
empId number Applicant’s employee ID No
purchaseOrder string Applicant’s purchase order No
department string Department name No
email string Applicant’s email Yes
names List List of names Yes (Please see detail below)
surname string Applicant’s surname Yes
givenName string Applicant’s first name Yes
userFullname string Business representative's full name Yes
otherGivenName string Applicant's other given name No
singleNameOnly boolean If the declared name is single name No (Yes If the declared name is a single name)
type string Valid input: PRIM/ Alias/ Maiden/ Previous No
gender string Applicant gender. Valid input: M/F/U Yes
dateOfBirth number Applicant's date of birth No
birthCountry string Country code. Global value No
birthSuburb string Suburb of town No
birthState string Birth state No
addresses List Applicant’s addresses Yes (Please see details below)
homePhone Number Applicant’s home phone No
workPhone Number Applicant’s work phone No
mobilePhone Number Applicant’s mobile phone No
licenseNo string Driver license number No
licenseIssueBy string Driver license Issue date No (Yes If “licenseNo” is mentioned)
firearms string Firearm license number No
firearmIssueBy String Firearm license Issue date No (Yes If “firearms” is mentioned)
purpose String Application’s purpose Yes
user String User’s full name Yes
childVul Boolean If applicant has direct access contact with Children, Elderly, Vulnerable or Disabled persons Yes
● Names
Attribute Type Description Required?
surname string Applicant's surname Yes
givenName string Applicant's first name Yes
otherGivenName string Applicant other given name No
singleNameOnly boolean If the declared name is a single name No
type string Valid input PRIM/ Alias/Maiden/Previous Yes
● Addresses
Attribute Type Description Required?
country string Applicant's Address Country Yes
streetNo string Applicant's Address Street No Yes
streetName string Applicant's Address Street Name Yes
postCode string Applicant’s Address State/Territory No
suburb string Applicant’s Address suburb No
yearFrom number Applicant’s Address Year From Yes
monthFrom number Applicant’s Address Month From Yes
dayFrom number Applicant’s Address Day From Yes
yearTo number Applicant’s Address Year To Yes
monthTo number Applicant’s Address Month To Yes
dayTo number Applicant’s Address Day To Yes
type string Applicant’s Address type Yes

Response

The API will respond with an HTTP 200 and email of applicant created the check.

        
{
  "email": APPLICANT_EMAIL,
  "error": false,
  "message": "New Check Created successfully"
}
        
      

Errors

Message Description
Miss Parameters When The parameter is incorrect
The Applicant Email is not valid When The Format of Email is incorrect
The Token is not valid When The Secure Token is incorrect
IP Restriction When request sent from IP that is not defined
Given Name is required! When Given Name is Empty
Surname is required! When surname is Empty
The User is required When “userFullname” is missing
The Applicant Phone is not valid! When Phone is not valid
CheckType is not valid! When CheckType is not 1 Or 2
The Department is not valid! When the name of the department is not defined in the system
Insufficient credit to do standard check When you have Insufficient credit for standard
The Purchase Order is not valid-Max Length Exceed! When the Purchase Order is more than 100 characters
The Employee ID is not valid-Max Length Exceed! When the Employee ID is more than 100 characters
The Applicant birthMonth is required When the birth month is missing
The Applicant birthYear is required When the birth year is missing
The Applicant Country is required When the birth country is missing
The Applicant Country is not Valid When the country is invalid
The Address Object is required! Address Object is missing
The Address Country is required Address Country is missing
The Address Country is not Valid Address Country is invalid
The Address Street No is required The Street Number is missing
The Address Street Name is required The Street Name is missing
The Address Year From is required The Start Year is missing
The Address Year To is required The End Year is missing
The ChildVul is required Children Vulnerable option is not selected
The Purpose is required The Purpose of the check is missing
The Applicant birthday is required The Applicant’s birthday is missing

VEVO CHECK:

Send an invitation to the Applicants to do the Right-to-work checks

HTTP Request

POST: https://secure.policecheckexpress.com.au/api/vevoCheck/invite

Parameters

Parameter Type Description Required?
token string API secure token Yes
surname string Applicant’s surname Yes
givenName string Applicant’s given name Yes
phoneHome string Applicant's Home phone No
phoneWork string Applicant’s Work phone No
phoneMobile string Applicant’s Mobile Phone No
birthDay integer Applicant’s day of birth Yes
birthMonth integer Applicant's month of birth Yes
birthYear string Applicant’s year of birth Yes
passportNo string Applicant’s Passport Number Yes
passportCountry string Passport Country. Country Code. Global Value Yes
employerId string Employer ID No

Response

The API will respond with an HTTP 200 and email of applicant created the check

        
{
  "email": APPLICANT_EMAIL,
  "error": false,
  "message": "New Right to work Created successfully"
}
        
      

Errors

GET VEVO CHECK DETAIL API

BY EMAIL:

Get Vevo check details by using Applicant’s Email

HTTP Request

GET: https://secure.policecheckexpress.com.au/api/vevoCheck

Parameters

Message Description
Miss Parameters When The parameter is incorrect
The Applicant Email is not valid When The Format of Email is incorrect
The Token is not valid When The Secure Token is incorrect
IP Restriction When request sent from IP that is not defined
Given Name is required! When Given Name is Empty
Surname is required! When surname is Empty
The Applicant Phone is not valid! When Phone is not valid
Passport is required! When Passport is Empty
Passport Country is required! When Passport Country is Empty
The Applicant birthDay is required When the birth day is missing
The Applicant birthMonth is required When the birth month is missing
The Applicant birthYear is required When the birth year is missing
Parameter Type Description Required?
token string API Security Token Yes
applicant string Applicant’s email address Yes

Response

The API will respond with an HTTP 200 and the check object

        
{
  "id": VEVO_REF_NUMBER,
  "firstName": APPLICANT_FIRSTNAME,
  "status": APPLICATION_STATUS,
  "lastName": APPLICANT_LASTNAME,
  "email": APPLICANT_EMAIL,
  "passport": PASSPORT_NUMBER,
  "country": COUNTRY_OF_ORIGIN,
  "resultDate": RESULT_DATE,
  "expireDate": EXPIRATION_DATE,
  "grantDate": GRANT_DATE,
  "applicant": (Primary/Secondary),
  "classification": VISA_CLASSIFICATION,
  "workEntitlement": VEVO_RESULT,
  "error": ERROR_CODE,
  "errorMessage": EROR_MESSAGE
}
        
      

Errors

Message Description
Miss Parameters When parameter is missing or incorrect
The Applicant Email is not valid When the email format is incorrect
The Token is not valid When the secure token is incorrect
IP Restriction When request sent from an IP that is not included in the saved list of safe IP addresses
The Applicant not found When we cannot find Reference number you sent or you don’t have access to police check for this applicant
General Exception When Something wrong happens to the system

BY VEVO REFERENCE NUMBER:

Get Vevo check details by using Application Ref number

HTTP Request

GET: https://secure.policecheckexpress.com.au/api/vevoCheck/reference

Parameters

Parameter Type Description Required?
token string API Security Token Yes
refno int Applicant Ref Number Yes

Response

TThe API will respond with an HTTP 200 and the check object.

        
{
  "id": VEVO_REF_NUMBER,
  "firstName": APPLICANT_FIRSTNAME,
  "status": APPLICATION_STATUS,
  "lastName": APPLICANT_LASTNAME,
  "email": APPLICANT_EMAIL,
  "passport": PASSPORT_NUMBER,
  "country": COUNTRY_OF_ORIGIN,
  "resultDate": RESULT_DATE,
  "expireDate": EXPIRATION_DATE,
  "grantDate": GRANT_DATE,
  "applicant": (Primary/Secondary),
  "classification": VISA_CLASSIFICATION,
  "workEntitlement": VEVO_RESULT,
  "error": ERROR_CODE,
  "errorMessage": EROR_MESSAGE
}
        
      

Errors

Message Description
Miss Parameters When parameter is missing or incorrect
The Applicant Email is not valid When the email format is incorrect
The Token is not valid When the secure token is incorrect
IP Restriction When request sent from an IP that is not included in the saved list of safe IP addresses
The Applicant not found When we cannot find Reference number you sent or you don’t have access to police check for this applicant
General Exception When Something wrong happens to the system

REPORTS API

The user will need to set up a webhook to listen for the results of the reports.Please refer to InterCheck’s Client Library in GitHub for further information.

HTTP Request

GET: https://secure.policecheckexpress.com.au/api/policeCheck/report

Response

TThe API will respond with an HTTP 200 and the report.

        
{
  “error”:false,
  “errorMessage”:NULL,
  “applicants”:[
  {
    “referenceNo”:APPLICANT_REFERENCE_NO,
    “name”:APPLICANT_FULL_NAME,
    “department”:APPLICANT_DEPARTMENT,
    “statusDescription”:APPLICANT_STATUS,
    “checkMethodDescription”:CHECK_METHOD_STATUS,
    “paidInvite”:(true/false),
    “dco”:disclosable court outcomes(“YES”/”NO”/”PENDING”),
    “resultDestroyed”:(true/false),
    “resultDate”:RESULT_DATE,
    “empId”:APPLICANT_EMPLOYEE_ID,
    “purchaseOrder”:APPLICANT_PURCHASE_ORDER
    }
  ]
}
        
      

Errors

Message Description
Miss Parameters When The parameter is incorrect
The Token is not valid When The Secure Token is incorrect
IP Restriction When request sent from an IP that is not included in the saved list of safe IP addresses
The Status is not found When The Status is incorrect
General Exception When Something wrong happens to the system

Limits

The Intercheck API is rate limited to prevent abuse. Every API request is recorded and if more requests are made during a time period than allowed, requests will be rate limited until the end of the time period. The limits are high enough that typical usage should rarely, if ever, be rate limited.

JSON and rate limiting

Most Intercheck customers use JSONP for autocomplete and search results. Because JSONP requests originate from your users, it is unlikely they will be affected by rate limiting, unless one of the users is abusing the service.

Rate limiting example

Requests that have been rate limited will respond with HTTP 429 Too Many Requests. HTTP 429 is a new (but very useful) status code proposed by RFC 6585. If the request was for a JSON resource, the response body will be JSON as well.

EXAMPLE - Rate limited JSON resource
        
curl -i -XGET 'http://search-api.intercheck.com/api/v1/public/engines/suggest.json?callback=foo&q=search&engine_key=your_engine_key'
        
      
EXAMPLE RESPONSE
        
HTTP/1.1 429
Content-Type: application/json; charset=utf-8
Content-Length: 32
        
        
{ 
  "error": "Rate limit exceeded." 
}
        
      

Rate limit mitigation

If your application is being negatively affected by rate limiting, please contact help@intercheck.com.au with details and we will help address the issue.

Terms of Use

1. Acceptance of Terms

This Intercheck API / WebHooks Terms of Service document (the “API / WebHooks TOS”) is an agreement you must accept in order to use the Intercheck API / WebHooks (as described below). This document describes both your rights and your obligations as part of using the Intercheck API / WebHooks. It is important that you read it carefully because you will be legally bound by these terms. Intercheck Technologies, Inc. (“Intercheck” “we” “us”) only provides the Intercheck API / WebHooks to you subject to this API TOS. By accepting this API / WebHooks TOS or by accessing or using the Intercheck API / WebHooks, you agree to be bound by this API / Webhooks TOS (including the Privacy Policy, Brand Guidelines, and general Terms of Service, which are incorporated here by reference).


If you are entering into this API / WebHooks TOS on behalf of a company or other legal entity, you represent that you have the authority to bind such entity to this API / WebHooks TOS. In that case, the terms “you” or “your” shall also refer to such entity. If you do not have such authority, or if you do not agree with this API / WebHooks TOS, you may not use the Intercheck API. You acknowledge that this API / WebHooks TOS is a contract between you and Intercheck, even though it is electronic and is not physically signed by you and Intercheck, and it governs your use of the Intercheck API / WebHooks.

2. API / WebHooks Key Definitions

2.1 Application – Any software application, website, or product you create or service you offer using the Intercheck API (defined below).

2.2 API / WebHooks Documentation – The documentation, data, and information that Intercheck provides regarding the use of the Intercheck API / WebHooks through the Developer Site.

2.3 Data – means any data and content uploaded, posted, transmitted or otherwise made available by users via the Services, including messages, files, comments, profile information and anything else entered or uploaded into the Service by a user of the Service.

2.4 Developer Site – Intercheck’s Developer site found at https://apidocs.Intercheck.com.au/

2.5 Intercheck API or “our API” – The publicly available Intercheck Application Programming Interface (“API”) as well as the related API Documentation.

2.6 Intercheck WebHooks or “WebHooks” – The publicly available Intercheck WebHook service.

2.7 Intercheck Brand – The Intercheck brand and brand assets, including names, logos, trade names, and trademarks.

2.8 Intercheck Service(s) – Intercheck’s real-time communication, messaging, archiving and search services and related systems and technologies, as well as the website http://Intercheck.com.au (the “Site”), and all software, applications, data, reports, text, images, and other content made available by or on behalf of Intercheck through any of the foregoing. The “Service” does not include Data or any software application or service that is provided by you or a third party (including Applications), whether or not Intercheck designates them as “official integrations”.

3. API / WebHooks License

As long as you follow this API / WebHooks TOS, Intercheck grants you a limited, non-exclusive, non-assignable, non-transferable license to use the APIs to develop, test, and support any software application, website, or product, and to integrate the Intercheck APIs with your Application. Your license is subject to the limitations set forth in Section 4.2 through 4.11 and Section 9 below, and you agree that violation of Section 4 will automatically terminate your license to use the Intercheck APIs / WebHooks.

4. Use of APIs, WebHooks and Intercheck Data

The following identifies limitations on use related to the Intercheck API / WebHooks:

4.1 Reliance on API / WebHooks Intercheck is still evolving, and we need the flexibility to occasionally make changes to our APIs / WebHooks, including backward incompatible ones. We will try to give notice of these changes, but you should follow the @Intercheckapi Twitter account for updates. Also, parts of our API / WebHooks are undocumented, including certain methods, events, and properties. Given that these undocumented aspects of our API / WebHooks may change at any time, you should not rely on these behaviors.

4.2 Applicable laws or agreements. You may not use the Intercheck API / WebHooks in violation of any law or regulation, or rights of any person, including but not limited to intellectual property rights, rights of privacy, or rights of personality, or in any manner inconsistent with this API / WebHooks TOS or Intercheck’s other agreements to which you are subject.

4.3 The scope of acceptable use. You may not use the Intercheck API / WebHooks or any other technology in a manner that accesses or uses any information beyond what Intercheck allows under this API / WebHooks TOS or the Documentation; that changes the Intercheck Service; that breaks or circumvents any of Intercheck’s technical, administrative, process or security measures; that disrupts or degrades the performance of the Intercheck Service or the Intercheck API / WebHooks; or that tests the vulnerability of Intercheck’s systems or networks.

4.4 Malware. You may not transmit any viruses or other computer programs that may damage, detrimentally interfere with, surreptitiously intercept, or expropriate any system or data.

4.5 Reverse engineering. You may not attempt to reverse engineer or otherwise derive source code, trade secrets, or know-how in the Intercheck API / WebHooks or portion thereof;

4.6 Functionality. You may not use the Intercheck API / WebHooks to replicate or compete with core products or services offered by Intercheck. You acknowledge and agree that Intercheck has or may in the future offer products or services that are similar to your Application, and nothing will prevent Intercheck from doing so;

4.7 Commercial Use. You may charge for your Application. However, you may not sell, rent, lease, sublicense, redistribute, or syndicate access to the Intercheck API / WebHooks

4.8 Advertising. You may place advertisements on and around your Application. However, you may not:

  1. Place any advertisements on Intercheck Service channels, and your advertisements may not resemble or be reasonably likely to confuse users as being an Intercheck Service message;
  2. Use Data or any content from Intercheck in any advertisements or for purposes of targeting advertisements, in your Application or elsewhere; or
  3. Use contact information obtained from Intercheck (including email addresses) to contact Intercheck users outside of Intercheck without their express permission.

4.9 Rate Limits. You will not attempt to exceed or circumvent limitations on access, calls and use of Intercheck API / WebHooks, or otherwise use the Intercheck API / WebHooks in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise fails to comply or is inconsistent with any part of this API / WebHooks TOS or the Documentation. See https://apidocs.Intercheck.com.au/apireference.html#limits.

4.10 Use for promotion of gambling or adult content. You may not use the Intercheck APIs / WebHooks in any Application that includes adult content, promotes gambling, involves the sale of tobacco or alcohol to persons under 21 years of age, or otherwise violates any applicable law or regulation.

4.11 Distribution of your application. You may not distribute or allow access to the Intercheck APIs / WebHooks to anyone other than, if applicable, the company on whose behalf you entered into this API TOS. Anyone who wants to access our APIs / WebHooks must agree to be bound by this API / WebHooks TOS.

5. Use of Intercheck Brand or Marks

You must not use the Intercheck Brand in a way that suggests your service is endorsed by, sponsored by, or associated with Intercheck, and you must abide by Intercheck’s Brand Guidelines available at https://Intercheck.com/brand-guidelines.

6. Storage of Data

6.1 Caching Data. Where Data is cached, you should refresh the cache at least every 24 hours.

6.2 Secure Storage Measures. All Data should be stored and served using strong encryption

6.3 Delete at User Request. You must delete all Data you have collected from an Intercheck user upon request by that user, and when the Intercheck user deauthorizes your Application or closes his or her account with you. Similarly, when a team stops using your Application, you should delete all Data obtained from that team. The restrictions of this Section do not apply to Data that Intercheck users also directly provide to you and that is separately entered or uploaded to you by the user of your Application.

6.4 Deletion at Termination. If we terminate your use of the Intercheck APIs / WebHooks for any reason, then you must permanently delete all Data and any other information that you stored pursuant to your use of the Intercheck APIs / WebHooks, except when doing so would cause you to violate any law or obligation imposed by a governmental authority. This provision does not require an Intercheck user to delete Data stored in Intercheck if the Intercheck user is prohibited from accessing the Intercheck API / WebHooks.

6.5 No Other Storing. You may not copy or store any Data or capture or store any information expressed by the Data (such as hashed or transferred data), except to the extent permitted by this API / WebHooks TOS.

7. Your User Agreement and Privacy Policy

If you offer your Application for use by others outside your organization, you must maintain a user agreement and privacy policy for your Application, which is prominently identified or located where users download or access your Application. Your privacy policy must meet applicable legal standards and accurately describe the collection, use, storage and sharing of data. You must promptly notify us of any breaches of your user agreement or privacy policy that impact or may impact Intercheck users. Your privacy policy must be at least as stringent and user-friendly as ours.

8. Security Measure

8.1 Protections. The network, operating system and software of your web servers, databases, and computer systems (collectively, “Your Systems”) must be properly configured to securely operate your Application and store Data. Your Application must use reasonable security measures to protect your users’ information. You must not architect or select Your Systems in a manner to avoid the foregoing obligation.

8.2 Reporting. You must promptly report any security deficiencies in, or intrusions to, your Systems to Intercheck in writing via email to security@Intercheck.com or subsequent contact information posted on the Developer Site. This includes any unauthorized access, use, disclosure or destruction of Data. You will work with Intercheck to immediately correct any security deficiency, and will immediately disconnect any intrusions or intruder. In the event of any security deficiency or intrusion involving the Application, Intercheck APIs / WebHooks or Data, you will make no public statements regarding such deficiencies or intrusions (e.g., press, blogs, social media, bulletin boards, etc.) without prior written and express permission from Intercheck in each instance.

9. Government Access

You will not knowingly:

9.1 Allow or assist any government entities, law enforcement, or other organizations to conduct surveillance or obtain data using your access to the Intercheck API / WebHooks in order to avoid serving legal process directly on Intercheck. Any such use by you for law enforcement purposes is a breach of this API / WebHooks TOS.

9.2 Display, distribute or otherwise make available Data or any Application to any person or entity that you reasonably believe will use Data to violate the Universal Declaration of Human Rights (located at http://www.un.org/en/documents/udhr/), including without limitation Articles 11, 17, or 18. Any law enforcement personnel seeking information about Intercheck users will be referred to Intercheck’s User Data Request Policy, located at https://Intercheck.com/user-data-request-policy. You will not conduct and your Application will not provide analyses or research that isolates a small group of individuals or any single individual for any unlawful or discriminatory purposes. Exemptions to these restrictions may be requested for exigent circumstances and are subject to prior written approval from Intercheck.

10. Ownership

As between you and us, we own all rights, title, and interest, including all intellectual property rights, in and to, the (1) Intercheck APIs / WebHooks, Documentation, and all elements and components thereof; (2) Data; (3) Intercheck Services; and (4) Brand Features (collectively, the “Intercheck Materials”). The only exception to this is Data that you as an Intercheck user have licensed to Intercheck under the https://Intercheck.com/terms-of-service, which governs that Data. Except for the express licenses granted in this API / WebHooks TOS, Intercheck does not grant you any right, title, or interest in the Intercheck Materials. You agree to take such actions as Intercheck may reasonably request to perfect Intercheck’s rights to the Intercheck Materials

11. Term and Termination

11.1 Duration of Terms. This API / WebHooks TOS will go into effect on the date upon which you agree to them, by accessing or using the Intercheck API / WebHooks, and will continue until terminated as set forth herein

11.2 Your Right to Terminate. You may terminate this API TOS by discontinuing use of our APIs / WebHooks.

11.3 Suspension; Termination. We may change, suspend or discontinue the Intercheck API / WebHooks and suspend or terminate your use of the Intercheck API / WebHooks, the Intercheck Service, and/or Intercheck Brand at any time and for any reason, without notice. Without limiting the foregoing, we may limit your Application's access to the Intercheck API / WebHooks if it, in our sole discretion, may negatively affect our Service or our ability to provide our Service.

11.4 Effect of Termination. Upon termination of this API / WebHooks TOS:

  1. All rights and licenses granted to you will terminate immediately;
  2. You will promptly destroy Documentation and any other Intercheck information in your possession or control that was received under this API / WebHooks TOS;
  3. Unless we agree otherwise in writing or as stated in this API / WebHooks TOS, you must permanently delete all Data and other information that you stored pursuant to your use of the Intercheck APIs / WebHooks. Intercheck may request that you certify in writing your compliance with this section; and
  4. Intercheck will make commercially reasonable efforts to remove all references and links to your Application from its Services (Intercheck has no other obligation to delete copies of, references to, or links to your Application).

11.5 The following sections of this API / WebHooks TOS shall survive any termination, Sections 4 (“Use of the APIs / WebHooks and Intercheck Data”), 5 (“Use of Intercheck Brand or Marks”), 6.4 (“Delete at User Request”), 6.5 (“Deletion at Termination”), 7 (“Your User Agreement and Privacy Policy”), 8 (“Security Measures”), 10 (“Ownership”), 11 (“Term and Termination”), 12 (“Other Important Terms”), 13 (“Disclaimer of Warranties; Limitation of Liability; Indemnity”), 14 (“Dispute Resolution”) and 15 (“General Legal Terms”).

12. Other Important Terms

12.1 Legal Representations. You represent and warrant to Intercheck that, excluding Intercheck Materials, you have the right to use, reproduce, transmit, copy, publicly display, publicly perform, and distribute your Application, and that use of your Application by Intercheck and its users will not violate the rights of any third party (e.g., copyright, patent, trademark, privacy, publicity or other proprietary rights of any person or entity), or any applicable regulation or law, including the Digital Millennium Copyright Act, the laws of any country in which your Application is made available and any applicable export laws

12.2 Modification of the API / WebHooks TOS. We may change, add to or delete this API / WebHooks TOS or any portion thereof from time to time in our sole discretion. If we make a material change to this API / WebHooks TOs, we will provide you with reasonable notice prior to the changes either by emailing the email address associated with your account or by posting a notice on the Developer Site. You acknowledge that these updates and modifications may adversely impact how you access, use, and communicate with the Intercheck API / WebHooks. If any change is unacceptable to you, then your only recourse is to cease all use of the Intercheck API / WebHooks. Your continued access or use of the Intercheck API / WebHooks will mean that you agree to the updates and modifications.

12.3 Other Applicable Agreements. You and your Application must also comply with the following, which are hereby incorporated by reference:

  1. Intercheck Terms of Service
  2. Intercheck Privacy Policy
  3. Intercheck Brand Guidelines

In the event of any conflict between the content in this document and the above documents, this document controls your use of the Intercheck APIs.

13. Disclaimer of Warranties; Limitation of Liability; Indemnity

13.1 NO WARRANTIES. THE INTERCHECK API / WEBHOOKS AND ALL RELATED COMPONENTS AND INFORMATION ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS WITHOUT ANY WARRANTIES OF ANY KIND, AND INTERCHECK EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. YOU ACKNOWLEDGE THAT INTERCHECK DOES NOT WARRANT THAT THE INTERCHECK API / WEBHOOKS WILL BE UNINTERRUPTED, TIMELY, SECURE, ERROR-FREE OR VIRUS-FREE, NOR DOES IT MAKE ANY WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM USE OF THE INTERCHECK API / WEBHOOKS, AND NO INFORMATION, ADVICE OR SERVICES OBTAINED BY YOU FROM INTERCHECK OR THROUGH THE DEVELOPER SITE SHALL CREATE ANY WARRANTY NOT EXPRESSLY STATED IN THIS API / WEBHOOKS TOS.

13.2 LIMITATION ON LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY (WHETHER IN CONTRACT, TORT, OR OTHERWISE) SHALL INTERCHECK BE LIABLE TO YOU OR ANY THIRD PARTY FOR (A) ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING LOST PROFITS, LOST SALES OR BUSINESS, LOST DATA, OR (B) FOR ANY AMOUNT IN THE AGGREGATE IN EXCESS OF THE FEES ACTUALLY PAID BY YOU IN THE SIX (6) MONTHS PRECEDING THE EVENT GIVING RISE TO YOUR CLAIM OR, IF NO FEES APPLY, FIVE HUNDRED ($500) AUSTRALIAN DOLLARS, OR (C) ANY MATTER BEYOND OUR REASONABLE CONTROL. THE PROVISIONS OF THIS SECTION ALLOCATE THE RISKS UNDER THIS TOS BETWEEN THE PARTIES, AND THE PARTIES HAVE RELIED ON THESE LIMITATIONS IN DETERMINING WHETHER TO ENTER INTO THIS TOS. Some jurisdictions do not allow the exclusion of implied warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply to you. IN THESE JURISDICTIONS, INTERCHECK’S LIABILITY WILL BE LIMITED TO THE GREATEST EXTENT PERMITTED BY LAW.

13.3 Indemnity. You agree to defend, hold harmless and indemnify Intercheck, and its subsidiaries, affiliates, officers, agents, employees, and suppliers, from and against any third party claim arising from or in any way related to your or your users’ use of the Application, Intercheck API / WebHooks or Data, use of Intercheck Brand, or violation of this API / WebHooks TOS, including any liability or expense arising from all claims, losses, damages (actual and consequential), suits, judgments, litigation costs and attorneys’ fees, of every kind and nature. In such a case, we will provide you with written notice of such claim, suit, or action.

14. Dispute Resolution

This API / WebHooks TOS and any claim, cause of action or dispute (“Claim”) arising out of or related to this Agreement shall be governed by the laws of the Commonwealth of Australia, regardless of your country of origin or where you access the Intercheck Service, and notwithstanding any conflicts of law principles and the United Nations Convention for the International Sale of Goods. You and Intercheck agree that all Claims arising out of or related to this Agreement must be resolved exclusively in the courts located in the county of Sydney, New South Wales. You and Intercheck agree to submit to the personal jurisdiction of the courts located within the county of Sydney, New South Wales and agree to waive any and all objections to the exercise of jurisdiction over the parties by such courts and to the venue in such courts for the purpose of litigating all such Claims. Notwithstanding the above, you agree that Intercheck shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction.

15. General Legal Terms

15.1 Severability. If any provision of this API / WebHooks TOS is found to be illegal, void, or unenforceable, the unenforceable provision will be modified so as to render it enforceable to the maximum extent possible in order to effect the intention of the provision; if a term cannot be so modified, it will be severed and the remaining provisions of this API / WebHooks TOS will not be affected in any way.

15.2 Language. Where Intercheck has provided you with a translation of the English language version of this API / WebHooks TOS or any document referenced in this API / WebHooks TOS, you agree that the translation is provided for your convenience only and that the English language versions of any such document, will control.

15.3 Notice and Service of Process. We may notify you via postings on the Developer Site or via the email address associated with your Application or Intercheck Service account. Intercheck accepts service of process by mail or courier at the physical address set forth in Section 15.9 below. Any notices that you provide without compliance with this section shall have no legal effect.

15.4 Entire Agreement. This API / WebHooks TOS and any documents incorporated into this API / WebHooks TOS by reference, constitute the entire agreement between you and Intercheck regarding the Intercheck APIs / WebHooks and supersedes all prior agreements and understandings, whether written or oral, or whether established by custom, practice, policy or precedent, with respect to the subject matter of this API / WebHooks TOS.

15.5 No Informal Waivers, Agreements, or Representations. Our failure to act with respect to a breach of this API / WebHooks TOs by you or others does not waive our right to act with respect to that breach or subsequent similar or other breaches. No representations, statements, consents, waivers or other acts or omissions by any Intercheck affiliate shall be deemed legally binding on any Intercheck affiliate, unless documented in a physical writing hand signed by a duly appointed officer of Intercheck.

15.6 Injunctive Relief. In no event shall you seek or be entitled to rescission, injunctive or other equitable relief, or to enjoin or restrain the operation of the Developer Site or Intercheck Service or any Intercheck APIs / WebHooks, or other material used or displayed through the Intercheck Developer Site or Intercheck Service

15.7 Assignment and Delegation. You may not assign or delegate any rights or obligations under this API / WebHooks TOS, including in connection with a change of control. Any purported assignment and delegation shall be ineffective. We may freely assign or delegate all rights and obligations under this API / WebHooks TOs, fully or partially without notice to you. We may also substitute, by way of unilateral novation, effective upon notice to you, Intercheck Technologies, Inc. for any third party that assumes our rights and obligations under this API / WebHooks TOs.

15.8 Potential Other Rights and Obligations. You may have rights or obligations under local law other than those enumerated here if you are located outside Australia.

15.9 How to Contact Us. If you have questions or comments about this API / WebHooks TOS or wish to make use of our Intercheck API / WebHooks in any way not permitted by this API / WebHooks TOS, please contact us via email at integrations@Intercheck.com or by physical mail at:

© 2021 InterCheck Australia. All rights reserved. InterCheck™ is a registered Trademark.