API Terms

These API Terms of Use ("API Terms") govern your access to and use of any application programming interface made available by Venuvo AB (org.nr 559499-4484) ("Venuvo API" or "API"). These API Terms supplement the Terms of Service and all capitalized terms not defined herein have the meanings given in the Terms of Service.

By accessing or using the Venuvo API, you agree to be bound by these API Terms in addition to the Terms of Service, EULA, and all other applicable policies. If you do not agree to these API Terms, you must not access or use the API.

What is an API? An Application Programming Interface (API) allows different software programs to communicate with each other. The Venuvo API allows you to connect your own tools and systems to the Venuvo platform programmatically.

1. API access and authentication

1.1 Eligibility

API access is available on qualifying subscription tiers as specified on our pricing page. Not all subscription plans include API access. Venuvo reserves the right to modify API availability across subscription tiers with thirty (30) days' notice.

1.2 API Keys

To access the API, you must generate API keys through your account settings. API keys are confidential credentials equivalent to your account password. You shall:

• Keep API keys strictly confidential and not share them with unauthorized individuals.
• Never embed API keys in client-side code (JavaScript in web browsers), mobile application source code available through app stores, or public code repositories (e.g., GitHub, GitLab, Bitbucket).
• Rotate API keys periodically (at least every ninety (90) days) and immediately upon any suspected compromise.
• Use environment variables or secure secret management systems to store API keys.
• Immediately revoke and regenerate any API key that you believe has been compromised, and notify Venuvo at info@venuvo.net.

You are responsible for all API activity associated with your API keys, whether authorized or unauthorized.

2. Permitted use

The Venuvo API may be used solely for the following purposes:

• Integrating the Service with your own internal business systems (CRM, ERP, accounting, marketing automation, etc.).
• Building internal tools and dashboards that access your Customer Data in the Service.
• Automating workflows and data synchronization between the Service and your authorized third-party applications.
• Developing custom applications for your internal business use that consume or interact with data in your Venuvo account.

API access is limited to accessing and managing your own Customer Data. You may not use the API to access, modify, or interact with data belonging to other Venuvo customers.

3. Rate limits and quotas

3.1 Rate Limits

API usage is subject to rate limits as specified in the API documentation. Rate limits are applied per API key and may vary by subscription tier and endpoint. Current rate limits are published in the API documentation and may be updated from time to time.

3.2 Throttling

If you exceed published rate limits, the API will return appropriate HTTP status codes (429 Too Many Requests) with a Retry-After header indicating when you may resume requests. Your application should implement exponential backoff and respect Retry-After headers.

3.3 Quota Adjustments

Venuvo reserves the right to adjust rate limits and quotas at any time. If your usage consistently exceeds standard limits, we may contact you to discuss higher-tier access or custom arrangements. Venuvo will provide reasonable notice before reducing rate limits below previously published levels.

4. Restrictions

In addition to the restrictions in the Terms of Service, EULA, and AUP, the following restrictions apply specifically to API usage:

• No scraping or bulk extraction: You may not use the API for systematic scraping, crawling, indexing, or bulk downloading of data beyond your own Customer Data.
• No circumvention: You may not circumvent, bypass, or disable any authentication, rate limiting, access control, or security mechanism of the API.
• No competitive use: You may not use the API for benchmarking, competitive analysis, performance testing, or to design, develop, or operate a product or service that competes with the Service.
• No redistribution: You may not redistribute, resell, or sublicense API access or create wrapper services that expose the API to third parties.
• No excessive load: You may not send requests at a volume or frequency that degrades the API's performance for other customers.
• No automated account creation: You may not use the API to create user accounts programmatically without Venuvo's written authorization.
• No data mining: You may not use the API to mine, extract, or aggregate data for purposes unrelated to your own Customer Data management.

5. Security requirements

All API integrations must comply with the following security requirements:

• HTTPS only: All API communications must use HTTPS (TLS 1.2 or higher). Unencrypted HTTP requests will be rejected.
• Authentication: Every API request must include valid authentication credentials (API key in the request header).
• Input validation: Your application must validate and sanitize all data before sending it to the API. Do not pass user input directly to API calls without proper validation.
• Error handling: Implement proper error handling, including retry logic with exponential backoff for transient errors (5xx status codes) and appropriate handling of authentication errors (401, 403).
• Data minimization: Request only the data fields you need. Use pagination for large result sets.
• Vulnerability reporting: If you discover a security vulnerability in the API, report it immediately to info@venuvo.net and do not exploit or publicly disclose the vulnerability.

6. API changes and versioning

6.1 Versioning

The API may use version identifiers (e.g., v1, v2) to maintain backward compatibility. When a new version is released, previous versions will be supported for at least twelve (12) months from the date the new version becomes generally available.

6.2 Deprecation

When an API version or endpoint is scheduled for deprecation, we will provide at least ninety (90) days' advance notice via the API documentation and email to account administrators. Deprecated endpoints will return warning headers before being removed.

6.3 Breaking Changes

We will use commercially reasonable efforts to maintain backward compatibility within API versions. Where breaking changes are necessary, we will release them as a new API version and provide migration documentation.

7. Service levels

API availability is subject to the same SLA as the Service. No additional or separate uptime guarantees apply to API endpoints. API performance metrics (latency, throughput) are not covered by the SLA but are monitored by Venuvo to maintain acceptable performance levels.

8. Termination of API access

Venuvo may suspend or revoke your API access, immediately and without notice, if: (a) you violate these API Terms, the Terms of Service, or the AUP; (b) your API usage poses a security risk to the Service or other customers; (c) your API usage materially degrades the performance of the Service for other customers; or (d) your Subscription is suspended or terminated. Upon termination, you must immediately cease all API usage, delete all cached API data, and revoke all API keys.

9. Disclaimer

The API is provided "as is" and "as available." Venuvo does not warrant that the API will be uninterrupted, error-free, secure, or compatible with your systems. Venuvo is not responsible for any issues arising from changes to the API, including changes that break your integration. You are solely responsible for testing and maintaining your API integrations.

10. Contact

Venuvo AB

Org.nr: 559499-4484

Örebro, Sweden

Email: info@venuvo.net

Website: https://www.venuvo.net