Terms of Service and Attribution Guidelines
Terms of Service
Thanks for using the Patch News API (“Patch API”). By using the Patch API, you agree to these terms and you agree and understand that these terms and the Patch API service may be modified by Patch at any time without prior notice. Patch reserves the right to change, suspend, or discontinue any aspect of the Patch API and reserves the right to charge a fee for the API in the future. You can always find the latest version of these terms at http://developers.patch.in/tos. By agreeing to these terms, you also agree to comply with Patch’s General Terms of Service, which can be found here: http://patch.com/terms.
Your license to the Patch API under these terms continues until it is terminated by either party. Patch may terminate the license at any time for any reason. Your rights will be terminated immediately if (i) you violate any of the terms contained herein, (ii) Patch posts a notice of termination on the Patch website, (iii) Patch sends a written notice of termination to you, or (iv) Patch disables your access to the Patch API.
1.1 For any content obtained through the Patch API, you must:
(a) Link story headlines directly back to the original story or article page without the use of interstitials, pop-ups, follow-frames, or similar mechanisms resulting from clicks on the links;
(b) Display the name of the source that originally published each story;(c) Link the source name back to source permalink URL.
1.2 You must remove from your application and/or site any content acquired via the Patch API that Patch asks you to remove for any reason within 24 hours of being contacted by Patch.
2.1 For any content obtained through the Patch API:
(a) You will not create article pages with a single story headline and summary (i.e., “permalink pages”);
(b) You will not visit the permalink of a story, scrape the content, and repost it in its entirety;(c) You will not remove the Patch/Outside.in redirect from your links to stories or sources.
2.2 You will not use the API for any applications or websites that constitute, promote, or are used in connection with spyware, adware, or other malicious programs or code; or in any manner that violate any law or regulation; or in a manner that adversely impacts Patch.
2.3 You will not be involved in reselling, leasing, or sub-licensing content obtained from the Patch API to a third party.
3.1 You may not exceed 5,000 queries per day or 4 queries per second. If your application requires higher rate limits, please contact firstname.lastname@example.org.
3.2 If you exceed the query limitations, Patch has the right to terminate access to the API.
4.1 You must show the current Patch logo and link back to the Patch website (homepage or region-specific page), unless specific permission to do otherwise is secured from Patch. Options for logos and attribution text can be found here: http://developers.patch.com/tos#attribution.
4.2 Patch reserves the right to change the logo and/or attribution requirements at any time. You shall update the logo and/or attribution promptly upon request by Patch to adhere to the modified requirements.
4.3 You shall not use “Patch” or derivations thereof in the URL of your application.
4.4 You may not otherwise use the Patch logo, name, or brand, including issuing press releases and other forms of marketing, without specific written permission from Patch.
4.5 Any use of the Patch logo in your application or website shall be less prominent than the logo or mark that primarily describes the application or website. Your use of the Patch logo shall not imply any endorsement by Patch.
5. Disclaimer of Warranty
PATCH DOES NOT REPRESENT OR WARRANT THAT ANY API IS FREE OF INACCURACIES, ERRORS, BUGS, OR INTERRUPTIONS, OR IS RELIABLE, ACCURATE, COMPLETE, OR OTHERWISE VALID. THE PATCH API IS PROVIDED "AS IS" WITH NO WARRANTY, EXPRESS OR IMPLIED, OF ANY KIND, AND PATCH EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES AND CONDITIONS, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AVAILABILITY, SECURITY, TITLE AND/OR NON-INFRINGEMENT. YOUR USE OF THE OUTSIDE.IN API IS AT YOUR OWN DISCRETION AND RISK, AND YOU WILL BE SOLELY RESPONSIBLE FOR ANY DAMAGE THAT RESULTS FROM THE USE OF THE PATCH API INCLUDING, BUT NOT LIMITED TO, ANY DAMAGE TO YOUR COMPUTER SYSTEM OR LOSS OF DATA.
6. Limitation of Liability
PATCH SHALL NOT, UNDER ANY CIRCUMSTANCES, BE LIABLE TO YOU FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH USE OF THE PATCH API, WHETHER BASED ON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE, PRODUCT LIABILITY OR OTHERWISE), OR ANY OTHER PECUNIARY LOSS, WHETHER OR NOT PATCH HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. UNDER NO CIRCUMSTANCES SHALL OUTSIDE.IN BE LIABLE TO YOU FOR ANY AMOUNT.
You agree to hold harmless and indemnify Patch and its subsidiaries, affiliates, officers, agents, licensors, or other partners, and employees from and against any third party claim arising from or in any way related to your use of the Patch API, including any liability or expense arising from all claims, losses, damages (actual and/or consequential), lawsuits, judgments, litigation costs and attorneys' fees. Our API Terms of Service require that any applications or sites using the API display the Patch logo and link back to our website at http://patch.com. This page contains guidelines and assets to help you attribute API content to Patch: http://developers.patch.com/tos#attribution.
LogosYou must include the Patch logo and the words “Powered by Patch” set in Helvetica. Anywhere you show a Patch logo and the words “Powered by Patch,” they must be less prominent than the main logo or mark that describes the website or application using our API, and should always link to our homepage: http://patch.com.
You may download an EPS file of our logo that you can resize to suit your application, or you may use one of the following pre-formated images:
If your application or site has special attribution needs that do not fit these standard guidelines, please contact us at email@example.com. We'd be happy to work out mutually agreeable attribution requirements for you!