Skip to main content
POST
/
v1
/
faucet
/
drips
Request testnet tokens
curl --request POST \
  --url https://api.circle.com/v1/faucet/drips \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "address": "0xca9142d0b9804ef5e239d3bc1c7aa0d1c74e7350",
  "blockchain": "MATIC-AMOY",
  "native": true,
  "usdc": true,
  "eurc": true
}'
This response does not have an example.

Authorizations

​
Authorization
string
header
required

Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.

Headers

​
X-Request-Id
string

Developer-provided parameter used to identify this request. Useful when communicating with Circle Support.

Example:

"2adba88e-9d63-44bc-b975-9b6ae3440dde"

Body

application/json
​
address
string
required

Blockchain generated unique identifier, associated with wallet (account), smart contract or other blockchain objects.

Example:

"0xca9142d0b9804ef5e239d3bc1c7aa0d1c74e7350"

​
blockchain
enum<string>
required

The testnet blockchain network the resource will be created on or is currently on.

Available options:
ETH-SEPOLIA,
AVAX-FUJI,
MATIC-AMOY,
SOL-DEVNET,
ARB-SEPOLIA,
UNI-SEPOLIA,
BASE-SEPOLIA,
OP-SEPOLIA,
APTOS-TESTNET
Example:

"MATIC-AMOY"

​
native
boolean
default:false

Request native testnet tokens.

Example:

true

​
usdc
boolean
default:false

Request USDC testnet tokens.

Example:

true

​
eurc
boolean
default:false

Request EURC testnet tokens.

Example:

true

Response

Successfully requested testnet tokens. No content in body.

⌘I