> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/technical-design/basket-publication-api.md).

# Basket publication API

`POST /baskets` accepts multipart form data with a `basket` JSON field and required `icon`. `PATCH /baskets/:id` accepts the same complete metadata and an optional replacement icon. Each leg supplies `perpAsset`, `weightBps`, `isLong` and `leverageBps`. Images are PNG/JPEG/WebP up to 5 MiB; JSON is bounded to 64 KiB. Validation checks metadata, unique markets, exact total weights, current eligibility and leverage limits before publication. Publication inserts version 1 atomically; ownership-checked edits append one version under a row lock. Upload failure creates no basket, failed database writes clean new uploads, and old version icons remain available. All baskets are public; prepared deployments are separate transaction state.

For live order triggers and target differences, see [Trading and rebalancing](/takes-docs/concepts/trading-and-rebalancing.md#trading-and-rebalancing). See [Analytics](/takes-docs/analytics.md) for performance, [Trade](/takes-docs/trade.md) for the separate trading experience, and [Referrals](/takes-docs/referrals.md) for attribution and rewards.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://takes.gitbook.io/takes-docs/technical-design/basket-publication-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.