Thank you for using the Certain Web Services Application Programming Interface (the "Certain API"). By using the Certain API, you agree to the terms below. If you disagree with any of these terms, Certain does not grant you a license to use the Certain API. Certain reserves the right to update and change these terms from time to time without notice. The most recent version of these terms can always be found here.

Your license to the Certain API under these terms continues until it is terminated by either party. You may terminate the license by discontinuing use of all or any part of the Certain API. Certain may terminate the license at any time for any reason. Your rights to use the Certain API terminate automatically if (i) you violate any of these terms, (ii) Certain publicly posts a written notice of termination on Certain.com, (iii) Certain sends a written notice of termination to you, or (iv) Certain disables access to the Certain API for you.

1. Licensed Uses and Restrictions

The Certain API is owned by Certain, Inc. (hereinafter "Certain") and is licensed to you on a worldwide (except as limited below), non-exclusive, non-sublicensable basis under the terms and conditions set forth herein. These terms define the legal use of the Certain API, including all updates, revisions, substitutions, and any copies made by or for you. Registration, Profile, Event data, and other related data records are owned by the Certain customer from whose account the data was generated, and not by Certain. All rights not expressly granted to you are reserved by Certain.

1. You shall:

1. Comply with the Certain Privacy Policy at https://certain.com/privacy-policy/
2. Comply with all restrictions and guidelines stipulated in your Certain license agreement.
3. Disclose in your application through a privacy policy or footer on each page how you collect, use, store, and disclose data collected from visitors. Include any applicable disclosures about third-party data collection, such as advertising cookies.

1. You shall not:

1. Use Certain API for any application that replicates or attempts to replace the essential user experience of Certain.com.
2. Attempt to cloak or conceal your identity or your application's identity when requesting authorization to use the Certain API.
3. Cache or store Certain data records beyond reasonable periods necessary to provide your service to Certain users.
4. Use the Certain API in connection with any spyware, adware, or other malicious code.
5. Use Certain API in a way that violates any law or regulation, including intellectual property rights, privacy rights, or rights of personality.
6. Market indiscriminately to individuals from lists of registrants or profiles stored within the Certain system.
7. Use Certain API in a manner that adversely impacts Certain.com servers or the behavior of other applications using the Certain API.
8. Sell, lease, sublicense, or derive revenues from Certain API or access thereto without Certain's permission.
9. Exceed the concurrent API usage rate limit, which will be enforced to maintain fair usage and system stability. Exceeding this limit may result in a 429 error response (see API Rate Limit section for more details).



1. API Rate Limit Enforcement FAQ




1. 1. What is the API rate limit?

20 concurrent connections

1. 2. Why is there a rate limit?

To ensure fair usage and maintain the stability of the API and services. Similar limits are common industry-wide to prevent service abuse and ensure reliability.

1. 3. What will happen if I exceed the limit?

The system will return a 429 error ("Too Many Requests"). Retry after a specified time.

1. 4. What is a 429 error?

A 429 error is an HTTP status code for too many requests within a short time. We suggest a retry after 2 seconds and use an exponential backoff strategy.

1. 5. How does this protect customers?

Enforcing rate limits prevents excessive requests that could slow down or disrupt service for all users.

1. 6. How do I avoid hitting the rate limit?

Monitor API usage, implement a retry mechanism with a backoff strategy, and avoid concurrent requests that could trigger the rate limit.

1. 7. Developer Best Practices for Managing API Rate Limits:

• Implement Exponential Backoff: Gradually increase the wait time after a 429 error to avoid further congestion.
• Monitor and Optimize API Calls: Review integration for minimal API calls; batch or cache responses when possible.
• Handle 429 Errors Gracefully: Design systems to log 429 errors, retry after the specified time, and notify users if delays occur.
• Queue Requests: Use a queuing mechanism to distribute requests over time.
• Parallelism Controls: Limit concurrent requests to stay within the rate limit.
• API Usage Monitoring: Set up real-time monitoring for proactive rate limit management.

1. 8. What if I need more concurrent connections?

Contact your customer success manager to discuss your use case.

1. 9. Does the rate limit affect all customers?

Yes, this applies to all API users to ensure fair usage.

1. 10. Will this rate limit be adjusted in the future?

We may adjust limits based on overall system health and customer needs.

1. 11. Who can I contact if I have more questions?

Please reach out to your customer success manager.



Additional Terms of Use

Data Privacy and Security

• User Responsibility: API users are responsible for securing any data accessed, ensuring compliance with applicable privacy laws and data protection standards.
• Data Handling and Retention: Users should handle personal data obtained via the API responsibly, including securing it and deleting it when no longer needed.

API Credentials Management

• Confidentiality: Users are required to protect their API credentials and must not share them with unauthorized individuals.
• Revocation: Certain may revoke API access in the event of misuse or violation of these Terms of Use.
• Usage Limits: Using multiple API keys to circumvent rate limits is prohibited.

Changes to the API

• Modification of Functionality: Certain reserves the right to modify or discontinue API functionalities as needed. Updates may require adjustments to users' applications.
• Deprecation Notices: When possible, Certain will provide advance notice for significant changes and allow a transition period.

Service Availability and Uptime

• Downtime Disclaimer: Certain does not guarantee 100% uptime for the API. Notice will be provided when feasible for planned maintenance.
• SLAs for Enterprise Users: Service-level agreements (SLAs) may apply for customers on premium or enterprise plans.

Support

• Support Channels: Limited developer support is available through Certain's designated support channels, such as the developer portal or help desk.
• Community Resources: Users may also find assistance in community forums and documentation resources provided by Certain.

Intellectual Property

• Ownership of Data and IP: Certain retains ownership of all data and intellectual property rights associated with the API. Users may not claim ownership of any API content or derivative works.
• Use of Branding: Unauthorized use of a Certain logo or branding in applications is prohibited.

Indemnification and Liability

• Indemnification: Users agree to indemnify Certain for any claims resulting from their API usage, especially in cases where their applications impact third parties.
• Limitation of Liability: Certain is not liable for damages resulting from API use, including application downtime, revenue loss, or data breaches.

Compliance with Third-Party API Policies

• Third-Party API Policies: If Certain API integrates with third-party APIs, users must comply with those providers' terms and policies.

Termination for Non-Compliance

• Termination Conditions:Repeated rate limit violations, API resource abuse, or failure to meet data handling standards may lead to termination of access.