POST
/
account
/
predict-address
curl --request POST \
--url https://be.onebalance.io/api/account/predict-address \
--header 'Content-Type: application/json' \
--header 'x-api-key: <api-key>' \
--data '{
"sessionAddress": "0x1cBFbFd62a276BF6D79d504eA4CA75a7baDcf5b1",
"adminAddress": "0xc162a3cE45ad151eeCd0a5532D6E489D034aB3B8"
}'
{
  "predictedAddress": "0xE20295ec513DEf805D9c3083b0C8EaB64692D764"
}

Authorizations

x-api-key
string
header
required

The OneBalance API uses API keys to authenticate requests. All API requests require authentication using an API key passed in the x-api-key header:

curl -X 'GET' \
'https://be.onebalance.io/api/path-to/endpoint' \
-H 'x-api-key: ${ONEBALANCE_API_KEY}' \
...

A public API key is available for testing purposes with limited usage: 42bb629272001ee1163ca0dbbbc07bcbb0ef57a57baf16c4b1d4672db4562c11.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Learn how to generate API access tokens at OneBalance Docs.

Body

application/json

The input parameters vary based on account type:

Role-based Account: Requires sessionAddress (used for signing operations) and adminAddress (backup admin that can perform rage quit).

Basic Account: Requires type (account type identifier) and signerAddress (ECDSA signer address).

Input parameters for predicting a smart account address.

Learn more about account types and their capabilities at OneBalance Account Models.

Input for role-based account prediction using sessionAddress and adminAddress

Response

201
application/json

Predicted address

The response is of type object.