Manage fee-wrapper access - Ground

Each fee wrapper has a customer allowlist separate from the underlying gVault’s allowlist. Ground authorizes the wrapper contract against the gVault; your backend authorizes customer addresses against the wrapper.

Add an address

Wait for the wrapper to reach status: ready, then call:

curl -X PUT \
  https://sandbox.groundtech.co/v2/fee-wrappers/8f4c52d7-62ab-4db9-a964-92f481f6b851/allowlist/0x3Bf25A73a1f1033C2d50Ac65f3C9d6A44123DB81 \
  -H "Authorization: Bearer $GROUND_API_KEY"

The path parameter is an address, which may be an EOA, smart account, multisig, or contract.

Verify access

curl \
  "https://sandbox.groundtech.co/v2/fee-wrappers/8f4c52d7-62ab-4db9-a964-92f481f6b851/allowlist/0x3Bf25A73a1f1033C2d50Ac65f3C9d6A44123DB81" \
  -H "Authorization: Bearer $GROUND_API_KEY"

{
  "allowed": true
}

Only enable a deposit after the effective state is true. If the mutation returns 202, its transaction hash is only submission evidence; poll this endpoint or consume the corresponding webhook event for confirmation.

Remove access

curl -X DELETE \
  "https://sandbox.groundtech.co/v2/fee-wrappers/8f4c52d7-62ab-4db9-a964-92f481f6b851/allowlist/0x3Bf25A73a1f1033C2d50Ac65f3C9d6A44123DB81" \
  -H "Authorization: Bearer $GROUND_API_KEY"

Removal blocks new deposits after confirmation. It preserves the address’s ability to redeem an existing fee-wrapper position. API reference: add, get, and remove.