Raise max sub-accounts for a key

curl --request POST \
  --url https://api.easierprop.com/admin/keys/{id}/max-accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "max_accounts": 5
}
'

{
  "ok": true,
  "data": {
    "key": "sk_live_abc123...",
    "id": "70f60784-20f1-45ba-9a04-8e01c0b810c3",
    "label": "Production key",
    "prefix": "sk_live_abc",
    "max_accounts": 4,
    "is_active": true,
    "admin_id": "2c0f8d1c-8211-4b67-8ef6-1d8c0f610c3a",
    "created_at": "2023-11-07T05:31:56Z"
  }
}

Admin

Raise max sub-accounts for a key

Authorize additional Extra Accounts on an existing key by raising its max_accounts cap. Strictly raise-only: the request is rejected if the new value is less than or equal to the current max_accounts.

Authentication

Use either:

the dashboard JWT (Authorization: Bearer <jwt>), or
any of your sk_ API keys (X-API-Key: sk_…)

Auth is admin-scoped, not key-scoped: an sk_ identifies the admin who owns it, so any of your sk_ keys can manage any of your other keys. For example, using the sk_ of “user A” to raise the cap on the key of “user B” works as long as both keys belong to the same admin. An sk_ from a different admin returns 400 Key not found (the response purposely doesn’t distinguish “exists but not yours” from “doesn’t exist”).

Billing impact

Extras are billed based on actual sub-accounts attached, so raising the cap by itself does not generate a charge — you only pay once a sub-account beyond the included threshold is actually created.

Example

curl -X POST https://api.easierprop.com/admin/keys/{id}/max-accounts \
  -H 'X-API-Key: sk_…' \
  -H 'Content-Type: application/json' \
  -d '{"max_accounts": 6}'

POST

admin

keys

{id}

max-accounts

Raise max sub-accounts for a key

curl --request POST \
  --url https://api.easierprop.com/admin/keys/{id}/max-accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "max_accounts": 5
}
'

{
  "ok": true,
  "data": {
    "key": "sk_live_abc123...",
    "id": "70f60784-20f1-45ba-9a04-8e01c0b810c3",
    "label": "Production key",
    "prefix": "sk_live_abc",
    "max_accounts": 4,
    "is_active": true,
    "admin_id": "2c0f8d1c-8211-4b67-8ef6-1d8c0f610c3a",
    "created_at": "2023-11-07T05:31:56Z"
  }
}

Authorizations

Authorization

string

header

required

JWT token obtained from POST /admin/login

Path Parameters

string<uuid>

required

API key ID

Body

application/json

max_accounts

integer

required

New cap value. Must be strictly greater than the key's current max_accounts. The endpoint is raise-only by design — it never accepts equal or lower values.

Required range: 1 <= x <= 1000

Example:

5

Response

Cap raised

boolean

Example:

true

data

object

Show child attributes

Update API key

List MT5 accounts