Skip to main content
POST
Rebind a customer to a new Hyperprop login (support flow)

Authorizations

Authorization
string
header
required

JWT Bearer token for user session auth. Format: "Bearer {token}". Used by User and Organization endpoints.

Path Parameters

bindingId
string
required

Binding ID from GET /trader-bindings

Body

application/json
traderId
string

The NEW Hyperprop user ID to bind this customer to. Provide EITHER traderId OR email.

Example:

"f994bc02-343c-4026-8a57-afc085eca8d5"

email
string

Email of the customer's NEW Hyperprop login (must already exist — the customer signs up first). Resolved to their user ID server-side.

Example:

"customer-new@gmail.com"

Response

Success - customer rebound to the new login

success
boolean
Example:

true

message
string
Example:

"Customer rebound — 2 active account(s) on the old login were failed"

data
object