Skip to main content
Inbazz is an influencer marketing platform: brands run campaigns with creators, give each creator a coupon, pay commissions on the sales attributed to those coupons, and send products to creators (seeding). The connector extracts your brands, the sales registered in Inbazz with their coupon, status and commission base, and the product seeding shipments that are waiting to be processed.

​
Configuring Inbazz as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Inbazz option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

Inbazz authenticates with an OAuth 2.0 API credential: a Client ID and a Client Secret created for your brand. The connector exchanges them for a short-lived access token on every sync, so there is nothing to renew on your side.
1

Create the credential

In the Inbazz panel, go to Integrations > API credentials and create a credential for your brand. Only brand administrators can create credentials.
2

Choose the read scopes

Select the scopes sales:read (sales) and seeding:read (seeding shipments). The connector only reads data, so the write scopes (sales:write, seeding:write) are not needed. Scopes cannot be changed later: to change them, create a new credential.
3

Copy the Client ID and Client Secret

Copy both values right away and paste them in the Nekt form.
Inbazz shows the Client Secret only once, when the credential is created. If it is lost, delete the credential in the Inbazz panel and create a new one. We recommend a credential dedicated to Nekt: Inbazz limits each credential to 100 requests per minute, shared by every system that uses it.
Groups with several brands (holdings) can ask Inbazz for a single holding credential that reaches every brand of the group. The connector then reads every active brand the credential reaches.
The following configurations are available:
  • Client ID: the identifier of the API credential created in Inbazz. Required.
  • Client Secret: the secret created together with the Client ID. Required.
  • Start Date: the earliest registration date of the sales to extract. Leave it empty to extract the full history. It does not apply to seeding shipments.
  • Lookback Days: how many days of sales are read again before the last sync point on every run. Inbazz only filters sales by their registration date, while their status keeps changing afterwards (shipped, delivered, cancelled, refunded), so recent sales are read again to pick up those changes. The default is 30.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis.
Tip: The stream can be found more easily by typing its name.
If the credential does not have the scope a stream needs (sales:read for Sales, seeding:read for Seeding Orders), that stream is skipped with a warning on the run log and the rest of the sync proceeds normally. The run fails instead, with a message explaining what to fix, when none of the selected streams can be read (for example, a credential created with write scopes only) or during a full sync, so that an empty table is never loaded over your data.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: Sales and Seeding Orders support INCREMENTAL, which we recommend. Stores is a small reference table and is always read in full (FULL_TABLE). Read more about Sync Types here.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Read the warning below before enabling it on a source with Seeding Orders.
We strongly recommend not running full syncs (manual or additional) on a source that has Seeding Orders selected.Inbazz only lists the seeding shipments that are still waiting to be processed, and never lists again the ones that left that list. A full sync replaces every table of the source, so the Seeding Orders table would keep only the shipments pending at that moment and lose all the history collected by the previous syncs. This cannot be undone by running the source again.If you also want periodic full syncs of Sales (to pick up status changes older than Lookback Days), create two Inbazz sources with the same credential: one with Stores and Sales, where full syncs are safe, and one with Seeding Orders only, always on INCREMENTAL and without additional full syncs. Both sources share the Inbazz limit of 100 requests per minute of that credential, so schedule them at alternate times (for example, one hour apart) to keep them from slowing each other down.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Inbazz and their corresponding fields. API reference: Inbazz Developers.
The brands the API credential reaches (GET /open-api/v1/stores, or GET /seedings/external/stores when the credential only has the seeding scope). A brand credential reaches one brand; a holding credential reaches every active brand of the holding.Primary key: store_id
The sales registered in Inbazz for each brand, used to attribute commissions to creators through their coupons (GET /open-api/v1/sales). Synced by their registration date; the last Lookback Days are read again on every sync to pick up status changes.Primary key: store_id, external_id · Replication key: created_at
Product seeding shipments (products your brand sends to creators) that are waiting to be processed (GET /seedings/external/orders). Inbazz only lists a shipment until the first status update is posted back for it (usually by your ERP or logistics integration) or until it is cancelled. On INCREMENTAL, every shipment the connector has seen stays in the table, with the data it had when it was last listed. Shipments whose last_seen_at is older than the latest sync have left the pending list, as long as their brand was read in that sync: if a brand was skipped (for example, the credential lost access to it), its shipments keep an older last_seen_at and only look like they left the list. Do not run full syncs on a source with this stream (see the warning in step 4).Primary key: store_id, reference · Replication key: created_at

​
Implementation Notes

  • Which sales are available: the Sales stream returns the sales your brand (or your e-commerce platform) registered in Inbazz. Fields such as discount, shipping and the order date on your platform are accepted by Inbazz when a sale is registered, but are not returned by its API.
  • Status changes: Inbazz has no “updated since” filter for sales. A status change on a sale registered more than Lookback Days ago is only picked up by a full sync, which is only safe on a source without Seeding Orders (see the warning in step 4). Increasing Lookback Days is the alternative that keeps everything in one source.
  • Several brands: with a holding credential, each brand keeps its own sync point, so a brand added to the holding later has its sales history from the Start Date extracted on its first sync.
  • Seeding shipments already processed: shipments that left the pending list before the connector ran (for example, picked up by an ERP integration that checks the list every few minutes) are not available through the Inbazz API, and neither is the delivery status or tracking code posted back for them.
  • Rate limit: Inbazz allows 100 requests per minute per credential. The connector stays below that limit and waits automatically when Inbazz asks it to slow down.