Repository navigation
🛠️ Building with Trakt: better tools and clearer API guidance #943
Replies: 4 comments 1 reply
|
I get this from a business perspective 100%, but you must see your recent changes is what has driven the sudden defect from Trakt that has allowed the competition to capitalise on that, and also, now advancement in AI allows AI to build an equivalent in a few hours. Self realisation must be on the agenda. |
ok super, but when it will be possible to create thouse apps, because for now I see only: "Tworzenie nowych aplikacji wymaga Trakt VIP" - which means you need vip account, and no buttons to create app (yes I have free account). Better step, but please give us some dates (no rush, but some concrete dates are better then general phrases) |
|
Hello Trakt Team, I'm developing Gamose (https://gamose.com/), an independent entertainment discovery and personal tracking platform for iOS, Android, and the web, currently in early development. Gamose will support movies, TV shows, and video games. Users will have their own Gamose accounts, personal libraries, watchlists, ratings, and viewing progress. We recently registered a Standard API application and successfully tested Trakt's movie and TV metadata, artwork, cast information, translations, filmographies, and episode schedules. Before proceeding further, I would like to clarify whether our intended use complies with your API policy, particularly your statement about competing platforms. Our planned integration would:
My main question is: Would an independent application like Gamose be considered a prohibited competing platform under your policy, even if we only use Trakt as a metadata provider and do not replicate its entire catalog? If this model is permitted, would the free Standard API and read-only Production access be suitable? We would also appreciate clarification on any additional requirements regarding commercial artwork usage and caching. We want to respect your policies and obtain clear guidance before committing further development resources. Thank you for your time and for supporting developers. Best regards, |
|
Thank you for your response and suggestion! We have already reviewed the API Use Policy. As stated in the policy, Premium provides higher rate limits and additional endpoint access, but does not permit otherwise prohibited use cases. Our main concern is not API limits, but whether our independent application model is permitted. @kevincador, could you please clarify whether Gamose can use the free Standard API solely as a movie and TV metadata provider while maintaining its own independent user accounts, libraries, ratings, and tracking system? We would not bulk-download, mirror, resell, or redistribute Trakt's catalog. We have also contacted the Trakt support team by email and would greatly appreciate your clarification. Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
If you’re building an app, a media player integration, or a personal script around Trakt, we want to make it easier for you to get started. That’s why we’re rebuilding our developer tools from the ground up and clarifying the kinds of integrations the API is here to support.
📚 A better starting point
We’ve built a new developer portal at developer.trakt.tv to bring our guides, the API reference, and an interactive playground into one place maintained by Trakt. You can look up how an endpoint works and try a request without switching between separate tools. The reference is still generated from the API’s definitions to help keep it up to date.
Whether you’re making your first request or maintaining an existing integration, give it a try. Let us know where an example is missing or an explanation leaves you guessing.
We’ll be adding more developer and API-focused features to the portal soon, so stay tuned.
🔗 More room for Community Apps
Free accounts can now connect two Community Apps, up from one. Official Trakt apps don’t count toward that limit.
That gives free users another connection to use with the tools you build. Users can review and manage their connections in Connected Apps.
🔌 What we want to see more—and less—of
Trakt is better when you can use it through the apps and tools that suit you. We welcome tracking apps, media players, and personal scripts that help you get more out of your Trakt account.
What we don’t support is another service using Trakt’s data and resources to build a competing platform. Protecting those shared resources helps keep Trakt available for the community that supports it.
We’re making this distinction clearer in our API guidance. Developers can read the draft proposal and share questions while it’s under review.
Tell us what you’re building and what would make working with Trakt easier. Your feedback can help improve both the tools and the guidance.
🍿 The Trakt Team
All reactions