POST
/
v2
/
evm
/
accounts
Create an EVM account
curl --request POST \
  --url https://api.cdp.coinbase.com/platform/v2/evm/accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Wallet-Auth: <x-wallet-auth>' \
  --data '{
  "name": "my-wallet"
}'
{
  "address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
  "name": "my-account",
  "policies": [
    "123e4567-e89b-12d3-a456-426614174000"
  ]
}

Authorizations

Authorization
string
header
required

A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.

Headers

X-Wallet-Auth
string
required

A JWT signed using your Wallet Secret, encoded in base64. Refer to the Generate Wallet Token section of our Authentication docs for more details on how to generate your Wallet Token.

X-Idempotency-Key
string

An optional UUID v4 request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.

Required string length: 36

Body

application/json
name
string

An optional name for the account. Account names can consist of alphanumeric characters and hyphens, and be between 2 and 36 characters long. Account names must be unique across all EVM accounts in the developer's CDP Project.

Example:

"my-wallet"

Response

Successfully created EVM account.

address
string
required

The 0x-prefixed, checksum EVM address.

Example:

"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"

name
string

An optional name for the account. Account names can consist of alphanumeric characters and hyphens, and be between 2 and 36 characters long. Account names are guaranteed to be unique across all EVM accounts in the developer's CDP Project.

Example:

"my-account"

policies
string[]

The list of policy IDs that apply to the account. This will include both the project-level policy and the account-level policy, if one exists.

Example:
["123e4567-e89b-12d3-a456-426614174000"]