You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9bc2a00
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: projects/developer/src/lib/guides/create-an-app.md
+39Lines changed: 39 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,3 +23,42 @@ By creating an app, you agree to the following terms:
23
23
* Use only **documented API methods** and please don't scrape the website for information.
24
24
* Please don't create additional API apps to avoid rate limits or other API restrictions we put in place.
25
25
* Be a good API developer and remember the API is shared by a lot of apps. Make sure to effectively cache data and keep your API hits as low as you can. Optimized API usage helps everyone!
26
+
27
+
## Going to production
28
+
29
+
Every app starts as a **Development** app: you and up to 16 people you invite
30
+
can sign in, and any redirect URI works for testing, including localhost,
31
+
hosted test sites and custom app schemes. Apps for yourself or a few people
32
+
stay on Development.
33
+
34
+
When your app is ready for everyone, open it from [My Apps](/apps) and choose
35
+
**Request Production access**. Premium developers see **Create Production app**
36
+
instead. Once access is granted, you get a separate **Production app** with its
37
+
own Client ID, and your Development app stays your sandbox.
38
+
39
+
Have these ready before you start:
40
+
41
+
* A short description of what your app does and who it's for (100 to 500 characters).
42
+
* At least one link to your app: repository, docs, store page, TestFlight or website.
43
+
* A link to your privacy policy.
44
+
* At least one link showing the notice "*Your app* uses Trakt but is not endorsed or certified by Trakt". A page, a README, or a screenshot or video you host is fine.
45
+
* How many monthly active users you expect, how your app uses Trakt, and which other services it relies on.
46
+
* For apps that sign users in with PKCE, your production redirect URIs: `https://` on a domain you control. Production apps don't accept localhost or custom app schemes; on mobile, use Universal Links or verified App Links.
47
+
48
+
Apps that only read public data (trending, search, ratings) get **read-only**
49
+
Production access: they use their own Client ID and nobody can sign in to
50
+
them. To let users sign in later, request another review.
51
+
52
+
Apps get no Client Secret by default. If your server exchanges and refreshes
53
+
tokens itself, ask for one in the same form and tell us why.
54
+
55
+
Standard developers wait for a review, usually within a few business days.
56
+
Premium developers get their Production app right away, and later changes to
57
+
your app information apply right away too. A Client Secret is always reviewed:
58
+
the request waits until we grant it. Nothing changes until a review is
59
+
granted, and a declined review leaves your apps as they were.
60
+
61
+
Granting Production access is not a review, endorsement or certification of
62
+
your app or how you use it. You stay responsible for following the
63
+
[API Use Policy](/docs/api-use-policy) and the law, and Trakt can remove access
0 commit comments