POST
/
api
/
v1
/
erc721
/
permit
curl --location --request POST 'https://groupos.xyz/api/v1/erc721/permit' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <token>' \
--data-raw '{
    "chainId": 5,
    "contractAddress": "0x67F4732266C7300cca593C814d46bee72e40659F",
    "recipientAddress": "0xc517c83f417b73dA98647dad0FCB80af9f3b9531"
}'

{
  "success": true,
  "permitId": "8493b65e-e0a1-4b13-90ec-7af3a923f8b9",
  "signature": "0xecb043a2da3a1c5e9a0a00cea8ffabb5815b12a9e1f91b97005c8d92b41b19cea8ffabb5815b12a9e1f91b97005c8d92b41b19ce"
}

Permiting is still currently in beta. Please schedule a call if you would like to use permits in production and we can fast-track your onboarding.

​
Permiting vs. Minting

Permiting enables you to permit an address to mint tokens on their own time and does not itself produce a blockchain transaction. This makes permiting free for your application as users will be paying with their own gas at the time of mint, which can take place on your own interface or use a default experience provided by Station.

When you permit an NFT, our cloud-wallets sign an approval for the recipient that is used to authenticate their mint call within the smart contract. Each signature can optionally be set with an expiration as well.

​
Body

chainId
number
required

The id of the chain supporting the NFT. This cannot be changed after creation.

contractAddress
string
required

The NFT smart contract address to permit with.

recipientAddress
string
required

The address to permit an NFT to.

expiration
date

The datetime for when this permit expires.

metadata
object

Metadata to associate with this NFT, which overrides any defaults set at the collection-level.

​
Response

success
boolean

Indicates whether the call was successful.

permitId
string

ID for the newly created permit.

signature
string

Raw bytes signature of approval for the newly created permit.

Mint NFTsQuery Owners