How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Phemex Orders API

The Orders API from Phemex — 26 operation(s) for orders.

Phemex Orders API is one of 9 APIs that Phemex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and rate-limit docs.

This API exposes 31 operations across 26 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.phemex.com, https://testnet-api.phemex.com.

31 operations 26 paths 10 schemas 8 DELETE14 GET3 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.phemex.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Phemex Orders API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-phemex-access-token (HmacAuth). By default, every request must be authenticated.

  • HmacAuth — HMAC SHA256 signed request. Also requires x-phemex-request-expiry and x-phemex-request-signature headers.

Paths & Operations 31

Across 26 paths, the API surfaces 31 operations — 8 DELETE, 14 GET, 3 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Orders 31
POST
/orders
Place order
placeContractOrder body → 200
DELETE
/orders
Bulk cancel orders
bulkCancelContractOrders 2 params → 200
PUT
/orders/create
Place order via query string
createContractOrderQueryString 12 params → 200
PUT
/orders/replace
Modify order
modifyContractOrder 9 params → 200
DELETE
/orders/cancel
Cancel order
cancelContractOrder 3 params → 200
DELETE
/orders/all
Cancel all orders
cancelAllContractOrders 3 params → 200
GET
/orders/activeList
Get active orders
getActiveContractOrders 1 param → 200
GET
/exchange/order/list
Get order history
getContractOrderHistory 7 params → 200
GET
/exchange/order
Get order by ID
getContractOrderById 3 params → 200
GET
/api-data/futures/orders
Get futures order history
getFuturesOrderHistory 5 params → 200
GET
/api-data/futures/orders/by-order-id
Get futures orders by ID
getFuturesOrderById 3 params → 200
POST
/g-orders
Place hedged order
placeHedgedOrder body → 200
DELETE
/g-orders
Bulk cancel hedged orders
bulkCancelHedgedOrders 3 params → 200
PUT
/g-orders/create
Place hedged order via query string
createHedgedOrderQueryString 14 params → 200
PUT
/g-orders/replace
Modify hedged order
modifyHedgedOrder 10 params → 200
DELETE
/g-orders/cancel
Cancel hedged order
cancelHedgedOrder 3 params → 200
DELETE
/g-orders/all
Cancel all hedged orders
cancelAllHedgedOrders 2 params → 200
GET
/g-orders/activeList
Get active hedged orders
getActiveHedgedOrders 1 param → 200
GET
/exchange/order/v2/orderList
Get closed orders
getHedgedClosedOrders 9 params → 200
GET
/api-data/g-futures/orders
Get hedged order history
getHedgedOrderHistory 5 params → 200
GET
/api-data/g-futures/orders/by-order-id
Get hedged orders by ID
getHedgedOrderById 3 params → 200
POST
/spot/orders
Place spot order
placeSpotOrder body → 200
PUT
/spot/orders
Modify spot order
modifySpotOrder 5 params → 200
DELETE
/spot/orders
Cancel spot order
cancelSpotOrder 3 params → 200
GET
/spot/orders
List active orders
listSpotActiveOrders 1 param → 200
PUT
/spot/orders/create
Place spot order via query string
createSpotOrderQueryString 10 params → 200
DELETE
/spot/orders/all
Cancel all spot orders
cancelAllSpotOrders 2 params → 200
GET
/spot/orders/active
Query specific active order
getSpotActiveOrder 3 params → 200
GET
/exchange/spot/orderdeprecated
Query closed orders (deprecated)
getSpotClosedOrders 5 params → 200
GET
/api-data/spots/orders
Get spot order history
getSpotOrderHistory 5 params → 200
GET
/api-data/spots/orders/by-order-id
Get spot orders by ID
getSpotOrdersByOrderId 3 params → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are HedgedOrderRequest (13 properties), ContractOrderRequest (12 properties), SpotOrderRequest (11 properties), OrderResponse_3 (3 properties). Each schema is shown below with its type and property counts.

OrderResponse
object
3 properties
OrderListResponse_2
object
2 properties
SpotOrderRequest
object
11 properties 4 required
ContractOrderRequest
object
12 properties 4 required
OrderResponse_3
object
3 properties
OrderResponse_2
object
3 properties
OrderListResponse
object
3 properties
ApiResponse
object
3 properties
OrderListResponse_3
object
2 properties
HedgedOrderRequest
object
13 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

phemex-orders-api-openapi.yml Raw ↑

Other APIs Phemex publishes across the network.

Phemex Account API
Phemex Conversion API
Phemex Market Data API
Phemex Positions API
Phemex Sub-Account Transfers API
Phemex Trades API
Phemex Transfers API
Phemex Wallets API
Where this information came from

This is an independent, third-party profile of Phemex Orders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.