For the complete documentation index, see llms.txt. This page is also available as Markdown.

🔗Public APIs for Registration form (RF)

Programmatically manage wholesale registration workflows — retrieve form schemas, create registrants, filter applicants, and manage approval status.

These REST APIs let you work with your wholesale registration flow: fetch form definitions, create wholesalers, filter registrants, and change approval status.

Requirements

  • Install the BSS B2B Solution Shopify app

  • Get your Access Key from the app (see below)


🔑 Get the Access Key

  1. Get your API Key. If you don’t have one yet, please follow this document to generate it.

  2. All endpoints on this page are v1 — include the key either as accessKey in the request body, or as a header:

x-bss-b2b-api-key: <accessKey>

⚠️ Not the same header as v2 (x-api-key, used only by the Volume Pricing v2 endpoint) — check the Authentication table if you're integrating multiple API groups.


📄 Form Endpoints

Get a form by ID

Purpose Fetch form data only. Validation logic used on the storefront is not returned.

GET

Path Params

  • :id – Form ID

Query Params

  • domain – your myshopify domain

Headers

  • x-bss-b2b-api-key – your access key

Example Request

Response (example)


🧑‍💼 Wholesaler Endpoints

Create wholesaler

POST

Body

name is the field ID in the form. value is the submitted customer information.

Multi-step (version 3) forms:

  • Multi-step forms never expose a password field to configure. If your formData includes a password entry for a multi-step form, it is silently ignored — the value is not stored on the wholesaler record. Omit password for multi-step forms.

  • Multi-step forms always require an email field, even if it isn't listed when you fetch the form schema — the API adds it automatically when validating and when returning the form via the form-fetch endpoint above.

Response


Filter wholesalers

POST

Request Body Params

  • domain – your myshopify domain

  • accessKey – your access key

  • status – status to filter (example below)

  • start_date – start date (YYYY-MM-DD)

  • end_date – end date (YYYY-MM-DD)

Example Request

Response (example)

Response (no results)


Approve or reject wholesalers

POST

Action Path Param

  • Replace :action with approve or reject

Important

  • You can only change status for accounts currently in PENDING status.

Request Body Params

  • domain – your myshopify domain

  • accessKey – your access key

  • emails – array of customer emails to update

Example Request

Response (approve with partial errors)

Response (reject)

Response (no results)


⚙️ Notes & Behavior

  • Form fetch returns the schema/fields only; it does not include storefront validation logic.

  • Status change endpoints operate only on PENDING accounts.

  • Some endpoints require domain and accessKey in the request body (see examples above).

  • Multi-step (version 3) forms ignore any submitted password value and always require email, even if the form's schema doesn't list them explicitly.

If you need further assistance, please feel free to reach us at support@bss-b2b.solutions or Live Chat.

Last updated

Was this helpful?