> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anthid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported Time In Force

> Available time-in-force instructions and broker support.

## Overview

Time in Force (TIF) determines how long an order remains active before it is executed or canceled.

Not all brokers support the same time-in-force instructions. Before submitting an order, verify that the selected broker supports the requested configuration.

## Broker Support

Use the exact intent values shown in the first column.

| Intent value          | Common name               | Lightspeed Connect | Alpaca |
| --------------------- | ------------------------- | ------------------ | ------ |
| `DAY`                 | Day                       | ✓                  | ✓      |
| `GOOD_TILL_CANCEL`    | Good till canceled (GTC)  | —                  | ✓      |
| `IMMEDIATE_OR_CANCEL` | Immediate or cancel (IOC) | —                  | ✓      |
| `AT_OPEN`             | At the open (OPG)         | —                  | ✓      |
| `AT_CLOSE`            | At the close (CLS)        | —                  | ✓      |
| `FILL_OR_KILL`        | Fill or kill (FOK)        | —                  | ✓      |
| `EXT`                 | Extended hours            | —                  | —      |

The API enum includes every value in this table. The broker column indicates the values currently honored by the end-to-end integration. Market order requests do not include a `time_in_force`; Anthid defaults them to `DAY` during execution.

## Time In Force Definitions

| Time in force         | Description                                                                                                 |
| --------------------- | ----------------------------------------------------------------------------------------------------------- |
| `DAY`                 | Remains active for the current trading session. The broker cancels any remainder at the end of the session. |
| `GOOD_TILL_CANCEL`    | Remains active until filled, canceled, or expired under broker rules.                                       |
| `IMMEDIATE_OR_CANCEL` | Fills any immediately available quantity and cancels the remainder.                                         |
| `AT_OPEN`             | Participates only in the market opening auction.                                                            |
| `AT_CLOSE`            | Participates only in the market closing auction.                                                            |
| `FILL_OR_KILL`        | Must fill the entire quantity immediately or be canceled.                                                   |
| `EXT`                 | Requests eligibility for supported pre-market and after-hours sessions.                                     |

## Examples

### DAY

Buy 100 shares of AAPL at \$200.

* 60 shares fill during the trading session.
* 40 shares remain unfilled at market close.
* The remaining 40 shares are automatically canceled.

### GOOD\_TILL\_CANCEL

Buy 100 shares of AAPL at \$190.

* The order remains active across multiple trading days.
* The order stays active until filled, canceled, or expired by the broker.

### AT\_OPEN

Buy 100 shares of AAPL with `AT_OPEN`.

* The order participates only in the market opening auction.
* If it cannot execute during the opening cross, it is canceled.

### IMMEDIATE\_OR\_CANCEL

Buy 1,000 shares of AAPL with `IMMEDIATE_OR_CANCEL`.

* 600 shares are immediately available.
* 600 shares execute.
* The remaining 400 shares are canceled immediately.

### AT\_CLOSE

Sell 100 shares of AAPL with `AT_CLOSE`.

* The order participates only in the closing auction.
* If it cannot execute in the closing cross, it is canceled.

### FILL\_OR\_KILL

Buy 1,000 shares of AAPL with `FILL_OR_KILL`.

* The broker must fill all 1,000 shares immediately.
* If the complete quantity is unavailable, the entire order is canceled.

<Note>
  `SMART` is a route strategy, not a time-in-force value. See Supported Destinations for route values.
</Note>