---
title: "Build deploy contract transaction data"
method: POST
path: "/api/v2/drops/deploy"
tags: ["Drops Endpoints"]
---

# Build deploy contract transaction data

`POST /api/v2/drops/deploy`

Returns ready-to-sign transaction data for deploying a new NFT drop contract. The caller is responsible for signing and submitting the transaction.

## Request body

- DropDeployRequest — Deploy contract request parameters
  - `chain` string, required — Chain slug (e.g. "ethereum", "base")
  - `contract_name` string, required — Name for the new contract
  - `contract_symbol` string, required — Symbol for the new contract
  - `drop_type` string, required — Drop type (see validation error for supported values)
  - `token_type` string, required — Token type (see validation error for supported values)
  - `sender` string, required — Deployer wallet address

## Response `200`

Ready-to-sign transaction data for contract deployment

## Other responses

- `400` — Invalid request: unsupported drop_type/token_type combination, bad address format, or missing required fields
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `409` — Conflict
- `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)