Market Deployer

A Market Deployer groups a set of contracts with its own margin pool. When you register your account, registerAccount enrolls you in one Market Deployer — the default one, or the one named in its marketDeployerId. If you want to trade contracts belonging to a different market deployer, or transfer collateral to one, you must explicitly enroll in it first using the enrollUserToMarketDeployer action. This action is idempotent: submitting it when you are already enrolled does not produce an error — the server simply returns enrolled: false to indicate no new enrollment was created. You can safely call it as a precondition check before any market-deployer-specific operation.

You must have a registered account before calling this action. If the signing wallet has not been registered, the server returns HTTP 400.

Prerequisites

A registered account (see registerAccount)
The numeric ID of the market deployer you want to join

Request

POST https://upsidemax.xyz/exchange
Content-Type: application/json

{
  "action": {
    "type": "enrollUserToMarketDeployer",
    "marketDeployerId": 2
  },
  "signature": { "r": "0x...", "s": "0x...", "v": 28 },
  "nonce": 1778572816871
}

Action Fields

string

required

type (required) — Must be the fixed string "enrollUserToMarketDeployer".

int32

required

marketDeployerId (required) — The numeric identifier of the market deployer you want to enroll in. Contact the market deployer operator or query the Info API to discover available IDs.

Response

{
  "status": "ok",
  "requestId": "req-144115188075855890",
  "response": {
    "type": "enrollUserToMarketDeployer",
    "data": {
      "marketDeployerId": 2,
      "enrolled": true
    }
  }
}

Response Fields

int32

The market deployer the account is now enrolled in, echoing the requested ID.

boolean

true if this request enrolled your account in the specified Market Deployer for the first time. false if you were already enrolled — not an error; the operation is idempotent — or if the request was rejected, in which case errorCode is present and non-zero. Read errorCode to tell the two apart.

number

A non-zero value indicates a business-level rejection. 0 or absent means success. Check this field even when status is "ok".

string

A human-readable description of the rejection when errorCode is non-zero. For example: "unknown marketDeployer" when the requested ID does not exist.

"status": "ok" confirms the request was received and processed by the server. It does not guarantee enrollment succeeded. Always inspect errorCode and errorMessage inside response.data to confirm the business outcome — for example, passing an unknown marketDeployerId returns status: "ok" with a non-zero errorCode.

Errors

Condition	Indicated By	Description
Unknown market deployer	HTTP 200, `enrolled: false`, `errorCode != 0`, `errorMessage: "unknown marketDeployer"`	The `marketDeployerId` does not correspond to any registered deployer. The enrollment list is unchanged.
Already enrolled	HTTP 200, `enrolled: false`, no `errorCode`	Not an error — enrollment is idempotent.
Unregistered account	`400 BAD_REQUEST`	The signing wallet has not called `registerAccount` yet, or `marketDeployerId` is missing.
Invalid parameter	`400 INVALID_PARAM`	`marketDeployerId` is out of range. `errors[]` names the field, the `reason`, and the `expected` value.
`sync` sent	`400 SYNC_NOT_APPLICABLE`	This action always answers synchronously.
Duplicate nonce	`400 DUPLICATE_NONCE`	A request with the same `nonce` from this signer is still in flight.
Bad signature	`401 SIGNATURE_INVALID`	Signature recovery failed or did not match.
Rate limited	`429 RATE_LIMITED`	Too many requests.
Unavailable	`503 DOWNSTREAM_UNAVAILABLE` / `WARMING_UP`	Temporarily unavailable; retry later.
Timeout	`504 DOWNSTREAM_TIMEOUT`	No result within the waiting window. The enrollment may already be applied — check with `userMarketDeployers` before retrying; see Timeouts and retries.

Do not confuse a business rejection (errorCode != 0 inside the response body) with an HTTP error. The server returns HTTP 200 for both successful enrollments and unknown-deployer rejections. Your client must always read errorCode to determine the true outcome.

Next Steps

Verify enrollment

Check that enrolled: true (or enrolled: false if you expected to already be enrolled) and that errorCode is 0 or absent.

Lock collateral into the deployer

Use lockCollateral to deposit funds into the market deployer’s collateral pool before placing orders.

Start trading

With collateral locked, you can now place orders on contracts belonging to this market deployer using the order action.

Overview

Account

Orders

Margin & Leverage

Conditional Orders

Collateral Transfers

API Wallet

Prerequisites

Request

Action Fields

Response

Response Fields

Errors

Next Steps

​Prerequisites

​Request

​Action Fields

​Response

​Response Fields

​Errors

​Next Steps

Prerequisites

Request

Action Fields

Response

Response Fields

Errors

Next Steps