Legal policy

API Terms

Last Updated: June 24, 2026*Draft for lawyer review

Rules for Vibeler APIs, app integrations, same-origin API proxy use, automation, and approved developer access.

Draft for lawyer review: This page is a practical Vibeler policy draft, localized for Canadian requirements where relevant. It is not legal advice and should be reviewed by counsel before launch or enforcement.

Jump to section

1. Draft status and scope

These API Terms are a practical operating draft and must be reviewed by a qualified Canadian lawyer before launch. Vibeler currently exposes backend APIs primarily for Vibeler's own web app and approved integrations. Vibeler does not yet promise a self-serve public developer API program.

2. Permitted API use

  • Use APIs only through Vibeler's documented app flows, same-origin proxy, or written approval.
  • Keep credentials, cookies, tokens, webhook secrets, and API keys confidential.
  • Respect rate limits, access controls, viewer-scoped data boundaries, and stage ownership.
  • Use returned data only for the lawful purpose for which your account, Stage, or integration is authorized.

3. Prohibited API use

  • Scraping, crawling, harvesting, bulk exporting, or enumerating users, stages, handles, channels, emails, media, products, or private content without written permission.
  • Bypassing paywalls, private-channel rules, entitlement checks, media gateway controls, rate limits, authentication, custom-domain restrictions, or security features.
  • Using Vibeler APIs to build or train a competing product, reverse engineer the Services, or infer non-public business logic.
  • Sending spam, unlawful content, malware, phishing, abusive requests, or misleading commercial communications.
  • Submitting data to Vibeler APIs without the rights, consents, privacy notices, and CASL consents required for that data.

4. Webhooks and integrations

If Vibeler provides webhook, import, export, or integration access, you must validate signatures where applicable, handle retries idempotently, protect secrets, and avoid processing data beyond the integration scope.

Vibeler may revoke API or integration access for security, abuse, legal, payment, deliverability, privacy, or platform-integrity reasons.

5. No API availability guarantee

APIs may change, be rate-limited, return errors, be unavailable, or be restricted without creating an uptime, compatibility, export, or support guarantee unless Vibeler signs a separate written agreement.

All policies

Structural reference: Bento API Terms. Vibeler policy text is original and adapted to Vibeler's product surface.