Infuse-Marketplace
Infuse-Marketplace connects embedded app and algorithm developers, providers, and customers with compatible Infuse-IoT SDK device fleets.
Use Infuse-Marketplace to publish Infuse IoT applications as marketplace apps or algorithms, make them available through provider listings, sell them for specific Infuse-IoT SDK devices, and install purchased releases onto compatible embedded hardware.
Most Infuse-Marketplace work happens in the Infuse Cloud dashboard. Developers use the dashboard to review earnings, link Infuse IoT applications, upload presentation assets, add releases, set pricing, and publish. Providers use the dashboard to review earnings, discover available apps and algorithms, create listings, review purchases, inspect devices, and install purchased releases. API guides are included for teams that automate these workflows or build custom storefronts.
How Infuse-Marketplace Fits Together
Infuse-Marketplace is built around a few linked records:
| Concept | What it represents |
|---|---|
| Infuse-Marketplace instance | A developer or provider workspace inside an organisation. |
| Infuse-Marketplace item | An app or algorithm linked to an Infuse IoT application owned by the developer organisation. |
| Release | A marketplace release linked to an Infuse IoT application release. |
| Listing | A provider's sellable version of an app or algorithm, including provider markup and visibility. |
| Checkout session | A hosted payment flow for selected apps, algorithms, and devices. |
| Purchase | The commercial record created after successful checkout. |
| Entitlement | The access record that allows a purchased app or algorithm to be installed or downloaded. |
The common flow is:
- A developer creates or selects an Infuse IoT application.
- The developer creates a Marketplace item linked to that application.
- The developer adds metadata, images, Infuse IoT releases, and pricing.
- The developer publishes the app or algorithm.
- A provider discovers it and creates a listing.
- A customer buys the listed app or algorithm for one or more devices.
- Infuse validates the purchase and creates entitlements.
- The provider installs a compatible release onto the target device.
Where to Start
If you are setting up marketplace access for your organisation, start with Infuse-Marketplace Instances. Instances explain the developer and provider split, when to create multiple instances, and how to separate teams, storefronts, customer groups, and permissions.
If you are a developer publishing apps or algorithms, start with Infuse-Marketplace Developers. That section walks through marketplace item creation, assets, releases, pricing, and publishing from the dashboard.
If you are a provider reselling apps and algorithms to customers, start with Infuse-Marketplace Providers. That section covers discovery, listings, checkout verification, purchases, device views, and installs.
If you are building a custom customer storefront, read Build a Storefront after creating provider listings in the dashboard.
Dashboard and API Usage
Use the dashboard for normal operations and validation. It is the recommended path for most developer and provider teams.
Use the Infuse-Marketplace APIs when you need to:
- integrate marketplace checkout into your own customer site,
- automate app, algorithm, listing, or purchase workflows,
- connect marketplace state to internal systems,
- build provider-specific device or install experiences.
For endpoint-level details, see the Infuse-Marketplace API reference.