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

Copper.co Orders API

The orders API from Copper.co — 8 operation(s) for orders.

Copper.co Orders API is one of 18 APIs that Copper.co 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.

This API exposes 10 operations across 8 paths, and defines 38 schemas. It is described by OpenAPI 3.2.0, at version latest.

Requests are made against 3 base URLs: https://api.copper.co/platform, https://api.stage.copper.co/platform, https://api.testnet.copper.co/platform.

10 operations 8 paths 38 schemas 2 GET5 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://api.copper.co/platform
Resource Areas
1

Paths & Operations 10

Across 8 paths, the API surfaces 10 operations — 2 GET, 5 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

orders 10
POST
/dry-run-orders
Dry Run Order
body → 200400403409
GET
/orders
Get Orders
22 params → 200400403409
POST
/orders
Create Order
body → 200400403409
POST
/orders/
Create Multiple Orders
1 param body → 200400403409
PATCH
/orders/{acceptOtcOrderId}
Accept Order
2 params → 200400403409
PATCH
/orders/{cancelOrderId}
Cancel Order
2 params body → 200400403409
PATCH
/orders/{coSignOrderId}
Approve (co-sign) Order
2 params body → 200400403409
GET
/orders/{orderId}
Get Order by ID
1 param → 200400403409
PATCH
/orders/{orderId}
Provide master password for Order
2 params body → 200400403409
PATCH
/orders/{startSigningOrderId}
Start Signing
2 params → 200400403409

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are OrderExtra (56 properties), CreateOrder (34 properties), DryRunOrderRequest (23 properties), CryptoAddress (20 properties). Each schema is shown below with its type and property counts.

AddressCategory
string
FeeLevel
string
FeeType
string
DryRunOrder
object
7 properties 3 required
BlockchainTransactionType
string
PortfolioType
string
UploadPartSignedTx
object
RequestedNetworkFees
object
5 properties
CreateOrders
object
1 property 1 required
LimitType
string
OrderType
string
ClearLoopExtra
object
2 properties
CurrencyConfigurationExtra
object
TargetType
string
DepositOrigin
string
AddressType
string
UpdateOrderCoSigners
object
1 property
CancelOrder
object
1 property
CreateOrder
object
34 properties 4 required
OrderReceiver
object
3 properties
Order
object
18 properties 9 required
Warning
object
2 properties 1 required
UserAbstraction
string
DeliveryType
string
FeeEstimation
object
12 properties 2 required
CryptoAddressExtra
object
OrderStatus
string
AddressTag
string
Orders
object
1 property 1 required
OrderExtra
object
56 properties
WithdrawTarget
object
3 properties 1 required
MinimalUnit
object
CryptoAddressEmbedded
object
1 property
DryRunOrderRequest
object
23 properties 3 required
UploadFullSignedTx
object
CryptoAddress
object
20 properties 8 required
EnterMasterPassword
object
1 property 1 required
CurrencyConfiguration
object
11 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

copper-co-orders-api-openapi.yml Raw ↑

Other APIs Copper.co publishes across the network.

Copper.co Accounts API
Copper.co Address Book API
Copper.co Blockchain API
Copper.co Clearloop API
Copper.co Currencies API
Copper.co Deposit Targets API
Copper.co Exchange API
Copper.co Files API
Copper.co Lending API
Copper.co Network API
Copper.co Organizations API
Copper.co Portfolios API
Where this information came from

This is an independent, third-party profile of Copper.co 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.