Restrictions on Scope and Use of the API
In connection with the EULA and the Order, and specifically section 3 “Prohibited Uses” subsection (ix), the following are the restriction on the scope of the API.
Sixgill API. The API consists of programmatic web APIs, software, interface definitions, generated code libraries and associated tools and functionalities that allow you to access and review certain data, datasets, information or content which are processed through the Solution (as defined in the EULA) and made accessible to you via the API (collectively, the “API”). Your use of the API and display of content in your application must comply with the API’s technical documentation, usage guidelines as made available to you by Sixgill (the “API Documentation) as well as the volume limits described below. Sixgill may monitor use of the API to ensure compliance with these API restrictions and to improve the Solution.
Access Credentials. You will be issued certain unique credentials, security keys, secrets or tokens (“Access Credentials”) for accessing the API and receiving the data. The Access Credentials enable Sixgill to associate your API activity with your application. The Access Credentials are to be used by your employees and authorized contractors designated by you and operating on your behalf for purpose of conducting the integration of the API with the application. You may not sell, transfer, sublicense or otherwise disclose your Access Credentials to any party other than your authorized users. You are responsible for maintaining the secrecy and security of your Access Credentials. You are fully responsible for keeping your account information up to date and for all activities that occur using your Access Credentials, regardless of whether such activities are undertaken by you or your Authorized Users.
API Modifications. Sixgill reserves the right to modify the Solution, Services and API, and to release subsequent versions of the API. You may be required to obtain and use the most recent version of the API in order to use the Solution or Services. In case of a Breaking Change to the API, Sixgill shall provide at least 30 days prior notice] . In case of a Non-Breaking API Change, Sixgill may provide reasonable advance notice of such change and its details.
For the purposes of this section,
“Breaking Changes” means a backwards incompatible update of the API that may cause a disruption to the integration with Customer’s application or lose existing functionality as related to its consumption of Sixgill’s data via the Sixgill API.
“Non-Breaking Change” is a change that the customer can adapt to at his own discretion and pace without disruption and without effecting capabilities available prior to such change.
Usage Limitations. Use of the API is subject to the monthly quota of requests. Requests to the API are limited to a rate of 300 requests per minute and 6 requests per second. Any requests beyond such rate shall result in an error notice with a relevant corresponding error code. The relevant user/s from which the excessive requests were made may experience a delay in response to request to the API for certain period of time to be determined by Sixgill or even a complete temporary cut-off from the ability to place queries to the API . You will not, and will not permit any person, directly or indirectly attempt to exceed or circumvent limitations on the API calls and use, or use the API in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise fails to comply or is inconsistent with these API Terms or the Documentation, including creating multiple Applications for identical, or largely similar, usage. Sixgill shall monitor the number of queries submitted by you.
Twitter Limitations. Without derogating from any other provision under these API Terms, any Content which includes Content received from Twitter is limited by the permission restrictions enforced by Twitter (“Twitter Content”). Such content will be marked clearly as originating from Twitter. Please note that Twitter Content shall not be redistributed via the API, except for Tweet ID and URL, tweet, author and the keywords that matched the tweet in the alert/search. In order to obtain the full Tweet content, you should use the tweet ID and at your own discretion request the full tweet content directly from Twitter using publicly available resources .
Last updated: February 20, 2023