House rules
What apps built on put.io should and should not do.
Please
- Sign people in with OAuth or a device link.
- Call it "Something for put.io" and say put.io did not make it.
- Say in your privacy policy what your app sends to your own servers.
- Keep your app's contact email current.
- Wait for the reset time when you get a 429.
Please don't
- Ask anyone for their put.io password.
- Ship a client secret in an app people install.
- Use the put.io logo.
- Add transfers from an iOS app.
- Poll in a tight loop.
- Rebuild settings, plans or billing. Link to put.io instead.
- Share accounts or run a public library of files.
Paid apps
You can charge for your app. You need no agreement with us, as long as each person signs in with their own put.io account.
put.io is small and niche, so expect a modest audience. The people who use it love it, and a good app gets noticed.
App Store
Apple rejects iOS apps that add transfers. Apps that hid the feature were removed months later, and one took our own apps down with it.
If App Review asks for proof that you may use put.io, ask us in the support chat. We will send a short letter.
App IDs
One app ID serves every copy of your app, device link included. Keep the ID you developed with when you ship.
Rate limits
We do not publish the limits. A 429 response carries X-RateLimit-Reset: wait until then before you try again.
Getting listed
Once your app has about 10 weekly users, it shows up on the extensions page, where people look for apps.