---
title: API terms
description: Terms for building against the FlickList API, covering fair use, branding, and credentials.
section: Reference & policies
order: 4
---

# API terms

These terms cover apps and services built against the FlickList API (`/v3` and the device-code auth endpoints). They sit alongside, not instead of, FlickList's general [Terms of Service](/terms). Using an API key or building a device-code integration means you agree to both.

## Fair use

- The catalog is for powering your app's own requests, not for scraping or bulk-mirroring FlickList's database into a copy of your own.
- Cache sensibly. If your app fetches the same title repeatedly, store the result locally instead of re-requesting it on every screen load.
- API keys are limited to 1,000 requests per hour by default as a fair-use ceiling (see [Rate limits](/dev/rate-limits)). Design your integration to back off on a `429` response rather than retry immediately.

## Naming and branding

- Your app can say it is powered by or built on FlickList. It cannot present itself as FlickList itself, or imply an official partnership or endorsement that does not exist.
- Do not use FlickList's name, logo, or branding in a way that would reasonably confuse someone into thinking they are using FlickList's own app or website.

## Credentials

- API keys and device-code client registrations are issued to you, are not transferable, and are tied to your developer account.
- We may revoke a key or a registered app's access if it is abusing the API, violating these terms, or putting other users' data at risk.
- Any FlickList user can revoke your app's access to their account at any time, from their own Connected Apps settings, without needing to contact you or us first. Build your app to handle that gracefully.

## Our promise

We do not cap how many third-party apps a free FlickList account can connect, and we are not planning to start. That commitment is part of why these terms exist: it only works if the apps connecting stay good citizens of the API, with reasonable request volume, honest branding, and respect for a user's right to disconnect.

These terms will expand as the FlickList developer platform grows.