---
title: "Build mint transaction data for a drop"
method: POST
path: "/api/v2/drops/{slug}/mint"
tags: ["Drops Endpoints"]
---

# Build mint transaction data for a drop

`POST /api/v2/drops/{slug}/mint`

Returns ready-to-sign transaction data for minting tokens from a drop. The caller is responsible for signing and submitting the transaction. No wallet authentication is required — only an API key. The minter address in the request body determines who will receive the tokens. Stage selection is handled automatically by the backend — if multiple stages are active, the first eligible stage is used.

## Path parameters

- `slug` string, required

## Request body

- DropMintRequest — Mint request parameters
  - `minter` string, required — Wallet address that will receive the minted tokens
  - `quantity` integer, required — Number of tokens to mint

## Response `200`

Ready-to-sign transaction data including target contract, calldata, and value

## Other responses

- `400` — Invalid request: bad address format, invalid quantity, or missing required fields
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Drop or collection not found for the given slug
- `409` — Drop is not currently active for minting (not started, ended, or paused)
- `422` — Minting precondition failed: insufficient native balance, wallet not in allowlist, mint limit exceeded, or supply exhausted
- `500` — Internal server error. Please open a support ticket so OpenSea can investigate.

---

[API](https://skmtc.net/opensea/apis/opensea-api.md) · [All operations](https://skmtc.net/opensea/apis/opensea-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/opensea/opensea-api/versions/acee8835f2ae/schema)