Integrations & API
Oblifee needs to know what you sell and how much of it you place on each market. You can enter that by hand or import a spreadsheet, but the least-effort path is to connect a source that already holds it. Integrations pull exactly the product and volume data compliance needs - and nothing more.
Ways to connect
| Method | Best for | Start here |
|---|---|---|
| Shopify | Merchants selling on Shopify - install the Oblifee app and link your store. | Shopify |
| Squarespace | Squarespace Commerce sellers. | Squarespace |
| REST ingestion API | ERPs and custom systems pushing data with a scoped token. | REST API |
| CSV import | One-off or periodic bulk loads, with AI-assisted column mapping. | Bulk import |
| By hand | A handful of products, or filling gaps. | Add products |
What data is pulled
Integrations are scoped to the minimum needed for compliance:
- Products - identity, brand, and packaging where available.
- Volumes - quantities placed on each market over time, which drive fees and thresholds.
They do not read customers, payment details or order contents beyond the aggregate volumes compliance requires. See Security & trust for how connections are authorised and isolated.
Authorisation at a glance
- Shopify / Squarespace use OAuth - you approve Oblifee from your store's admin, and access can be revoked there or in Oblifee at any time.
- The REST API uses a scoped token you generate per business; it can be revoked or rotated from the imports screen. See REST API.
- Webhooks (uninstall, data-deletion requests) keep Oblifee in step with the source and honour data-subject requests automatically.
:::info Sales-channel scope Oblifee is deliberately not an order-management or storefront tool. Integrations exist to keep your compliance data current, not to run your shop. :::