DailyStory (the “Service”) has open APIs that are documented at https://dev.dailystory.com/. The APIs make it possible for developers to better use the Services and build integrations that help other people use the Services in new ways (each an “Integration”). We provide these APIs to allow people to build on and benefit from DailyStory. At the same time, we have to protect our system, as well as our users’ rights. That’s why this API Use Policy (the “Policy”) exists. Your use of the APIs must comply with both this Policy and our Terms of Service.
You’ll only access the API using OAuth or an API key. If you have an Integration, then users must have the option to log in via OAuth or using their API key. You won’t prompt users to provide their DailyStory username, password, or security questions.
2. Spam and Abuse
You won’t use the API to send spam or, if you’re using DailyStory’s API, take any actions that violate our Acceptable Use Policy. You’ll follow all documentation we provide for the APIs. You won’t attempt to hack or change the way the Services function. We may throttle your use of the APIs at any time. We may monitor your use of the APIs for compliance with these rules, and we may deny You access to the API or shut down your Integration if you try to go around or exceed the limitations we set.
We own all worldwide rights, titles, and interest in the Services and the APIs, including all intellectual property rights, marks, code, and features. You won’t infringe or copy our code, design, or content. Any rights not expressly granted by this policy are withheld, so if you don’t see it here, then it’s not a right we’re giving you. You own all worldwide rights, titles, and interest in the Integration, except for the APIs, our marks, and the Services, including all intellectual property rights. If you give us comments about the APIs or the Services, we may copy, modify, create derivative works, display, disclose, distribute, and use that feedback without any obligation to compensate you.
5. Use of Marks
You may only use our name and marks (meaning our logos and copyrighted images) according to our Brand Guidelines. You may not alter or remove any proprietary notices in our marks. You won’t use our name or marks in your Integration name or logo, or in any way that implies an endorsement by us. If you use our marks to create your logo or name, you’ll immediately assign those rights to us at no expense.
6. Representations and Warranties
You represent and warrant that you’ll maintain all the licenses required for your Integration, and that your Integration won’t violate any law or regulations in any way.
To the maximum extent permitted by law, We provide the APIs as-is. That means we don’t provide warranties of any kind, either express or implied, including but not limited to merchantability and fitness for a particular purpose.
We may update or modify the APIs and this Policy from time to time by posting the changes on this site or notifying you via email. These changes may affect your use of the APIs or the way your Integration interacts with the API. If we make a change that’s unacceptable to you, you should stop using the APIs. Continued use of the APIs means you accept the change.
You may have access to confidential, proprietary, and non-public information specific to the APIs (“Confidential Information”). You may use this information only to use and build with the APIs. You won’t disclose the Confidential Information to anyone without our written consent, and you’ll protect the Confidential Information from unauthorized use and disclosure in the same way you’d protect your own confidential information.
You’ll indemnify and hold us and our Team harmless from any losses (including attorney fees) that result from third-party claims that relate to your use of the API.
11. The Rest
This policy is part of our Terms of Service. This policy doesn’t create or imply any partnership, agency, or joint venture.
Thanks for taking the time to read our API Use Policy. People like you are why we have an API in the first place.
Updated February 2017