Livid API Terms

20 Oct 2026

These API Terms apply to anyone who uses the Livid API, and sit alongside the Livid Terms of Service. If the two conflict on something about the API, these API Terms win.

The Short Version: The API lets you and the tools you build work with your Livid account without logging in. Keep your tokens secret, stay within the limits, and you're responsible for everything that comes in through your integrations, including uploads from people who aren't Livid users. In return, we'll give you notice before we change anything that would break what you've built.

1. Scope: These API Terms govern your access to and use of the Livid application programming interface, its documentation, and any API tokens (together, the "API"). The API is part of the Services under the Terms of Service, and everything in the Terms of Service applies to your use of the API unless these API Terms say otherwise.
2. Acceptance: By generating an API token or calling the API, you agree to these API Terms on behalf of yourself and the organization that owns the Livid account.

Access and API Tokens

The Short Version: An API token is a key to your account. Anyone who has it can do whatever its permissions allow, without your email. Keep it secret, give it only the permissions it needs, and revoke it the moment it might have leaked.

1. Plan Access: API access is available only on paid plans that include it, and is not available on free plans. Livid may change which plans include API access in line with the Terms of Service.
2. Who Can Generate Tokens: Only members of your organization with permission to manage API tokens can generate or revoke them. Each token belongs to one organization and can only access that organization's content.
3. Token Permissions: You choose a token's permissions when you generate it. You are responsible for giving each token only the permissions its use needs.
4. Token Security: API tokens are credentials that give access to your account independently of the magic-link email login described in the Terms of Service. You are solely responsible for keeping your tokens confidential and for storing them securely on servers you control. You must not place a token in code that runs in a web browser or mobile app, publish it, or share it with anyone not authorized to act for your organization.
5. Revocation: You must revoke a token without delay if you know or suspect it has been exposed, or if the person or service it was issued to should no longer have access. A token remains valid until it expires or is revoked, including after the person who generated it leaves your organization or loses their permission to manage tokens.
6. Responsibility for Token Activity: All activity carried out with your API tokens is treated as activity on your account, whether or not you authorized it. Livid is not liable for any data loss, financial loss, or reputational damage resulting from the use of a token that was not kept secret or was not revoked.

Using the API

The Short Version: Build whatever you like on Livid: upload forms, migration tools, internal workflows, plugins for other platforms. Just stay within the rate limits, don't try to get around them, and remember that if you give a token to someone else's tool, what that tool does is on you.

1. Permitted Use: You may use the API to build applications, integrations, plugins and automations that work with your Livid account, including tools that move content into or out of Livid, and tools you offer to your own customers.
2. Rate Limits: You must stay within the rate limits set out in the API documentation, which Livid may change from time to time. You must not attempt to exceed or get around them, for example by spreading requests across several tokens or accounts. Requests over a limit may be refused.
3. Prohibited Use: You must not use the API to: (a) break the Terms of Service or the Acceptable Use Policy; (b) access, or try to access, content or accounts that are not yours; (c) interfere with, overload or disrupt the Services or other customers; (d) probe, scan or test the Services for vulnerabilities, except as permitted by any security disclosure policy Livid publishes; or (e) misrepresent your application as made, endorsed or operated by Livid.
4. Third-Party Applications: If you give an API token to an application, plugin, agency, contractor or other service you did not build, you authorize it to act for your organization within that token's permissions. You are responsible for that third party's use of the token as if it were your own. Livid does not review or support third-party applications and is not responsible for them.
5. Your Applications: If you build an application on the API for other people to use, you are responsible for it, for supporting its users, and for any terms or privacy notices it needs. You must not imply that Livid is a party to your terms with your users.

Content Uploaded Through Your Integrations

The Short Version: If you use the API to let other people upload to your account (say, filmmakers submitting to your festival), their videos are your responsibility, just like your own. They never signed up to Livid, so you need to make sure they have the rights to what they upload and that it follows our rules.

1. Uploaders: "Uploaders" means anyone who sends content to your Livid account through an application or integration that uses your API tokens, including members of the public who are not Livid users and have not accepted the Terms of Service.
2. Your Responsibility: Content sent by Uploaders is User Content of your account. You are responsible for it as if you had uploaded it yourself, including its compliance with the Acceptable Use Policy and the Copyright & DMCA Policy.
3. Rights: Before accepting content from Uploaders, you must obtain from them the rights needed for you to store, process and share their content through the Services, and for Livid to do so under the license in the Terms of Service. You must also get their confirmation that they own or are authorized to submit it.
4. Moderation: You are responsible for reviewing content from Uploaders and removing anything that breaks the Acceptable Use Policy. Livid may remove such content and suspend your tokens or account under the Terms of Service, even if you did not upload it yourself.
5. Privacy: If you collect personal information from Uploaders, such as names or email addresses, you are responsible for doing so lawfully and for giving them any notices required.
6. Indemnity: Your obligations under the Indemnification section of the Terms of Service apply to claims arising from content sent by Uploaders and from your applications and integrations.

Bandwidth and Storage

The Short Version: Videos uploaded or streamed through the API count towards your storage and bandwidth exactly like everything else.

1. Storage: Content uploaded through the API counts towards your plan's storage quota under the Terms of Service. An upload that would take your account over its quota will be refused. A video whose upload has been started but not finished counts towards your storage, as described in the API documentation, until it is finished or removed.
2. Bandwidth: All data transfer from your account counts towards your Bandwidth Cap and any Overage Fees under the Terms of Service, whether it comes from the Livid app, embeds, watch pages or the API, including downloads through the API.

Changes to the API

The Short Version: We'll keep improving the API, and most changes won't affect anything you've built. If we ever need to change something in a way that would break your integration, we'll tell you at least 60 days in advance, unless it's needed to fix a security problem or comply with the law.

1. Versions: The API is versioned, and the version is shown in the address of every call.
2. Non-Breaking Changes: Livid may make changes that do not break existing integrations at any time without notice. These include adding new calls, new optional request fields, new fields in responses, and new values where the documentation says more may be added. Your integration should ignore response fields it does not recognize.
3. Breaking Changes: For any change that would stop a correctly built integration on the current version from working, such as removing a call or field, or changing a field's meaning, Livid will give at least 60 days' notice before the change takes effect, or make it only in a new version.
4. Retiring a Version: Livid will give at least 6 months' notice before retiring an API version.
5. Exceptions: Livid may make a breaking change with shorter or no notice where it is reasonably needed to address a security risk, prevent abuse, or comply with law, and will tell affected customers as soon as reasonably possible.
6. Notice: Livid will email notice of breaking changes and version retirements to the owners and admins of organizations that have used the API in the previous 90 days.

Suspension, Downgrades and Content Lock

The Short Version: If a token is being abused, we can switch it off. If you move to a plan without API access, your tokens stop working as soon as the change takes effect, so plan for your integrations before you downgrade.

1. Suspending Tokens: Livid may suspend or revoke any API token, or limit its access, if Livid reasonably believes it has been exposed, is being used in breach of these API Terms or the Terms of Service, or puts the Services or other customers at risk. Where it is safe to do so, Livid will tell your organization's owners and admins.
2. Downgrades: If your organization moves to a plan that does not include API access, your API tokens stop working when the change takes effect.
3. Content Lock: While your account is in a Content Lock state under the Terms of Service, calls that would add content may be refused. Calls that read your content remain available, so you can export it during the grace period.
4. Termination: When your account is terminated, all of its API tokens stop working immediately.

General

1. No Uptime Guarantee: The API is provided "as is" and "as available" under the Limitation of Liability section of the Terms of Service. Unless you have a separate written agreement with Livid that says otherwise, Livid does not guarantee any level of API availability or performance.
2. Feedback: If you send Livid suggestions about the API, Livid may use them without any obligation to you.
3. Changes to These API Terms: Livid may update these API Terms under the Changes to These Terms section of the Terms of Service. Changes to the commitments in Changes to the API will not shorten any notice period already given.
4. Contact: Questions about the API or these API Terms can be sent to support@livid.com.

Last Updated: 20th Oct 2026