🔗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
Get your API Key. If you don’t have one yet, please follow this document to generate it.
All endpoints on this page are v1 — include the key either as
accessKeyin 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
nameis the field ID in the form.valueis the submitted customer information.
Response
Filter wholesalers
POST
Request Body Params
domain– your myshopify domainaccessKey– your access keystatus– 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
:actionwithapproveorreject
Important
You can only change status for accounts currently in PENDING status.
Request Body Params
domain– your myshopify domainaccessKey– your access keyemails– 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
domainandaccessKeyin the request body (see examples above).Multi-step (version 3) forms ignore any submitted
passwordvalue and always requireemail, even if the form's schema doesn't list them explicitly.
Last updated
Was this helpful?