Skip to content
Reference

GET /api/v1/wallets

Every wallet on the account, with its group and nickname.

The key is read from PORT_API_KEY, so the command never prints it.

curl -s https://getport.app/api/v1/wallets -H "Authorization: Bearer $PORT_API_KEY"

A 200 with the envelope every endpoint answers, and this endpoint's answer in data. Amounts and USD figures are strings.

What data looks like, with sample values: the shape is the schema's, checked when these pages are built, and the figures are made up, not anyone's port.

{
"wallets": [
{
"address": "0x8f3c0e7b2a91d4c6f5e3b2a1908d7c6b5a4fc21a",
"family": "evm",
"label": "Vault",
"kind": "mine",
"group": "Cold",
"excluded": false,
"paused": false,
"verified": true
}
]
}
Field of dataTypeAlways present
walletsarray of objectyes
The whole schema of data

As the OpenAPI document at https://getport.app/api/v1/openapi.json states it. Objects are left open, because a response only ever gains fields.

{
"type": "object",
"properties": {
"wallets": {
"type": "array",
"items": {
"type": "object",
"properties": {
"address": {
"type": "string"
},
"family": {
"type": "string",
"enum": [
"evm",
"svm",
"cex",
"btc",
"move",
"tvm",
"near"
]
},
"label": {
"type": [
"string",
"null"
]
},
"kind": {
"type": "string"
},
"group": {
"type": [
"string",
"null"
]
},
"excluded": {
"type": "boolean"
},
"paused": {
"type": "boolean"
},
"verified": {
"type": "boolean"
}
},
"required": [
"address",
"family",
"label",
"kind",
"group",
"excluded",
"verified"
]
}
}
},
"required": [
"wallets"
]
}

The MCP tool port_wallets answers the same question ("which wallets are on my account") with the same figures, over the MCP server.

Every endpoint shares three: 401 for a missing or dead key, 402 for an account whose plan has no API ("Agents, MCP and the API are on Pro+ and above."), and 429 past the minute or day limit. The errors section has each body.