Reference & policies .md

FAQ

How do I get a client_id?#

There is no self-serve app registration yet. Reach out through the FlickList Discord (linked in the site footer) or the contact address on your dashboard, tell us what you are building, and we will register a client_id for you. Personal scripts do not need one: an API key works immediately.

Can I reuse my TMDB client code?#

Yes. The catalog preserves TMDB v3 response shapes exactly, and ?api_key= query authentication works the same way. Point your existing client at https://flicklist.tv/api/v3 with a FlickList key.

Is there an official SDK?#

No, and that is deliberate for now. The API follows two shapes (TMDB, Trakt) that existing libraries already speak, and the OpenAPI spec generates typed clients for any language you want.

Why did scrobble return 400 for my item?#

Scrobbling and playback progress require the item to resolve to a TMDB-linked catalog entry. Items known only by other ids cannot be scrobbled yet. Other write endpoints accept any resolvable item; see The ids object.

How do I know when something changed on the account?#

Poll GET /v3/sync/last_activities and compare per-domain timestamps. Only re-fetch a collection whose timestamp moved. Polling full collections on a timer is the one pattern that will get an app noticed by our fair-use review.

What happens if two catalog entries get merged?#

The fldb id follows the merge: the surviving item keeps answering for old fldb values, and an item's fldb is never reassigned to something else. Cache by fldb and merges are invisible to you.

Does unmarking history delete anything?#

No. Unmarking hides the event from reads; account data is not deleted by API writes.

My rate limit feels tight for a real workload. Can it change?#

Ask us, with a sentence about what the app does and its request pattern. The published ceiling is a fair-use default, not a sales lever; genuine workloads get worked with, per our commitments.