Snapcaster Developer Terms

Effective date: November 20, 2026 (version 2026-11-20)

1. About these Developer Terms

These Developer Terms are an agreement between you and Eppler Software, a sole proprietorship registered in British Columbia that does business as Snapcaster ("Snapcaster", "we", "us", "our"). They apply when you build on the Snapcaster Marketplace API as a platform, including your platform console, the sandbox, production, your credentials, Connect, key links and webhooks. "You" means the business you accept these Developer Terms for, and the person who accepts them must be able to bind it.

You accept these Developer Terms when you accept your platform invite, and we record the version you accepted. The version and effective date at the top of this page identify this text.

The Terms of Service also apply to you, and if the two conflict, these Developer Terms govern your use of the Marketplace API. Each shop that connects to your platform sells under the Seller Terms. You are not a party to the Seller Terms, but you must not cause a shop to break them.

In these Developer Terms, a "shop" is a Snapcaster Seller that has approved your platform, a "Buyer" is the person who places an order with a shop, and "Buyer information" is any information about a Buyer, or about the person an order ships to, that we send you, including names, email addresses, shipping addresses (including a corrected or suggested address) and order details. Your "credentials" are your store keys, client id and client secret, webhook signing secrets, and the sign-in details of your Test stores.

2. Your platform and its owner

Your platform has one owner, the Snapcaster account that accepted your invite. That account must keep a passkey or an authenticator app while it owns your platform. You are responsible for everything done from your platform console and for keeping the owner account secure.

3. Your credentials

Keep your credentials confidential. Store them in a secret store, never in code a browser or app user can read, and share them only with people who need them to run your platform.

Use a shop’s key only for that shop, and only for what the shop approved your platform to do. Anything done with your credentials is treated as done by you, including listing, price, stock and order changes. You are responsible for your employees, contractors and service providers who use them.

If a credential is exposed, or you think it may be, stop using it, tell us at support@snapcaster.ca at once, and replace it:

  • your webhook signing secret, your client secret, and a Test store’s key or password, from your platform console;
  • a shop’s key that came through Connect, by sending the shop through Connect again, which retires the old key;
  • a shop’s key that the shop pasted into your app, by asking the shop to replace its key from its Snapcaster settings, which retires the old key.

4. Shops that connect to your platform

A shop connects to your platform through Connect or by pasting its key into your app, and approves your platform when it does. You may act only for shops that have approved your platform, and only while they stay connected. When a shop is disconnected from your platform, by the shop or by you, whoever disconnects it chooses who finishes its open orders. If your platform is to finish them, you may read, ship and cancel those orders and answer their cancellation requests, and nothing else. Each of those orders closes to your platform as soon as it ships or is cancelled. That right ends when the last of those orders ships or is cancelled, when the shop connects again, or when the shop takes the orders back, whichever comes first.

The listings you send for a shop must match what the shop has to sell, including its cards, conditions, prices and on-hand quantities as of the time you measured them. If your platform ships a shop’s orders, you must fulfil them the way the Seller Terms require the shop to, and report what you shipped accurately.

5. Buyer information

You may use Buyer information only to fulfil and support the order it came with and to meet your legal obligations. You must not use Buyer information for marketing, add the Buyer to a mailing list, or sell, rent or trade it. You may share it with the shop that sold the order, its carrier, and service providers that work for you, only as needed to fulfil and support the order or meet your legal obligations. You remain responsible for Buyer information that you share.

You must protect Buyer information with reasonable safeguards against loss, theft, and unauthorised access, use or disclosure, and limit access to the people who need it. You must comply with the privacy laws that apply to you.

You may keep Buyer information only as long as you need it to fulfil and support the order and to meet your legal obligations, and you must then delete it. When we or the shop ask you to delete Buyer information, or when a shop disconnects from your platform, you must delete that shop’s Buyer information within 30 days, except what the law requires you to keep or what you still need to finish orders placed before the shop disconnected.

If a Buyer asks you about their information, tell us at privacy@snapcaster.ca and help us answer.

If Buyer information you hold is lost or stolen, or is accessed, used or disclosed without authorisation, or you have reason to believe it was, you must tell us at privacy@snapcaster.ca promptly and no later than 72 hours after you learn of it. Tell us what happened, what information and which orders it affects, and what you have done about it, and help us respond. We decide how Buyers and regulators are told, unless the law requires you to tell them yourself.

Our Privacy Policy explains how we handle personal information.

6. The sandbox and production

The sandbox is a separate environment that uses Stripe test mode, so no real money moves there. Use only test data in the sandbox, and never real Buyer information, real Seller information or real payment details.

Your platform reaches production only after we approve your sandbox work. We review each request for production access and may say not yet, and we tell you what is missing. Production uses real payments, refunds and Seller payouts, and you must remove every call to the sandbox-only operations before you send production traffic. Production has no uptime or support response-time commitment.

You must follow the published API documentation at developers.snapcaster.ca and its rate limits. You must not try to get around a rate limit, reach data your credentials do not authorise, or test the security or load capacity of production without our written permission.

Your platform pins the API version it uses. We retire a supported API version only after every platform has moved off it, and with at least 90 days’ written notice.

7. Suspension and ending access

We may suspend your platform, in the sandbox and in production at once, or revoke any of your credentials, for a material or repeated breach of these Developer Terms or the Terms of Service, fraud, or risk to Buyers, Sellers or the Services. We tell you why when we can. While your platform is suspended, your console stays readable but makes no changes, your shops’ keys and Connect stop working, your shops’ listings leave buyer browse, and your webhook events wait until the suspension lifts. Your shops can still finish their open orders from their Snapcaster seller dashboards.

You may stop using the Marketplace API at any time by writing to info@snapcaster.ca. When your access ends, for any reason, you must stop using your credentials and delete Buyer information under section 5. Sections 3, 5, 9 and 10 survive the end of your access.

8. Changes to these Developer Terms

When we change these Developer Terms, we publish a new version with a new version number and effective date on this page. We email your platform’s owner at least 30 days before a material change takes effect, unless the law or a risk to Buyers, Sellers or the Services needs it sooner. A material change is one that increases your obligations or reduces your rights. If you do not agree to a change, you may stop using the Marketplace API before it takes effect.

9. Disclaimers, liability and indemnity

The Marketplace API, the sandbox and the documentation are provided "as is" and "as available". Sections 15 and 16 of the Terms of Service apply to them.

You will indemnify us against third-party claims arising from your breach of these Developer Terms, including your use or loss of Buyer information.

10. Governing law and disputes

These Developer Terms are governed by the laws of the Province of British Columbia and the federal laws of Canada applicable there.

The courts of British Columbia may hear disputes about these Developer Terms, but this does not stop you or us from going to any other court that has jurisdiction.

11. Contact

  • Eppler Software, doing business as Snapcaster
  • 778-348-2447
  • info@snapcaster.ca (questions about these Developer Terms or your platform)
  • support@snapcaster.ca (incidents and exposed credentials)
  • privacy@snapcaster.ca (Buyer information)
  • Our business address is in section 1 of the Terms of Service.