Terms of API use · Scanimart Developers

1. About these terms

In short: this is the agreement between your business and Scanimart for using Scanimart Connect.

1.1 Parties. These terms are an agreement between Snappikart Techlabs Private Limited, with its registered office at Manju Kunj, Ranchi, Jharkhand 834001, India and operations in Noida, Uttar Pradesh ("Scanimart", "we", "us", "our"), and the business that opens a Scanimart Connect developer account to connect its point-of-sale, billing, ERP or inventory software ("you", "your").

1.2 Acceptance. You accept these terms for your business when a person ticks the acceptance box on the sign-up form and creates your Developer Account. We record the date and time, and the version of these terms accepted. By doing so, that person confirms that they are at least 18 years old and authorised to bind your business. The business bound is the one named at sign-up. When you give your business's legal name (clause 5.2), you confirm that it is the business that accepted these terms. Keep it accurate.

1.3 Earlier accounts. If your Developer Account was opened before these terms were published at developers.scanimart.com/terms, and so could not accept them at sign-up, we will send these terms to your Owner, Admins and contact e-mail. They apply to you if you keep using the Service 30 days after that notice. If you do not agree, stop using the Service and close your account under clause 20.1 before then. Any written agreement about the Service that you and Scanimart signed before these terms applied to you continues to prevail where it conflicts with them, until it ends.

1.4 Headings and summaries. Each section starts with a one-line summary in italics. Headings and summaries are a reading aid only. They are not part of these terms and do not change their meaning.

1.5 Other documents. Scanimart's Privacy Policy (https://scanimart.com/privacy) explains how Scanimart handles personal data in its customer, retailer and staff apps; clause 8.10 explains how we handle your team's data. Scanimart's Terms & Conditions (https://scanimart.com/terms) govern how Retailers and Customers use the Scanimart Platform; they do not apply to your use of the Service. These terms do not change any agreement that you or Scanimart has with a Retailer.

1.6 Contact. Write to developers@scanimart.com about the API or these terms. Section 29 lists every contact, including for security reports and grievances.

2. Definitions and interpretation

In short: capitalised words have the meanings given here, or where the clause noted below defines them.

2.1 In these terms:

API means the Scanimart Connect API, live at https://api.scanimart.com and in the Sandbox at https://sandbox.api.scanimart.com, including Webhooks and the events feed.
Applicable Law means any law, rule, regulation or binding direction in India that applies to the party or activity concerned.
Connected Store means a Store that has connected to you with a Connection Code (or, in the Sandbox, the test store we connect for you) and has not since been disconnected.
Connection Code means the single-use code a Store generates through the Scanimart Platform to connect a developer.
Customer means an individual who buys from a Store through the Scanimart Platform.
Customer Data means Scanimart Data about a Customer or a Customer's Order, purchase, payment or cancellation, whether or not it identifies the Customer.
Dashboard means the developer dashboard at developers.scanimart.com.
Developer Account means your account for the Service, including its Team Members, Keys, webhook endpoints and Store connections.
Documentation means the guides, API reference and other material we publish at developers.scanimart.com, as updated from time to time (subject to clause 28.2), but not the code that section 15 covers.
Event means a record of something that happened at a Connected Store, sent by Webhook or listed in the events feed.
Key means a secret API key we issue to you: a Live Key (sk_live_…) for live use, or a Test Key (sk_test_…) for the Sandbox. A Key normally covers all your Connected Stores. A Store-scoped Key reaches only one Connected Store, and cannot claim Connection Codes, manage webhook endpoints or retry Webhook deliveries (see clause 4.3).
Live Access means permission to use Live Keys with real Stores, Customers and Orders.
Order means an order a Customer places with a Store through the Scanimart Platform.
Retailer means the business that owns or runs a Store, and the people it authorises to act for it.
Sale means a delivered delivery Order, or a paid in-store Scan & Go basket.
Sandbox means the API's test environment, with test stores and simulated orders.
Scanimart Data means all data you receive through the Service, including Store details, Orders, Sales, Events, Customer Data, courier and rider details and Webhook contents, but not Your Data.
Scanimart Platform means the apps and services through which Scanimart lets Customers buy from Stores and lets Retailers run their Stores, including the Scanimart customer, retailer and staff apps. It does not include the Service.
Service means the API, Sandbox, Dashboard, Webhooks and Documentation, and related services we provide to developers. It does not include the SDKs or the other code that section 15 covers.
Signing Secret means the secret (whsec_…) used to sign the Webhooks sent to one of your endpoints.
Store means a retail store that sells through the Scanimart Platform. Where these terms say that a Store decides, instructs, agrees, connects, disconnects, has rights or duties, or is told something, they mean the Retailer that runs it, acting through its owner or the people it authorises.
Store Agreement means your agreement with a Retailer covering your use of the Service for its Store or Stores and your processing of their data (see clauses 6.3 and 8.3).
Team Member means a person with a login to your Developer Account, whatever their role.
Webhook means an HTTPS request we send to an endpoint you register, telling you about an Event.
Your Application means the software you make, sell or run that uses the Service, and related services you provide to Stores.
Your Data means data you send through the Service, such as stock counts, prices, product details and decisions on Orders.

2.2 Some terms are defined where they are used: Owner and Admin (clause 3.2), Security Incident (clause 9.2), Breaking Change (clause 12.2), SDKs (clause 15.1) and Confidential Information (clause 18.1).

2.3 "DPDP Act" means the Digital Personal Data Protection Act, 2023, and "IT Act" means the Information Technology Act, 2000. "Personal Data", "Data Fiduciary", "Data Processor", "Data Principal" and "personal data breach" have their DPDP Act meanings. "Including" means including without limitation. A reference to a law includes it as amended or replaced, and rules made under it. "Written" includes e-mail and other electronic records, such as terms accepted online.

3. Your Developer Account and team

In short: keep your details current. You answer for your team.

3.1 Keep your Developer Account details accurate and current. Your Owner and Admins can change your company name, legal name, GSTIN, website and contact e-mail in the Dashboard. To change something the Dashboard does not let you change, such as a Team Member's login e-mail or who your Owner is, write to developers@scanimart.com.

3.2 The person who signs up is your Owner until the Owner is changed under clause 3.1. The Owner and Admins (Team Members with the Admin role) can invite Team Members as Admin, Developer or Viewer. Each Team Member must use their own login.

3.3 You are responsible for your Team Members and for everything done through your Developer Account or under your Keys, except to the extent caused by our breach of these terms. Make sure every Team Member knows and follows these terms.

3.4 Give each person only the access they need: every role, Viewer included, can see Store details and Webhook contents. We recommend two-factor sign-in for everyone. Removing a Team Member ends their sessions, but does not revoke Keys they created or saw, or change Signing Secrets they revealed. Roll or revoke those if needed.

4. Keys and secrets

In short: keep Keys on servers you control, put only a Store-scoped Key on a store's device, and revoke a leaked Key at once.

4.1 Keys and Signing Secrets are secrets. Keep them on servers you control, except as clause 4.2 allows.

4.2 Where Your Application runs on a device in a Store (such as a billing PC, POS terminal or handheld), use a Store-scoped Key for that Store only. Keep it in the operating system's protected credential storage or equivalent, never in a plain-text file or setting that store staff or other users of that device can open. Never put a Key that covers more than one Store on a device in a Store.

4.3 A Store-scoped Key reaches only its own Store: that Store's details, Orders, inventory, Sales and Events. It cannot claim Connection Codes, see or manage your webhook endpoints or their Signing Secrets, or retry Webhook deliveries; do those with a Key that covers all your Connected Stores, from servers you control. A Store-scoped Key is still a secret: whoever holds it can act for its Store, including accepting and rejecting its Orders, changing its stock and prices, and disconnecting it. Protect it under clause 4.2. If it is exposed, act at once under clause 4.5, and check that Store's recent Orders, stock and prices for actions you did not take.

4.4 Never build a Key or Signing Secret into software you distribute (such as an installer, app package or browser code). Never put one in a public code repository, a log, or an e-mail or other message to anyone, including us; quote a Key's prefix instead.

4.5 If you know or suspect that a Key or Signing Secret has been exposed, revoke the Key or roll the Signing Secret at once, and report it under clause 9.3. You may instead roll an exposed Key with no overlap period, which retires it as soon as the new Key is issued. Do not roll an exposed Key with an overlap period, because the exposed Key keeps working until the overlap ends (up to 7 days).

4.6 We may revoke any Key we reasonably believe has been exposed or misused, without notice. We will e-mail your Owner, Admins and contact e-mail promptly afterwards, naming the Key and, where we can, saying why. The Key shows as revoked in your Dashboard. Your other Keys are not affected.

5. Sandbox and Live Access

In short: test in the Sandbox from sign-up. Real stores need Live Access, granted after review.

5.1 You may use the Sandbox from sign-up to build and test Your Application. Use only test data there. We may reset, change or remove Sandbox data at any time.

5.2 To ask for Live Access:

(a) Your Application completes the go-live checklist through its Sandbox activity (the Dashboard records each item automatically);
(b) your Owner or an Admin gives your business's legal name and a contact e-mail in the Dashboard; and
(c) your Owner or an Admin requests review in the Dashboard.

We may ask for more information, such as your GSTIN.

5.3 A person at Scanimart reviews each request, including your Sandbox activity and request log. We decide, in our reasonable discretion, whether to approve it, and may waive a checklist item. If we do not approve, we tell your Owner, Admins and contact e-mail why, by e-mail, and show it in the Dashboard. Your Sandbox access continues, and you may fix what we raised and request review again. To ask us to reconsider a decision, write to developers@scanimart.com or reply to our e-mail. We do not promise a review time.

5.4 Approval means only that you met our review at that time. It is not a certification or endorsement, and you must not describe it as one.

6. Connecting Stores

In short: work only for stores that chose to connect you, on their instructions.

6.1 A Store connects you by generating a Connection Code and giving it to you. Claim a code only when the Store has asked to connect Your Application. Check that the Store named in the claim response is the one that asked you. If it is not, disconnect it at once and tell us.

6.2 Never obtain a Connection Code by deception, pressure or a misleading account of who you are. Do not guess or collect codes, use a code given to you by anyone other than the Store, or keep retrying a code that was refused. Retrying a claim whose answer you did not receive, with the same Idempotency-Key, is allowed.

6.3 You act for each Connected Store. Use the Service for it only on its instructions and under a Store Agreement. The Store Agreement must tell the Store what Your Application will do for it through the Service (for example, read its Orders, including earlier ones, accept and reject Orders, and set its stock and prices), and must cover your processing of its data as clause 8.3 requires. Your standard customer terms, accepted online or by e-mail, are enough if they cover these points. One Store Agreement with a Retailer can cover all its Stores.

6.4 Reflect each Store's decisions accurately in the Scanimart Platform, and the Scanimart Platform's information accurately to the Store. Never change, hide or delay information in a way that could mislead a Store or its Customers.

6.5 A Store may disconnect you at any time without giving a reason. Disconnect a Store yourself when your Store Agreement for it ends or it asks you to.

6.6 Once a Store is disconnected, stop using the Service for it and revoke any Store-scoped Keys for it. Webhooks for earlier Events may still arrive; you may book them into the Store's records if the Store wants that, but take no other action for it. Clause 8.9 covers its data.

6.7 Stores with more than one connection. A Store may connect more than one developer. Each receives the same Orders, Events and Sales, and only the first to accept or reject an Order succeeds. The Store decides which connected software books its Sales and pushes its stock. Following the Store's instructions on this is not a breach of these terms, even if another developer books the same Sales or pushes different counts.

7. Orders, inventory and sales

In short: what you do through the API binds the store, so act only as the store wants.

7.1 Authority. Accept, reject or change the delivery method of an Order only when the Store has decided to, either by a person at the Store or by a rule the Store set up in Your Application. Show each new Order to the Store as soon as Your Application receives it. An Order's stock is held for a limited time (currently 15 minutes, as the Documentation describes), so the Store needs to see it well within that time.

7.2 Accepting. Accepting an Order accepts it for the Store. The Customer is told through the Scanimart Platform, and the Store must then fulfil the Order. The API does not let you cancel an Order once it is accepted. An accepted Order that the Store cannot fulfil is for the Store and Scanimart to resolve, not for Your Application; tell the Store promptly if Your Application learns of such a problem.

7.3 Rejecting. Rejecting an Order cancels it and triggers a full refund to the Customer; Your Application does not issue the refund. Any reason you give is shared with the Store and with any other software the Store has connected, and may be shown to the Customer. It must be short, accurate, customer-safe and free of Personal Data.

7.4 Picking and packing. Picking and packing are recorded in the Scanimart Staff app and are not actions available through the POS API. Your Application receives progress through Webhooks. Starting picking closes the Customer's option to cancel in the Scanimart customer app. On a Scanimart courier Order, starting picking or marking the Order packed books the courier. Marking an Order packed tells the Customer, and Scanimart does not check the items.

7.5 Delivery method. The delivery method decides who delivers and the commission the Store pays Scanimart, so the Store chooses it. For each Order, Your Application must either:

(a) show the Store each option the API returns for that Order (for an available option, its commission and, for Scanimart courier, the courier's pickup ETA; for an unavailable option, the reason the API gives), and send the method the Store picks; or
(b) apply a default method that the Store chose in Your Application after seeing those options for an earlier Order. If the default is not available for an Order, ask the Store.

Use the API's current figures, never hard-coded ones. Scanimart courier delivery may not be available for every Store or Order, or at all.

7.6 Inventory. Push only stock counts, prices, MRPs, expiry dates and product details that are accurate and lawful and that the Store has set or approved. A selling price for packaged goods must not exceed their MRP. The selling price you push is what Customers pay. Push a full stock count as soon as a Store connects you, and before you accept any of its online Orders. Do not send stock adjustments for Sales; the Scanimart Platform has already taken that stock.

7.7 Product information. Product details you send for a barcode new to the Scanimart Platform may be added to Scanimart's catalogue and shown at other Stores. Send only details that are accurate and lawful and that you have the right to send.

7.8 Sales. Book each Sale into the Store's records once. Answer a sale.completed Webhook with a 2xx status, or acknowledge the Sale through the API, only after booking it. Prices are tax-inclusive and Scanimart does not split out GST, so Your Application must apply the Store's tax treatment.

7.9 Content. Product details, reasons and other text you send, which Scanimart may show to Stores or Customers, must not: belong to someone else without their permission; be obscene, defamatory, deceptive or misleading; impersonate anyone; infringe intellectual property; harm children; threaten the unity, integrity, defence, security or sovereignty of India or public order; contain malware; or otherwise break Applicable Law. We may remove or refuse such content.

8. Data protection

In short: use data only to serve the store it came from. Never sell it, market with it or profile anyone.

8.1 Law. Each party must comply with Applicable Law on data protection and information security. This includes the DPDP Act and its rules, as far as they are in force. It also includes the IT Act and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, as far as they apply.

8.2 What you receive. The API is designed not to give you Customers' names, phone numbers, e-mail addresses, delivery addresses or locations. Customer Data can still identify a person (a basket, time and Store together, or a free-text reason), so treat it all as Personal Data. Store details may include a sole proprietor's Personal Data. On Orders delivered by Scanimart courier, you receive the rider's name, phone number and vehicle details so the Store can hand the Order over.

8.3 Roles. For Personal Data in Scanimart Data that Your Application processes for a Store, you act as the Store's Data Processor, and the Store is the Data Fiduciary responsible to its Customers. Process that data only under your Store Agreement. It must meet the DPDP Act's requirements for a contract with a Data Processor once those apply, and must let you meet these terms, including clauses 8.8, 9.3 and 9.4. Scanimart is a separate Data Fiduciary for its own processing. Neither of us is the other's Data Processor.

8.4 Purpose. Use Scanimart Data only to provide Your Application to the Connected Store it came from, as that Store instructs, and to comply with these terms and Applicable Law. Providing Your Application includes supporting, securing, backing up and fixing it for that Store, and working out what to charge that Store for it. It never includes a use that clause 8.5 prohibits. This clause covers everything the API returns about a Connected Store, including any Orders from before it connected you.

8.5 Prohibited uses. You must not:

(a) sell, rent or give Scanimart Data to anyone, except your service providers under clause 8.7, or as the Store instructs or the law requires;
(b) use it for advertising or marketing, to contact Customers, or to profile or track anyone;
(c) combine data from different Stores, or with other data, to build a profile of a person or a picture of a Store's business for anyone but that Store;
(d) try to identify a Customer or re-identify anyone; or
(e) use rider details except to hand over that Order and keep the Store's records of it.

8.6 Minimisation and retention. Collect, keep and show only the Scanimart Data you need. Keep it only as long as you need it to serve the Store under clause 8.4, or longer only where the Store instructs or Applicable Law requires (for example, tax records). Then delete it securely.

8.7 Safeguards and providers. Protect Scanimart Data with reasonable security practices suited to the risk, including encryption in transit, access control and logging. Give access only to people who need it and are bound to confidentiality. Use a service provider only under a written contract at least as protective as this section; you remain responsible for it. Transfer Personal Data outside India only as Applicable Law allows.

8.8 Requests and help. Refer a Data Principal's request about Personal Data that came through the Service to the Store (and to Scanimart, if it concerns Scanimart's processing), and help the Store respond. Give Scanimart the help it reasonably needs to meet its own legal obligations, including towards the Data Protection Board of India, CERT-In and law enforcement.

8.9 After a Store leaves. When a Store disconnects you or your Store Agreement for it ends, delete or return its Scanimart Data as the Store instructs (or, if it gives no instruction, delete it), unless Applicable Law requires you to keep it. Orders and Sales already booked into the Store's records are the Store's own records; your Store Agreement governs them, and clause 8.5 still applies.

8.10 Your team's data. To run, secure and audit the Service and to meet our legal obligations, we process Team Members' Personal Data (name, work e-mail, role, sign-in activity, each session's IP address and browser, and audit-trail actions) and a log of API requests made with your Keys. Other Team Members and authorised Scanimart staff can see some of it in the Dashboard. The request log in the Dashboard keeps every failed request and a sample of successful ones for 7 days; it is not a complete record of your use. We keep the rest while your Developer Account is open, and afterwards only as long as we need it for security, legal, tax or dispute purposes or Applicable Law requires. Tell your Team Members this.

8.11 Demands from authorities. If an authority asks you for Scanimart Data, disclose only what the law requires. Where the law allows, tell the Store first, and tell Scanimart if the demand concerns Scanimart.

8.12 Compliance information. On our reasonable request, confirm in writing how you comply with sections 8 and 9, and name the service providers that hold Scanimart Data for you.

9. Security

In short: secure your systems, report incidents within 24 hours, and report vulnerabilities privately.

9.1 Use reasonable security practices, at least those in clause 8.7, to keep Your Application, and every system holding Keys, Signing Secrets or Scanimart Data, secure, patched and monitored.

9.2 A Security Incident is any actual or reasonably suspected unauthorised access to, or use, disclosure, loss or alteration of, Scanimart Data, Keys or Signing Secrets in your or your service providers' control, including a personal data breach.

9.3 Tell us of a Security Incident without undue delay, and in any case within 24 hours of becoming aware of it, by e-mail to developers@scanimart.com with the subject "Security". Say what happened, when, which Stores, Keys and data are affected, and what you are doing, and update us as you learn more.

9.4 Contain the incident, revoke affected Keys (or roll them with no overlap period) and roll affected Signing Secrets, tell affected Stores without undue delay so they can meet their own legal duties, and cooperate with us. Do not make public statements naming Scanimart without consulting us, unless the law requires. Where directions issued by CERT-In under section 70B of the IT Act require you to report the incident, do so within the time they set and tell us.

9.5 We maintain reasonable security practices for the Service. If we learn of a security incident we reasonably believe affects your Keys, Signing Secrets or Developer Account, we will tell you without undue delay, as far as the law and any investigation allow.

9.6 Security research. Report vulnerabilities in the Service to developers@scanimart.com with the subject "Security", and give us reasonable time to fix them before telling anyone else. Do not run load tests, vulnerability scans or penetration tests against the Service, Sandbox included, unless we agree in writing; to ask, write to developers@scanimart.com. Never access or keep data that is not yours, or run security tests against real Stores, Customers or payments. Ordinary integration testing with a Store that has agreed to it, as the Documentation suggests, is not security research. We will not take legal action against good-faith research that follows this clause.

10. Acceptable use

In short: use the API only for your connected stores, within its limits, and honestly.

10.1 Stay within the rate limits in the Documentation (currently counted per Key). To ask for more for a particular job, write to developers@scanimart.com; we may agree, for example, that you use additional Keys for it. We may lower a limit at once, for as long as needed, to protect the Service. A lasting reduction likely to stop a working integration gets the same notice as a Breaking Change (clause 12.2).

10.2 You must not:

(a) get around rate limits, Key scopes, the separation of Sandbox and live, or other technical limits, for example by creating Keys or accounts only to multiply a limit (one Store-scoped Key per Store, as the Documentation recommends, is allowed);
(b) access, or try to access, data about a Store that has not connected you, or another developer's data;
(c) scrape or extract data from the Service beyond what your Connected Stores need;
(d) reverse engineer or decompile the Service, except as Applicable Law allows despite this restriction;
(e) disrupt the Service, or send malware through it;
(f) misrepresent who you are, what Your Application does, or your relationship with Scanimart or a Store;
(g) use Scanimart Data to build or improve a marketplace, ordering or delivery service that competes with Scanimart. This does not stop Your Application from showing a Store's Scanimart Orders alongside its orders from other channels, or keeping that Store's stock correct across all its channels, for that Store. Nor does it limit what a Store may do with its own records, including Sales booked into them (clause 8.9);
(h) sell, resell or sublicense access to the Service, or let anyone else use your Keys or account, except your service providers under clause 8.7 (charging Stores for Your Application, including its Scanimart features, is allowed under clause 14.3 and is not selling access);
(i) use the Service for anything unlawful or fraudulent, or that harms Stores, Customers or Scanimart; or
(j) open another Developer Account to avoid a suspension, termination or limit.

11. Webhooks

In short: check every signature, answer quickly, and expect duplicates.

11.1 Register only HTTPS endpoints that you or your service provider control.

11.2 Verify the signature on every Webhook with the endpoint's Signing Secret, as the Documentation describes. Answer a Webhook whose signature or timestamp fails with a 4xx status, and do not act on it.

11.3 Answer each Webhook with a 2xx status within the time the Documentation sets (currently 10 seconds). For sale.completed, a 2xx means you have booked the Sale (clause 7.8). If Your Application cannot book a Sale within that time, either answer with a non-2xx status so the delivery is retried later, or leave sale.completed out of that endpoint's event types and instead pull Sales through the API, acknowledging each one once it is booked.

11.4 Webhooks are delivered at least once and not necessarily in order. Use the Event id so you never act on the same Event twice.

11.5 We retry a failed delivery for a limited period, as the Documentation describes (currently ten attempts over about three days). If an endpoint keeps failing (currently, continuously for three days), we switch it off and tell your Owner, Admins and contact e-mail by e-mail; deliveries still pending for it are marked failed. You can switch it back on, replay failed deliveries, and catch up on order and sale Events for your Connected Stores from the events feed, which keeps them for 30 days. Deleting an endpoint deletes its delivery history, and rolling a Signing Secret takes effect immediately.

12. API changes and versioning

In short: within a version we only add. Breaking changes get at least 90 days' notice.

12.1 Within an API version we only add new endpoints, optional request fields, response fields and event types. Error codes stay the same; messages may be reworded. Build Your Application to ignore fields and event types it does not know, and to rely on error codes, not messages.

12.2 A Breaking Change is one that would stop a correctly built integration that follows the Documentation from working, such as removing or renaming an endpoint, field or event type, changing a field's type or meaning, or making an optional field required. We make a Breaking Change only in a new API version, announced at least 90 days before it takes effect, or on shorter notice only where needed for security or to comply with Applicable Law. Until the API lets you choose a version, a new version applies to every request from its effective date, so use the notice period to update Your Application. Webhook deliveries created before that date, including their retries, keep the earlier version's shape and api_version. Every Event carries api_version, so you can see which version you are reading.

12.3 Correcting the Service so that it does what the Documentation says is not a Breaking Change, unless the Documentation was inconsistent on the point or these terms describe the behaviour being changed. We will give reasonable notice of a correction likely to affect working integrations.

12.4 We announce changes under this section by e-mail to your Owner, Admins and contact e-mail, and publish them at developers.scanimart.com. We may stop offering the API altogether on at least 90 days' notice.

13. Availability and support

In short: we work to keep the Service running, but there is no uptime guarantee, and you keep your own records.

13.1 We aim to keep the Service available, but do not promise that it will be uninterrupted, error-free or available at any particular level. There is no service level agreement. Maintenance may interrupt the Service; where we reasonably can, we will announce planned maintenance likely to cause a significant interruption.

13.2 Support is by e-mail to developers@scanimart.com. Quote the Request-Id of any request you ask about. We do not commit to response times.

13.3 The Service keeps data only for limited periods, as the Documentation describes: currently, the events feed and the sales list cover the last 30 days, Idempotency-Keys are kept for 24 hours, and the request log is kept as clause 8.10 says. It is not a record-keeping service for you. Keep your own records of what Your Application does.

14. Free of charge

In short: integrating with Scanimart is free. We charge you nothing.

14.1 The Service is free of charge to developers. Scanimart does not charge you for your Developer Account, Keys, the Sandbox, Live Access, API calls, Webhooks or connecting Stores.

14.2 What Stores pay Scanimart, including the commission on each Order (charged at the courier rate where an Order goes by Scanimart courier), is a matter between Scanimart and the Store. The API shows these amounts so the Store can decide; they are not charges to you.

14.3 You may charge Stores for Your Application as you agree with them, but must not present your charges as Scanimart's or misstate what Scanimart charges.

15. SDKs and sample code

In short: the SDKs, samples and generated clients are MIT-licensed; calling the API is still governed by these terms.

15.1 The official Scanimart Connect libraries for Node.js (@scanimart/connect on npm) and Python (scanimart-connect on PyPI) (the SDKs) are open source under the MIT License. The LICENSE file in each SDK governs its code. Packages under other names are not official.

15.2 You may use, copy, modify and share, under the MIT License, the code samples in the Documentation and the Postman collection we publish. Keep the same copyright notice as in the SDKs' LICENSE files.

15.3 You may use, modify and share client code you generate from our OpenAPI description on the same terms as the code samples.

15.4 These terms govern every call to the API, whether made through an SDK, sample code, generated code or any other client. The MIT License gives you no rights in the Service, Keys, Scanimart Data or Scanimart's trade marks.

15.5 Clauses 10.2, 16.1, 16.2 and 20.3 do not limit what the MIT License lets you do with the code this section covers. If these terms end, you may keep that code in software you have shipped, but you may no longer call the API.

16. Intellectual property

In short: you get a limited licence to use the API for your connected stores. You keep your software; we keep ours. We may use the data you send to run the Scanimart Platform, and may keep using product details you add to our catalogue.

16.1 Our licence to you. Subject to these terms, Scanimart grants you a limited, non-exclusive, non-transferable licence, while these terms are in force and subject to suspension under section 19, to use the Service and Documentation to develop, test and run Your Application and provide it to Connected Stores. You may not sublicense it, except to your service providers under clause 8.7 so they can act for you.

16.2 Ownership. Scanimart and its licensors own the Service, the Documentation and Scanimart's trade marks, and you get only the rights these terms expressly give. You own Your Application; we claim no rights in it except under clauses 16.3 and 17.3.

16.3 Your Data. You grant Scanimart a non-exclusive, royalty-free, worldwide licence to use, copy, store, adapt, display and share Your Data to run the Scanimart Platform for the Stores concerned and their Customers, and to keep the records Applicable Law requires. It lasts for as long as Scanimart needs Your Data for those purposes, including after these terms end. For product details added to Scanimart's catalogue under clause 7.7, the licence is perpetual and irrevocable and covers use for any Store. You confirm that you have the rights, including from the Store, to grant this licence.

16.4 Scanimart Data. You get no ownership of Scanimart Data and may use it only as these terms allow. Nothing in these terms limits a Store's rights in its own data.

16.5 Feedback. We may use any feedback you give us about the Service freely, without obligation to you.

17. Brand use

In short: you may say your software works with Scanimart; anything more needs our written approval.

17.1 You may state accurately that Your Application "works with Scanimart" or "integrates with Scanimart Connect", using the Scanimart name in plain text. You may also use the word "Scanimart" in plain text to label the Scanimart features inside Your Application, such as a "Scanimart orders" screen or a "Connect to Scanimart" setting.

17.2 Without our prior written approval, you must not use Scanimart's logos or other trade marks, use "Scanimart" in your company, product or domain name, or suggest that Scanimart endorses, certifies or partners with you.

17.3 While these terms are in force, you allow Scanimart to show your company name, POS product name and website to Stores in the Scanimart Platform, including to each Store you are connected to, and in lists of software that works with Scanimart. You may ask to be left out of such lists, but not out of a Connected Store's own list of its connections.

18. Confidentiality

In short: keep each other's non-public information private.

18.1 Confidential Information means non-public information one party gives the other under these terms that is marked confidential or would reasonably be seen as confidential, including Keys, Signing Secrets, security information and review feedback.

18.2 The receiving party must use it only for these terms, protect it with reasonable care, and share it only with personnel, service providers and advisers who need it and are bound by confidentiality. This does not apply to information that is public through no fault of the receiving party, already known to it, independently developed or lawfully received from someone else. A party may disclose Confidential Information where the law requires, telling the other first where lawful.

18.3 These duties continue after these terms end, for as long as the information remains confidential.

19. Suspension

In short: we can pause your access at once to protect stores, customers or security, or to obey the law; for other breaches, we first give you a chance to fix them.

19.1 We may suspend your Developer Account, revoke Keys or switch off webhook endpoints, with immediate effect, where we reasonably believe it is needed:

(a) to protect Stores, Customers, Scanimart or the Service from harm;
(b) to deal with a leaked Key or Signing Secret or a Security Incident; or
(c) to comply with Applicable Law or a direction from an authority.

19.2 For any other material breach of these terms, we will first tell you by e-mail what is wrong and give you a reasonable period to fix it. If you do not fix it in that period, we may suspend your Developer Account.

19.3 During a suspension, all your Keys, test and live, stop working, no Events are delivered to your endpoints, and deliveries already queued are marked failed. You can still sign in to the Dashboard. Your Store connections remain unless a Store disconnects you, and your obligations continue. We may tell affected Stores, so they can handle their Orders in the Scanimart Platform.

19.4 We will e-mail your Owner, Admins and contact e-mail that your Developer Account is suspended, and why, as soon as we reasonably can, unless the law or an investigation prevents us from giving the reason.

19.5 We will lift a suspension once its reason has been resolved to our reasonable satisfaction, and e-mail your Owner, Admins and contact e-mail what access it restores. Lifting it restores the access you had before the suspension, except Keys revoked during it; it never gives you Live Access you did not already have. If our records do not show what access you had, we restore Sandbox access, and you may ask us to confirm your Live Access. To ask for a review of a suspension, write to developers@scanimart.com or reply to our e-mail about it. Once it is lifted, you can replay the deliveries that were marked failed and catch up from the events feed (clause 11.5).

20. Termination

In short: either side can end these terms; access then stops and Scanimart Data is dealt with as stores and the law require.

20.1 You may end these terms at any time. Your Owner or an Admin asks us, by e-mail to developers@scanimart.com, to close your Developer Account. Before you ask, tell your Connected Stores, so they can handle their Orders in the Scanimart Platform. We will close the account promptly and confirm by e-mail to your Owner and Admins. These terms end when we close the account.

20.2 We may end these terms by notice:

(a) for any reason, giving at least 90 days' notice;
(b) immediately, if you materially breach these terms and the breach cannot be fixed or you do not fix it within the reasonable period we set;
(c) immediately, if Applicable Law or an authority requires it; or
(d) immediately, if you stop doing business or, to the extent Applicable Law allows, if an insolvency, liquidation or winding-up process begins for you.

20.3 When these terms end, we will revoke your Keys, end your Store connections and stop Webhooks, and the licence in clause 16.1 ends. You must stop using the Service, delete your Keys and Signing Secrets, deal with Scanimart Data under clause 8.9, tell your Connected Stores (if you have not already) so they can make other arrangements, and stop saying that Your Application works with Scanimart. Each Connected Store sees in its Scanimart retailer app, under Settings → POS software, that you are no longer connected. We may also tell it directly, and we will stop listing you under clause 17.3. We keep information about your Developer Account only as clause 8.10 says. Ending these terms does not affect rights and liabilities that arose before then.

20.4 Sections 8, 18, 21 to 24 and 26 to 28, clauses 9.2 to 9.4, 15.5, 16.2 to 16.5 and 20.3, and any other provision that by its nature should survive, survive the end of these terms.

21. Warranties and disclaimers

In short: beyond what these terms say, the Service comes as it is.

21.1 Each party confirms that it has the power and authority to enter into these terms.

21.2 You confirm that the information you give us is accurate; that you will comply with Applicable Law; that you have, and will keep, a Store Agreement and the authority you need for each Connected Store; and that Your Application and Your Data do not infringe anyone's rights.

21.3 Except as these terms expressly say, the Service is provided "as is" and "as available". To the extent the law allows, Scanimart gives no other warranty, express or implied, including of quality, fitness for purpose, accuracy or non-infringement.

21.4 Much data in the Service comes from Stores, Customers, couriers and other third parties, and Scanimart does not warrant its accuracy. Courier tracking pages are run by third parties, and Scanimart does not control their content.

22. Limitation of liability

In short: no liability for indirect losses; other liability is capped at INR 10,000, except in the cases in clause 22.3.

22.1 Neither party is liable to the other for any indirect, special, incidental or consequential loss, or for loss of profit, revenue, business, goodwill or data, arising out of or in connection with these terms, even if foreseeable.

22.2 Each party's total liability for all claims arising out of or in connection with these terms, whether in contract, tort (including negligence) or otherwise, is limited in aggregate to INR 10,000.

22.3 Clauses 22.1 and 22.2 do not limit:

(a) your obligations under section 23 (Indemnity);
(b) your liability for breach of section 8 (Data protection), clauses 9.1 to 9.4 (security and Security Incidents) or section 18 (Confidentiality);
(c) either party's liability for fraud or wilful misconduct; or
(d) any liability that Applicable Law does not allow to be limited.

22.4 Scanimart is not liable for loss to the extent it is caused by what Your Application does or fails to do, by a Store, Customer or courier, or by your failure to follow these terms, including the Documentation instructions they point to.

23. Indemnity

In short: if your breach, a fault in your software or your handling of data causes a claim against Scanimart, you cover it.

23.1 You will defend Scanimart and its directors and employees against any third-party claim (including by a Store, Customer, rider or authority), and indemnify them against the resulting losses, damages, costs, reasonable legal fees and, to the extent the law allows, penalties, to the extent the claim arises from:

(a) your breach of these terms or Applicable Law;
(b) a defect in Your Application, or Your Application doing something through the Service that the Store did not instruct;
(c) your processing of Scanimart Data, or a Security Incident;
(d) Your Data infringing anyone's rights; or
(e) a dispute between you and a Store.

23.2 This does not apply to the extent the claim is caused by Scanimart's breach of these terms, negligence or wilful misconduct, or by a Store's own decision that Your Application carried out as instructed.

23.3 Scanimart will tell you of a claim promptly. Except for a claim or proceeding by an authority, Scanimart will let you control its defence with counsel reasonably acceptable to Scanimart, and will help at your cost. Scanimart controls its own dealings with any authority, consulting you where it reasonably can, and you will reimburse its reasonable costs of them. You must not settle a claim in a way that admits fault for Scanimart or places obligations on it without its written consent.

24. Force majeure

In short: no one is liable for events truly beyond their control, but your security duties never pause.

24.1 Neither party is liable for delay or failure caused by events beyond its reasonable control, such as natural disasters, epidemics, war, civil unrest, government action, power or internet failures, failures of third-party hosting, payment or courier providers, or cyber-attacks despite reasonable safeguards. The affected party must tell the other promptly and limit the effect as far as it reasonably can.

24.2 This section does not excuse your obligations to protect Keys, Signing Secrets and Scanimart Data with reasonable security practices, or to report and handle Security Incidents under clauses 9.3 and 9.4.

25. Changes to these terms

In short: we give 30 days' notice of changes; using the Service afterwards means you accept them.

25.1 We may change these terms by giving at least 30 days' notice by e-mail to your Owner, Admins and contact e-mail, and by publishing the new version, with its version number and effective date, at developers.scanimart.com/terms.

25.2 A change required by Applicable Law, or needed for security, may take effect immediately. We will tell you about it as soon as we can.

25.3 If you keep using the Service after a change takes effect, your business accepts the new version. If you do not agree, stop using the Service and close your Developer Account under clause 20.1 before then.

25.4 We keep every version of these terms we publish, and will send you an earlier version on request. The version your business accepted at sign-up is recorded with its acceptance (clause 1.2).

25.5 A change does not shorten the notice for Breaking Changes in clause 12.2, and does not apply to a dispute or claim that arose before the change took effect.

25.6 Changes to these terms:

Version 1.0, effective 10 October 2026: first published version.

26. Notices

In short: legal notices to us go by e-mail and post; we write to your account's e-mail addresses.

26.1 Legal notices to Scanimart, such as a notice of breach, claim or dispute, must be sent both by e-mail to developers@scanimart.com and by post to Scanimart's registered office in clause 1.1. A request to close your Developer Account under clause 20.1 needs only an e-mail. Other communications go by e-mail to developers@scanimart.com.

26.2 We send notices to you by e-mail to your Developer Account's contact e-mail and its Owner and Admins. Notices for all developers may also be published at developers.scanimart.com. A reply to an e-mail we send you about the Service counts as an e-mail to developers@scanimart.com under clause 26.1.

26.3 An e-mail notice is given when sent, unless the sender is told it was not delivered. A notice by post is given when delivered. A notice that must go by both is given when both have been given.

27. Governing law and disputes

In short: Indian law applies; we negotiate first, then arbitrate in Ranchi.

27.1 These terms, and any dispute arising out of or in connection with them, are governed by the laws of India.

27.2 Either party may notify the other of a dispute under section 26. The parties will then try in good faith to resolve it by negotiation for 30 days.

27.3 A dispute not resolved within those 30 days will be finally resolved by arbitration under the Arbitration and Conciliation Act, 1996, by a sole arbitrator appointed by agreement of the parties or, if they have not agreed within 30 days of a written request by either party, appointed under section 11 of that Act. Neither party may appoint the arbitrator alone. The seat and venue of the arbitration is Ranchi, Jharkhand, and the language is English. The award is final and binding.

27.4 Subject to clause 27.3, the courts at Ranchi, Jharkhand have exclusive jurisdiction. Either party may seek interim relief from those courts under section 9 of that Act.

28. General

In short: the usual legal mechanics.

28.1 Assignment. You may not assign or transfer these terms without our written consent. We may assign them to an affiliate, or to a successor to the relevant part of our business, by notice to you.

28.2 Entire agreement and precedence. These terms, with the Documentation instructions they point to, are the entire agreement between you and Scanimart about the Service. The Documentation describes how the Service works. Only the Documentation instructions that these terms point to (in clauses 10.1, 11.2 and 11.3) form part of these terms; the rest of it is guidance. If we change those instructions in a way that adds to what you must do, the change applies to you only after the notice that clause 12.2 or section 25 requires, whichever applies. In a conflict, a written agreement signed by you and Scanimart prevails to the extent it expressly says so (or as clause 1.3 says); then these terms; then the Documentation.

28.3 No exclusivity. These terms do not stop either party from working with others. You may integrate with other platforms, and Scanimart may work with other developers and build features like yours.

28.4 Other terms. If any part of these terms is invalid, the rest remains in force. Not enforcing a part is not a waiver of it. The parties are independent; these terms create no partnership, agency or employment, and you may not bind Scanimart. No one other than you and Scanimart has rights under these terms, except that Scanimart may enforce section 23 for its directors and employees. These terms are an electronic record under the IT Act and need no physical signature.

29. Grievance officer and contact

In short: write to developers@scanimart.com, or to the Grievance Officer if a complaint is unresolved.

29.1 Questions about the API or these terms: developers@scanimart.com. Security reports and Security Incidents: developers@scanimart.com, with the subject "Security". Legal notices: as clause 26.1 says.

29.2 In accordance with the IT Act and the rules made under it, you may raise a grievance about the Service or the handling of data with our Grievance Officer:

Name: Sankalp Jain, Founder & CEO
Email: support@scanimart.com, with the subject line "Grievance"
Post: Grievance Officer, Snappikart Techlabs Private Limited, Manju Kunj, Ranchi, Jharkhand 834001, India

29.3 We acknowledge grievances within 24 hours of receipt and resolve them within 15 days of receipt.