Partner dashboard sign-in and organization routes ship with the launch pair
today on Development, TestNet and MainNet. Programmatic organization key
routes and trading keys with an organization key come after launch.
Sign in on the partner dashboard
Invited users sign in on the partner dashboard with Continue with Google.- Sign-in is restricted to invited email addresses. An email address with no
partner user and no open invitation receives HTTP
403(partner_not_invited). - Your first sign-in accepts all open invitations for your email address.
- Sign-in ships with the launch pair today on Development, TestNet and MainNet for invited partners.
Members and roles
An organization has members with one of three roles:owner, admin or
member. Each membership also carries a write permission flag (canWrite).
List your organization’s members with
GET /v2/organizations/{organizationId}/members. The response returns members
oldest first, with id, email, role and canWrite. A member without write
permission receives HTTP 403 (organization_permission_required) on partner
session writes.
Organization keys and scopes
Programmatic requests to/v2/organizations/{organizationId} authenticate with
an organization key sent in the Authorization header:
- Where to create a key: An
owneroradmincreates organization keys in the partner dashboard. - Secret shown once: Copy the
edel_ok_...secret when you create the key. The dashboard shows the secret once and does not display it again. - Key scopes:
read: Read organization details, members, listing requests and deposit state.read_write: Includesread, plus send listing requests, confirm listing deposits and replace listing request logos. Areadkey calling a write route receives HTTP403(organization_key_scope_insufficient).
- Scope boundary: An organization key works only on its own organization’s routes. It cannot read trader account routes or place orders, and a trader API key cannot call organization routes.
- Rate limit: Each organization key allows up to 120 requests per minute
across the organization routes (
429withRetry-After). - After launch: API routes to create, list and revoke organization keys programmatically come after launch. Today, create and manage keys in the partner dashboard.
Organization routes and curl examples
SetEDEL_API_URL from the platform introduction or
Networks. Export ORG_KEY
(edel_ok_...) and ORGANIZATION_ID before you run these commands.
Read your organization
GET /v2/organizations/{organizationId} requires the read scope and returns
id, name, slug, logoUrl, state (active or suspended), timestamp
and datetime. See
Read your organization.
List organization members
GET /v2/organizations/{organizationId}/members requires the read scope and
returns members oldest first. See
List your organization’s members.
List listing requests
GET /v2/organizations/{organizationId}/listing-requests requires the read
scope and returns the organization’s spot listing requests, newest first, with
status, decidedAt and refusalReason. See
List your organization’s listing requests.
Create a listing request
POST /v2/organizations/{organizationId}/listing-requests requires the
read_write scope and returns 201 with status pending. Do not send a
requester field; the organization comes from the key. Each organization can
send at most 10 listing requests per hour (429). See
Send a spot listing request for your organization.
depositClaim object (amount, sentAt,
transactionReference) in the request body. The venue records depositClaim as
a statement only and never counts it as a confirmed deposit. Set quoteAsset to
the venue settlement asset (read from GET /v2/spot/markets or
GET /v2/currencies).
Read listing request deposit
GET /v2/organizations/{organizationId}/listing-requests/{requestId}/deposit
requires the read scope and returns deposit instructions, live ledger
state, accepted arrivals and depositConfirmedAt. See
Read listing request deposit.
Confirm listing request deposit
POST /v2/organizations/{organizationId}/listing-requests/{requestId}/deposit/confirm
requires the read_write scope and takes no request body. The venue reads
pending transfers at the custody party, accepts a matching transfer and sets
depositConfirmedAt. See
Confirm listing request deposit.
Replace listing request logo
PUT /v2/organizations/{organizationId}/listing-requests/{requestId}/logo
requires the read_write scope. logoUrl must use https, name a host and
have no user, password or port. state is applied while the request is
pending (or failed before logo copy), or waiting_operator once Edel’s logo
store holds the logo. See
Replace listing request logo.
Common error codes
Listing requests and deposits
A spot listing request starts in statuspending. Before approval, you deposit
the required token amount to the venue custody party and confirm the deposit.
1
Read deposit instructions
Call the deposit read route:Read
instructions.custodyParty, instructions.instrumentAdmin,
instructions.instrumentId, instructions.amountNeeded and
instructions.reference.2
Send the Canton transfer instruction
Create one transfer instruction of that token to
custodyParty for the
exact amountNeeded. Attach the metadata key
edel.finance/listing-request-id with the value set to {requestId}.3
Confirm the deposit
Call the deposit confirm route with no body:When the venue accepts the matching transfer, it records the arrival with
the sender party from the transfer and sets
depositConfirmedAt.- A transfer without
edel.finance/listing-request-id, with another request ID, or with a near match never counts. - Tokens already held at
custodyPartynever count. depositClaimfrom request creation is a statement only and never creates a credit.- Deposit
state.statusiswaiting(no matching transfer),partial(a transfer names the request withwrong_amount,expiredornot_pending),offered(exact amount waits for confirmation) orconfirmed(accepted). - If the ledger is unreachable, deposit routes return
503(canton_offline).
Public spot prices
Spot prices are public and need no API key or organization key. CallGET /v2/spot/tickers to read all tradable spot markets, or pass symbols to
filter. See Fetch tickers.
- The API symbols use the venue quote spelling (for example
USD.E); the partner dashboard shows that quote asUSDCx. - Public ticker reads allow 120 requests per minute per source. Live ticker updates also stream over WebSockets.