Developer documentation for Clover

Our developer documentation provides API reference specifications as well as detailed tutorials, examples, and recipes, and release notes.

Release notes

• What's new—Monthly updates about new features and updates across the Clover developer platform.
• Bug fixes—Monthly updates on the latest bug fixes across our developer platform.
• API Changelog—Monthly updates related to API changes.
• Announcements—Messages that are sent in the Developer Communications emails are usually added to our announcements page as well. If you miss an email, check our Announcements.

Key Tutorials

• Build with Android
• Build with REST API, OAuth flows in Clover
• Build with Ecommerce API
• Integrate Clover Payment extensions for Ecommerce
• Connect your POS app to a Clover device using REST Pay Display API

Documentation features

• Style conventions—Standard text format and notational conventions in developer documents help to understand and emphasize essential information. Learn about our style conventions.
• Region icons—Clover is expanding into International markets and regions across North America, Europe, and Latin America. Learn more about Region-specific features and limitations and use the regions icons on relevant topic pages help you identify if a topic is relevant for your region.
• Recipes—Recipes provide response details and are a great option if you don't have an OAuth token.
  See the Learn how sections of the Manage orders data topic to tour working examples of common use cases. Explore more recipes.

Send documentation feedback

We in the Clover Technical Publications team value your opinions and ideas. We continuously work to improve our documentation and maintain its accuracy. If you find an issue, let us know. If you have an idea for an improvement, we want to hear it.

To send us your questions and suggestions, click the Yes 👍 or No 👎 icon at the end of any topic page and then enter your comments in the text box. Click Vote to submit your feedback.

If you want us to get back in touch with you, include your email address with your comments.

📘

NOTE

We review documentation feedback bi-weekly and put all requests in a queue that is managed and prioritized along with product updates. We'll only use your email address to contact you if we need to discuss your feedback.