Admin Release Allocations

Trigger a claim on behalf of your stakeholders by creating admin withdraw transactions. This is the API equivalent of the "Trigger Claim" action on the Magna dashboard — the admin pays the gas fee, and tokens are released directly to stakeholder wallets.

Note: Only allocations that are started, funded, and have a releasable amount greater than 0 will be processed. Ineligible allocations are silently skipped.

---

Example request

curl -X POST https://app.magna.so/api/external/v1/allocations/admin-release \
-H 'Content-Type: application/json' \
-H 'x-magna-api-token: magna_project_api_token' \
-d '{
  "tokenId": "your_token_id",
  "allocationIds": ["allocation_id_1", "allocation_id_2"],
  "sender": "admin_wallet_address"
}'

• magna_project_api_token (required) — replace with your Full Access Magna API token

• tokenId (required) — the token ID associated with the allocations you want to release

• allocationIds (required) — an array of allocation IDs to trigger the claim for (minimum 1)

• sender (required) — the admin wallet address that will sign the resulting transactions

---

Response

{
  "isProcessed": true,
  "result": {
    "items": [
      {
        "transactionGroupId": "0a95df41-468f-4e9b-b5eb-08e982618ad1",
        "parameters": [
          {
            "from": "0xAdminWallet...",
            "to": "0xContract...",
            "data": "0x8612...",
            "platformFee": null,
            "transactionId": "67f987e4-70cc-4833-8935-1f3baff601a4"
          }
        ]
      }
    ],
    "total": 1
  }
}

• items — an array of transaction groups, each containing unsigned transaction parameters ready for signing

• transactionGroupId — the ID of the created transaction group

• parameters — an array of unsigned transactions within the group

  • from — the sender (admin) wallet address

  • to — the smart contract address

  • data — the encoded transaction data to sign

  • platformFee — the platform fee, if applicable (null if none)

  • transactionId — the Magna transaction ID, used when submitting the signed hash

• total — the number of transaction groups created

Note: If allocations span multiple contracts, multiple transaction groups will be returned. Large batches may also be split into multiple transactions within a group based on chain-specific batch size limits.

---

After signing

Once you have signed the transaction(s), submit the signed hash to complete the flow:

curl -X POST https://app.magna.so/api/external/v1/transactions/indexing \
-H 'Content-Type: application/json' \
-H 'x-magna-api-token: magna_project_api_token' \
-d '{
  "transactionId": "67f987e4-70cc-4833-8935-1f3baff601a4",
  "transactionHash": "0xYourSignedTransactionHash..."
}'

Repeat for each transactionId returned in the response.