> For the complete documentation index, see [llms.txt](https://docs.metalx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metalx.com/developers-dex/contract-mappings/fill-types.md).

# Fill Types

Metal X DEX supports different fill types:

**GTC (Good-Till-Cancel) (FillType = 0):** Order will be in queue until it gets executed/fills completely or user can cacel at anytime.

**IOC (Immediate-Or-Cancel) (FillType = 1)**: Order will be executed/filled immediately based on the quantity available in the open orders in the orderbook, remaining unfilled orders will be cancelled. Incase of no matching fills, entire order will get cancelled. Market orders should be submitted with this type.

**POST\_ONLY (FillType = 2):** it will not be executed/filled immediately even though matching orders available in the orderbook. This kind of orders adds liquidity to the market.


---

# 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.metalx.com/developers-dex/contract-mappings/fill-types.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.