⚠️ Generate a private key from a mnemonic (deprecated)

Code samples

POST /api/v1/trx/account/privatekey

curl -X POST 'https://settla.net/api/v1/trx/account/privatekey' \
  -H 'X-API-Key: $SETTLA_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "mnemonic": "<12 or 24 words>",
  "index": 0
}'

DEPRECATED, shutdown 2026-12-01. The endpoint accepts a mnemonic and returns a private key; the service does not store or handle client keys.

Replacement: derive keys in your own wallet, build the transaction with POST /api/v1/trx/transactions/create, sign it on your side and submit it with POST /api/v1/trx/transactions/broadcast.

Body parameter

{
  "mnemonic": "<12 or 24 words>",
  "index": 0
}

🛠️ Parameters

Name	In	Type	Required	Description
body	body	object	true	none
» mnemonic	body	string	true	none
» index	body	integer	false	Optional derivation index for BIP44 (defaults to legacy derivation if not provided).

Example responses

200 Response

{
  "address": "TWHdzxwX6144Btjk1hvrRcVdiagwvUHika",
  "private_key": "<64 hex characters>",
  "public_key": "<130 hex characters>"
}

400 Response — missing

{
  "error": "Mnemonic is required."
}

400 Response — invalid

{
  "error": "Invalid mnemonic."
}

500 Response

{
  "error": "Failed to generate address."
}

🔁 Responses

Status	Meaning	Description	Schema
200	OK	Generated keys and address	Inline
400	Bad Request	Mnemonic missing or unparseable	Inline
500	Internal Server Error	Internal server error	Inline

🔄 Response Schema

Status Code 200

Name	Type	Required	Restrictions	Description
» address	string	false	none	none
» private_key	string	false	none	none
» public_key	string	false	none	none

Status Code 400

Name	Type	Required	Restrictions	Description
» error	string	false	none	none
» details	object	false	none	Present only on a few validation errors.

Status Code 500

Name	Type	Required	Restrictions	Description
» error	string	false	none	none
» details	object	false	none	Present only on a few validation errors.