> For the complete documentation index, see [llms.txt](https://docs.shyft.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shyft.to/dev-guides/solana/build-nft-marketplace.md).

# Build NFT Marketplace

Developing and launching a marketplace can be quite a time and resource-intensive task. This is where SHYFT APIs come in. SHYFT provides a suite of **marketplace APIs for Solana Blockchain**, using which you can create and launch your own fully functional in-app NFT marketplace in a few days.

We have deployed a devnet NFT marketplace for you to play around with. Try it out to get a sense of how it feels.

[Nft Marketplace Demo](https://nfts.shyft.to)

This series will help you understand SHYFT's Marketplace APIs better. By the end of this series, you will be able to

* Set up an NFT marketplace.
* Update an NFT marketplace.
* List NFTs for sale in the marketplace.
* Un-list (cancel) a listed NFT.
* Buy NFTs in the marketplace.
* Show all NFTs listed on the marketplace.
* Get marketplace statistics.
* Fetch and withdraw treasury balance from the marketplace.

Let's get started on the journey, in the first episode we will understand terminologies around a marketplace. Create and update marketplace parameters.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.shyft.to/dev-guides/solana/build-nft-marketplace.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.