Integrating Rain POS
In Rain POS system, there three systems available for working with API as follows:- MOCK: https://vendor-api.rainpos.com/mock
- STAGE: https://vendor-api.rainpos.com/stage
- PROD: https://vendor-api.rainpos.com/prod
Through PostMan the Key will be “x-api-key” and value should hold the Rain POS API Key.
There are the following API present in Rain POS:
Customer
get/authorizedCustomersLow Inventory
get/lowInventory/{customerToken}Purchase Order
post/purchaseOrder (Adds a Purchase Order to a Customer) put/purchaseOrder (Updates a Purchase Order already added) delete/purchaseOrder (Deletes a purchase order) post/shippingNotice (Adds a Shipping Notice to a Purchase Order)WEBHOOK
GET/webhook POST/webhook PUT/webhook/{name} DELETE/webhook/{name} The above mentioned APIs are present by default and it’s really very easy to do any integration operation to RAIN POS system to Add/Update/get/delete data. Even though there are many default API present in Rain POS by default but there are some limitations in other sections of data synchronization, like, you can’t Add/Update catalog details to Rain Pos system through API. To send the Catalog details, you have to submit the products file to a specified FTP folder by Rain POS team and it might cost you extra. At the conclusion, I would say it is a solution that handles the point-of-sale, inventory management, CRM, customer marketing, website, e-com, rental mgt, repair mgt, etc for the retailers, in an easy to use the web-based platform through integration.
You may also like:
Webinar: B2B Content Marketing – The Most Stunning Tips and Tricks
How to Start a Dropshipping Business with Shopify – Ultimate Guide Frequently Asked Questions
Yes. Rain offers a vendor API across mock, stage and production environments, authenticated with an x-api-key header. It covers authorized customers, low inventory, purchase orders, shipping notices and webhooks.
No. Catalog data cannot be created or updated through the Rain API. Product files are submitted to an FTP folder provisioned by the Rain team, and Rain has indicated that process may carry an additional cost.
Rain publishes native integrations for both, and lists them on specific plans rather than across the board. Check your plan before you assume either one is available.
There is no native ERP connector. You either build against the Rain API and the catalog file process yourself, or you use an integration platform that already has a connector for your ERP.
Transactional data can move in near real time using webhooks. Catalog data cannot, because it travels through scheduled file drops. Most Rain integrations end up part event driven and part batched for that reason.
An API key for the environment you are working in, the store base URL, a store ID for each location, and user or technician IDs if the integration touches work orders.


