API Use Policy

CellarPass (“Services”) have open APIs that you can access (referred hereinto as “APIs”). 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 have designed these APIs to allow developers to build on and benefit from CellarPass platform. At the same time, since our platform has a sole purpose to maintain viability and peak performance for our guests and destination partners, we have policies and systems in place that are design to protect our system, as well as our end users’ rights. Anyone accessing our APIs will have to agree to our API Use Policy (the “Policy”) and your use of the APIs must comply with both this API Policy and our Standard Terms of Use.

1. Authorization

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 CellarPass personal User username, password, or answer additional security questions. If you do not submit a request for approval to go-live within six (6) months of receiving your provisional API access, your API access will be terminated. Furthermore, my granting you access to our Content or APIs, you cannot sublet or re-assign your access to any other company without our prior written consent.

2. Ownership

We maintain ownership, rights, titles and interest in the Services and the APIs, including all intellectual property rights, marks, code and features. When granting access and the use of our APIs, you agree that you will not infringe or attempt to copy our code, design, or content. Any rights not expressly granted by this policy are withheld. If it’s not stated here, you have no rights. When it comes to the code you write to access our APIs, we agree that 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. Should you provide feedback to help improve our APIs or the Services, we may copy, modify, create derivative works, display, disclose, distribute and use that feedback without any obligation to compensate you or provide any ownership, credit or attribution of the work.

3. Use of Trademarks

You may only use our name and marks (meaning our logos, icons and copyrighted images) in full, according to our company’s brand guidelines. You may not alter or remove any proprietary notices in our marks such as our copyright symbol or abbreviate our company’s name or logotype. You further agree that you will not use our name or our company’s marks in your integration name or logo, or in any way that implies an endorsement by CellarPass (that includes putting your logo on the CellarPass “fox’ logo). If you use our marks to create your logo or name, you’ll immediately assign those rights to us at no expense.

4. 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 international law or regulations in any way including copyright infringement or claiming someone’s else’s work as your own.

5. Disclaimer

To the maximum extent permitted by law, CellarPass provides the APIs as-is, which simply put, we do not provide warranties of any kind, either express or implied, including but not limited to merchant-ability and fitness for a particular purpose.

6. Updates

We strive for accuracy and elimination of errors, therefore we reserve the right to make updates or modify the APIs, including this API Policy from time to time by posting the changes our website 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 cease using the APIs until they are corrected, immediately. Should you continue to use the CellarPass APIs, you are accepting the responsibility for completing the necessary change(s) immediately to comply with the latest API technical specifications.

7. Privacy

You’ll respect the privacy of our users. Your Integration must display a privacy policy for users, detailing the information you’ll collect from them when they use the Integration.

8. Confidentiality

You may have access to confidential, proprietary, and non-public information specific to the APIs (“Confidential Information”) and our Content. You may use this information only to design, build and deploy integrations with the CellarPass APIs. You agree to never disclose the Confidential Information to anyone outside of your organization without our prior written consent. You further agree to protect the Confidential Information from unauthorized use and disclosure in the same way you’d protect your own intellectual property. 

9. Indemnification

You agree to indemnify and hold us and our Company harmless from any losses (including attorney fees) that result from third-party claims that relate to your proper use or misuse of the CellarPass APIs.

10. No Exclusivity or Implied Partnership

This policy is part of our Standard Terms of Use for our Services. This policy doesn’t create or imply any partnership, exclusivity, agency, or joint venture.

11. CellarPass Attribution

CellarPass provides access to our APIs and all associated links, available to interested parties in exchange for the free traffic driven to CellarPass.com. You agree to request written approval from CellarPass for any CellarPass Content that will be displayed on your website and/or app prior to launch.

You must supply links to your development or test site and/or app on which you plan to display CellarPass content in order to seek approval to publicly display is contingent upon meeting all of the CellarPass attribution requirements: All users of the CellarPass Reviews API must adhere to the ALL following display requirements:

Note: If you wish to use the image and/or assets below, they should be copied and hosted on your servers. Do not reference the images on this page directly as this may change without any prior, written notice.

Requirement	Example
CellarPass must always be written as one word, no space, with a capital “C” and a capital “P”	CellarPass
The full CellarPass logo must be shown on every page that displays CellarPass Content. The logo must be positioned above, and as close as possible to the CellarPass Content. Logo can be found below and must be used without modification.
The overall CellarPass Review rating for each business must always: 1) Be shown as five gray stars with the CellarPass “fox” logo to the left of the five stars 2) Be accompanied by the text "CellarPass Reviews" 3) Shown with the number of reviews on which the rating is based next to, and to the right of, the rating stars. This number is dynamic and must be kept updated via the API. 4) Set up a clear invitation to click on the link back (e.g. underline or add 'Read more >)
You may not combine or aggregate CellarPass ratings or reviews with any other data source.	N/A
All ratings images are provided by CellarPass and served direct from a CellarPass image URL. Do not store and locally serve CellarPass logos.	N/A

References and Links back to CellarPass

Requirement	Example
A CellarPass logomust be placed on the homepage of your site indicating inclusion of CellarPass ratings. CellarPass suggests the wording "Ratings Powered by CellarPass" to be used in conjunction with the logo.
The total number of reviews is an aggregate rating displayed in your website and/or app must be linked to the business' profile page on CellarPass. A clear invitation to click must be visible. e.g. underline the number of reviews or add a 'Read more >' link. Example: "54 Reviews" must link to: https://www.cellarpass.com/profile/encore-winery

Note: If your website and/or app is available in a language other than English, all text strings noted above must be translated into the relevant language.

12. Brand Assets

This policy is part of our Standard Terms of Use for our Services. This policy doesn’t create or imply any type partnership, exclusivity, agency, or joint venture with your company or integration.

13. Spam and Abuse

You agree to follow all documentation, including guidelines and best practices that we provide with the CellarPass APIs. We will not accept any abuse or misuse of our APIs. The APIs were not designed nor furnished to send spam. You agree to take any actions against anyone within your organization that is found to violate our Acceptable Use Policy. You further agree to never attempt to hack, reverse engineer or change the way the Services were designed to function. We reserve the right to throttle your use of the APIs at any time without any prior notice. We may monitor your use of the APIs for compliance with these rules, and we reserve the right to revoke your access to the API or shut down your Integration if you try to go around or exceed the limitations we set. We reserve the right to terminate your access to the CellarPass APIs without any prior notice and for any reason.

We all don’t like to have to enforce rules, but with rules, comes order. We’d rather spend the time improving the CellarPass APIs than policing them. So please use our APIs responsibly so we can work together and build some amazing features and integrations our customers will rave about.