Skip to main content
API docs by Redocly

Codefi Staking API (3.5.0)

Download OpenAPI specification:Download

License: Apache 2.0

Staking

Staking operations.

Initiate staking by idempotently reserving validators (0x01 credentials only).

Reserves a validator for the specific client (0x01 credentials only). Requires an idempotent key.

It takes the supplied withdrawal_pubkey, the amount which must be equal to 32,000,000,000 Gwei (32 ETH), with the following optional fields: a vault_name, a fee_recipient ETH1 address and builder_relays with the array of MEV relay addresses.

It returns the deposit payload for the user to send.

Filtering options available. Customer can choose CloudProvider(s), Region(s) and ClientType(s) (see documentation for full list of possibilities) If omitted, validators allocated as per default.

Authorizations:
token
header Parameters
Idempotency-Key
required
string <uuid>
Example: f1c971b4-7114-4c4b-8ad2-a6f9e33e2cd0

the unique idempotency key for this request

Request Body schema: application/json
required

Withdrawal Public Key, the pledged Amount of 32,000,000,000 Gwei (32 ETH) and an option vault name.

withdrawal_pubkey
required
string (PublicKey) ^(0x[a-fA-F0-9]{40})$

Unique Ethereum address withdrawal key: 20-bytes, hex-encoded, optional 0x prefix, case insensitive.

amount
required
string (Gwei) ^[0-9]+$
vault_name
string^[ a-zA-Z0-9_-]{3,20}$
fee_recipient
string (Eth1Address) ^0x[a-fA-F0-9]{40}$

An ethereum 1 address, uniquely identifying them. 20-bytes, hex encoded with 0x prefix, case insensitive.

builder_relays
Array of strings (BuilderRelayAddress) [ items^(?:https?://)((0x[a-fA-F0-9]{96})|(0x[a-fA-F... ]
cloud_providers
Array of strings (CloudProvider)
Items Enum: "azure" "aws"
regions
Array of strings (Region)
Items Enum: "as-japan" "as-singapore" "eu-sweden" "eu-ireland" "us-central"
client_types
Array of strings (ClientType)
Items Enum: "teku" "lighthouse"

Responses

Request samples

Content type
application/json
{}

Response samples

Content type
application/json
{
  • "chain_deposit_configuration": {
    },
  • "stake": {
    },
  • "fee_recipient": "0x93247f2209abcacf57b75a51dafae777f9dd38bc"
}

Initiate staking by idempotently reserving validators (0x01 credentials only).

Reserves validators for the specific client (0x01 credentials only). Requires an idempotent key.

It takes the supplied withdrawal_pubkey, the amount which must equal to or a multiple of 32,000,000,000 Gwei (32 ETH), with the following optional fields: a vault_name, a fee_recipient ETH1 address and builder_relays with the array of MEV relay addresses.

It returns the deposit payloads for the user to send.

Filtering options available. Customer can choose CloudProvider(s), Region(s) and ClientType(s) (see documentation for full list of possibilities) If omitted, validators allocated as per default.

Authorizations:
token
header Parameters
Idempotency-Key
required
string <uuid>
Example: f1c971b4-7114-4c4b-8ad2-a6f9e33e2cd0

the unique idempotency key for this request

Request Body schema: application/json
required

Withdrawal Public Key, the pledged Amount of 32,000,000,000 Gwei (32 ETH) and an option vault name.

withdrawal_pubkey
required
string (PublicKey) ^(0x[a-fA-F0-9]{40})$

Unique Ethereum address withdrawal key: 20-bytes, hex-encoded, optional 0x prefix, case insensitive.

amount
required
string (Gwei) ^[0-9]+$
vault_name
string^[ a-zA-Z0-9_-]{3,20}$
fee_recipient
string (Eth1Address) ^0x[a-fA-F0-9]{40}$

An ethereum 1 address, uniquely identifying them. 20-bytes, hex encoded with 0x prefix, case insensitive.

builder_relays
Array of strings (BuilderRelayAddress) [ items^(?:https?://)((0x[a-fA-F0-9]{96})|(0x[a-fA-F... ]
cloud_providers
Array of strings (CloudProvider)
Items Enum: "azure" "aws"
regions
Array of strings (Region)
Items Enum: "as-japan" "as-singapore" "eu-sweden" "eu-ireland" "us-central"
client_types
Array of strings (ClientType)
Items Enum: "teku" "lighthouse"

Responses

Request samples

Content type
application/json
{}

Response samples

Content type
application/json
{
  • "chain_deposit_configuration": {
    },
  • "stakes": [
    ],
  • "fee_recipient": "0x93247f2209abcacf57b75a51dafae777f9dd38bc"
}

Initiate staking by idempotently reserving a unique validator with 0x02 credential.

Reserves a consolidated validator for the specific client (withdrawal credential 0x02). Requires an idempotent key. It takes an amount must equal or above 32,000,000,000 Gwei (32 ETH) and equal or below 2,048,000,000,000 Gwei (2048 ETH). It uses the supplied withdrawal_pubkey, with the following optional fields: a vault_name, a fee_recipient ETH1 address and builder_relays with the array of MEV relay addresses. It returns the deposit payloads for the user to send for each validator. Filtering options available. Customer can choose CloudProvider(s), Region(s) and ClientType(s) (see documentation for full list of possibilities) If omitted, validators allocated as per default.

Authorizations:
token
header Parameters
Idempotency-Key
required
string <uuid>
Example: f1c971b4-7114-4c4b-8ad2-a6f9e33e2cd0

the unique idempotency key for this request

Request Body schema: application/json
required

Stake a single consolidated validator (0x02 withdrawal credential)

withdrawal_pubkey
required
string (PublicKey) ^(0x[a-fA-F0-9]{40})$

Unique Ethereum address withdrawal key: 20-bytes, hex-encoded, optional 0x prefix, case insensitive.

amount
required
string (Gwei) ^[0-9]+$
vault_name
string^[ a-zA-Z0-9_-]{3,20}$
fee_recipient
string (Eth1Address) ^0x[a-fA-F0-9]{40}$

An ethereum 1 address, uniquely identifying them. 20-bytes, hex encoded with 0x prefix, case insensitive.

builder_relays
Array of strings (BuilderRelayAddress) [ items^(?:https?://)((0x[a-fA-F0-9]{96})|(0x[a-fA-F... ]
cloud_providers
Array of strings (CloudProvider)
Items Enum: "azure" "aws"
regions
Array of strings (Region)
Items Enum: "as-japan" "as-singapore" "eu-sweden" "eu-ireland" "us-central"
client_types
Array of strings (ClientType)
Items Enum: "teku" "lighthouse"

Responses

Request samples

Content type
application/json
{}

Response samples

Content type
application/json
{
  • "chain_deposit_configuration": {
    },
  • "stakes": [
    ],
  • "fee_recipient": "0x93247f2209abcacf57b75a51dafae777f9dd38bc"
}

Get deposit payload for the previously reserved stake.

It returns the deposit payloads for the the previously reserved stake.

Authorizations:
token
path Parameters
stakeID
required
string (UUID) ^[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}...
Example: deadbeef-cafe-1337-2021-339ab8909701

Stake ID

Responses

Response samples

Content type
application/json
{
  • "chain_deposit_configuration": {
    },
  • "stakes": [
    ],
  • "fee_recipient": "0x93247f2209abcacf57b75a51dafae777f9dd38bc"
}

Request a signed voluntary exit message with optional encryption.

Get Signed Voluntary Exit Message

This endpoint prepares a signed voluntary exit message. It won't submit the message to the consensus client.

The are two possible cases: the Default and Open PGP cyphered.

Default voluntary exit

The successful response object has two fields:exit_transaction and fork_version.

Open PGP cyphered voluntary exit

The successful response object has the same exit_transaction and fork_version fields as in the previous case. The difference is that exit_transaction is an 0x-prefixed hex encoded string which contains a signed voluntary exit message encrypted as an ASCII armored message.

The customer should manually provide their armored PGP public key, and set the cypher query parameter to openpgp.

Summary of applied rules

  • No PGP public key given and the cypher=openpgp -> 400 - bad request
  • PGP public key given and cypher is not specified -> 400 - bad request
  • PGP public key given and cypher=openpgp -> Open PGP cyphered.
  • No PGP public key given and cypher is not specified -> default.
Authorizations:
token
path Parameters
validatorID
required
string (ValidatorID)
Examples:
  • 2.5552491662185297e+115 - Validator BlS Public Key
  • 42 - Validator Index

Validator identifier

query Parameters
cypher
string
Value: "openpgp"

Cypher type. The only available option at the moment is openpgp.

Responses

Response samples

Content type
application/json
Example
{
  • "exit_transaction": {
    },
  • "fork_version": "0x00000001"
}

Request a signed voluntary exit message with optional encryption.

Submit voluntary validator exit

This endpoint submits the voluntary validator exit by preparing and submitting a signed voluntary exit message. It will submit the message to the consensus client. It does not support cyphering.

Authorizations:
token
path Parameters
validatorID
required
string (ValidatorID)
Examples:
  • 2.5552491662185297e+115 - Validator BlS Public Key
  • 42 - Validator Index

Validator identifier

query Parameters
cypher
string
Value: "openpgp"

Cypher type. The only available option at the moment is openpgp.

Responses

Response samples

Content type
application/json
Example
{
  • "code": 400,
  • "message": "api error: code 400: bad request: cannot initiate validator voluntary exit: validator is not active"
}

Keys

Add ETH1 withdrawal public key (to create 0x01 withdrawals credentials).

Add ETH1 withdrawal public key (to create 0x01 withdrawals credentials).

Authorizations:
token
Request Body schema: application/json
required

Withdrawal public key with label.

id
string (UUID) ^[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}...

Unique identifier.

name
required
string^[ a-zA-Z0-9_-]{3,20}$
status
string
public_key
required
string (PublicKey) ^(0x[a-fA-F0-9]{40})$

Unique Ethereum address withdrawal key: 20-bytes, hex-encoded, optional 0x prefix, case insensitive.

Responses

Request samples

Content type
application/json
{
  • "id": "deadbeef-cafe-1337-2021-339ab8909701",
  • "name": "string",
  • "status": "string",
  • "public_key": "0x93247f2209abcacf57b75a51dafae777f9dd38bc"
}

Response samples

Content type
application/json
{
  • "id": "deadbeef-cafe-1337-2021-339ab8909701",
  • "name": "string",
  • "status": "string",
  • "public_key": "0x93247f2209abcacf57b75a51dafae777f9dd38bc"
}

Healthcheck

Readiness Probe

Readiness status

Authorizations:
token

Responses

Response samples

Content type
application/json
{
  • "code": 0,
  • "message": "string"
}

Liveness Probe

Liveness status

Authorizations:
token

Responses

Response samples

Content type
application/json
{
  • "code": 0,
  • "message": "string"
}