---
title: "Create an Order for an Account"
method: POST
path: "/v1/trading/accounts/{account_id}/orders"
tags: ["Trading"]
---

# Create an Order for an Account

`POST /v1/trading/accounts/{account_id}/orders`

Creating an order for your end customer. Each trading request must pass in the account_id in the URL.

- Note that when submitting crypto orders, `market`, `limit` and `stop_limit` orders are supported while the supported `time_in_force` values are `gtc`, and `ioc`.
- For equities and crypto we accept fractional orders as well with either `notional` or `qty` provided.
- Note that submitting an options order is only available for partners who have been enabled for Options BETA.
- In case of Fixed Income, only `market` and `limit` order types with `day` `time_in_force` are supported, and order replacement is not supported.
Note that submitting Fixed Income orders is only available for partners who have been enabled for Fixed Income.
- Note that submitting DMA orders (using `advanced_instructions` with `algorithm: DMA`) is only available for partners/correspondents who have been enabled for DMA.
- For IPO indications of interest (`asset_class: "ipo"`), the `symbol` is the offering reference returned by [`GET /v1/ipos`](#operation/listIPOOfferings) (e.g. `FI111225`). IPO orders are notional-only (`notional` required, `qty` must be omitted), buy-side, `market` type, and `gtc` time_in_force. Indications of interest can be replaced or canceled while the offering is open via [`PATCH /v1/trading/accounts/{account_id}/orders/{order_id}`](#operation/replaceOrderForAccount) and [`DELETE /v1/trading/accounts/{account_id}/orders/{order_id}`](#operation/deleteOrderForAccount).

## Request body

- CreateOrderRequest
  - `advanced_instructions` AdvancedInstructions — Advanced instructions for Direct Market Access (DMA) routing. When `algorithm` is `DMA`, the order is routed directly to the exchange specified in `destination`. Note that this feature is only available to partners/correspondents who have been enabled for DMA.
    - `algorithm` 'DMA' — The advanced routing algorithm to use for the order. Only `DMA` (Direct Market Access) is supported.
    - `destination` 'IEX' | 'MEMX' — Target exchange for order execution. Required when `algorithm` is `DMA`.
    - `display_qty` string, decimal — Maximum shares displayed on the exchange at any time. Must be in round lot increments.
  - `client_order_id` string — A unique identifier for the order. Automatically generated if not sent. (<= 128 characters)
  - `commission` string, decimal — The commission you want to collect from the user.
  - `commission_bps` string, decimal — **deprecated**: Please use the commission_type = bps instead and set the desired bps value in the `commission` field. The percent commission you want to charge the end user on the order (expressed in bps). Alpaca will convert the order to a notional amount for purposes of calculating commission.
  - `commission_type` 'notional' | 'qty' | 'bps' — An enum to select how to interpret the value provided in the commission field. - notional: Charge commission on a per order basis. (When the `commission_type` field is omitted from the order request, this is used as the default). - qty: Charge commission on a per qty/contract basis, pro rated. - bps: The percent commission you want to charge the end user on the order (expressed in bps). Alpaca will convert the order to a notional amount for purposes of calculating commission. Commission value in bps can have up to two decimal places.
  - `extended_hours` boolean — Defaults to false. If true, order will be eligible for execution in the pre-market, after-hours, and overnight sessions. Only works with type `limit` and time_in_force set to either `day` or `gtc`.
  - `instructions` string
  - `legs` MLegOrderLeg[] — list of order legs (<= 4)
    - `position_intent` 'buy_to_open' | 'buy_to_close' | 'sell_to_open' | 'sell_to_close' — Represents the desired position strategy.
    - `ratio_qty` string, required — proportional quantity of this leg in relation to the overall multileg order qty
    - `side` 'buy' | 'sell' | 'buy_minus' | 'sell_plus' | 'sell_short' | 'sell_short_exempt' | 'undisclosed' | 'cross' | 'cross_short' — Represents what side of the transaction an order was on. Required for all order classes except for `mleg`.
    - `symbol` string, required — symbol or asset ID to identify the asset to trade
  - `limit_price` string, decimal — Required if type is `limit` or `stop_limit`. - In case of `mleg`, the limit_price parameter is expressed with the following notation: - A positive value indicates a debit, representing a cost or payment to be made. - A negative value signifies a credit, reflecting an amount to be received. - In case of Fied Income, the price is expressed in percentage of par value (face value). Price is always clean price, meaning it does not include accrued interest.
  - `notional` string, decimal — Dollar amount to trade. Cannot work with qty. Only market and limit orders supported with time_in_force = day; Only limit orders for extended hours.
  - `order_class` 'simple' | 'bracket' | 'oco' | 'oto' | 'mleg' | '' — The order classes supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order classes for each category: - Equity trading: simple (or ""), oco, oto, bracket. - Options trading: - simple (or "") - mleg (required for multi-leg complex option strategies) - Crypto trading: simple (or "").
  - `position_intent` 'buy_to_open' | 'buy_to_close' | 'sell_to_open' | 'sell_to_close' — Represents the desired position strategy.
  - `qty` string, decimal — - For equities, the number of shares to trade. Can be fractionable for only market and day order types. - Required for `mleg` order class, represents the number of units to trade of this strategy. - For Fixed Income securities, qty represents the order size in par value (face value). For example, to place an order for 1 bond with a face value of $1,000, provide a qty of 1000.
  - `side` 'buy' | 'sell' | 'buy_minus' | 'sell_plus' | 'sell_short' | 'sell_short_exempt' | 'undisclosed' | 'cross' | 'cross_short' — Represents what side of the transaction an order was on. Required for all order classes except for `mleg`.
  - `source` string
  - `stop_loss` object — Takes in a string/number values for stop_price and limit_price
    - `limit_price` string, decimal
    - `stop_price` string, decimal
  - `stop_price` string, decimal — Required if type is stop or stop_limit
  - `subtag` string
  - `swap_fee_bps` string, decimal
  - `symbol` string — Symbol or asset ID to identify the asset to trade. Required for all order classes except for `mleg`.
  - `take_profit` object — Takes in a string/number value for limit_price
    - `limit_price` string, decimal
  - `time_in_force` 'day' | 'gtc' | 'opg' | 'cls' | 'ioc' | 'fok', required — The Time-In-Force values supported by Alpaca vary based on the order's security type. Here is a breakdown of the supported TIFs for each specific security type: - Equity trading: day, gtc, opg, cls, ioc, fok. - Options trading: day. - Crypto trading: gtc, ioc. Below are the descriptions of each TIF: - day: A day order is eligible for execution only on the day it is live. By default, the order is only valid during Regular Trading Hours (9:30am - 4:00pm ET). If unfilled after the closing auction, it is automatically canceled. If submitted after the close, it is queued and submitted the following trading day. However, if marked as eligible for extended hours, the order can also execute during supported extended hours. - gtc: The order is good until canceled. Non-marketable GTC limit orders are subject to price adjustments to offset corporate actions affecting the issue. We do not currently support Do Not Reduce (DNR) orders to opt out of such price adjustments. - opg: Use this TIF with a market/limit order type to submit "market on open" (MOO) and "limit on open" (LOO) orders. This order is eligible to execute only in the market opening auction. Any unfilled orders after the open will be cancelled. OPG orders submitted after 9:28am but before 7:00pm ET will be rejected. OPG orders submitted after 7:00pm will be queued and routed to the following day's opening auction. On open/on close orders are routed to the primary exchange. Such orders do not necessarily execute exactly at 9:30am / 4:00pm ET but execute per the exchange's auction rules. - cls: Use this TIF with a market/limit order type to submit "market on close" (MOC) and "limit on close" (LOC) orders. This order is eligible to execute only in the market closing auction. Any unfilled orders after the close will be cancelled. CLS orders submitted after 3:50pm but before 7:00pm ET will be rejected. CLS orders submitted after 7:00pm will be queued and routed to the following day's closing auction. - ioc: An Immediate Or Cancel (IOC) order requires all or part of the order to be executed immediately. Any unfilled portion of the order is canceled. Most market makers who receive IOC orders will attempt to fill the order on a principal basis only, and cancel any unfilled balance. On occasion, this can result in the entire order being cancelled if the market maker does not have any existing inventory of the security in question. - fok: A Fill or Kill (FOK) order is only executed if the entire order quantity can be filled, otherwise the order is canceled.
  - `trail_percent` string, decimal — If type is trailing_stop, then one of trail_price or trail_percent is required
  - `trail_price` string, decimal — If type is trailing_stop, then one of trail_price or trail_percent is required
  - `type` 'market' | 'limit' | 'stop' | 'stop_limit' | 'trailing_stop', required — The order types supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order types for each category: - Equity trading: market, limit, stop, stop_limit, trailing_stop. - Options trading: market, limit. - Options Multileg trading: market, limit. - Crypto trading: market, limit, stop_limit.

## Response `200`

OK

- Order
  - `asset_class` 'us_equity' | 'us_option' | 'crypto' | 'ipo' — This represents the category to which the asset belongs to. It serves to identify the nature of the financial instrument, with options including "us_equity" for U.S. equities, "us_option" for U.S. options, "crypto" for cryptocurrencies, and "ipo" for IPO indications of interest. This `asset_class: ipo` value is distinct from the assets API `attributes: ["ipo"]` flag.
  - `asset_id` string, uuid — The asset ID (For options this represents the option contract ID)
  - `cancel_requested_at` string, date-time, nullable — Time when cancellation or bust was requested (if applicable)
  - `canceled_at` string, date-time, nullable — Can be null
  - `client_order_id` string — Client unique order ID
  - `commission` string, decimal — The dollar value commission for this order.
  - `commission_bps` string, decimal — **deprecated**: Please use the commission_type = bps instead and set the desired bps value in the `commission` field. The percent commission you want to charge the end user on the order (expressed in bps). Alpaca will convert the order to a notional amount for purposes of calculating commission.
  - `commission_type` 'notional' | 'qty' | 'bps' — An enum to select how to interpret the value provided in the commission field. - notional: Charge commission on a per order basis. (When the `commission_type` field is omitted from the order request, this is used as the default). - qty: Charge commission on a per qty/contract basis, pro rated. - bps: The percent commission you want to charge the end user on the order (expressed in bps). Alpaca will convert the order to a notional amount for purposes of calculating commission. Commission value in bps can have up to two decimal places.
  - `created_at` string, date-time — Time when order was entered
  - `expired_at` string, date-time, nullable — Can be null
  - `extended_hours` boolean
  - `failed_at` string, date-time, nullable — Can be null
  - `filled_at` string, date-time, nullable — Time the order was filled. Can be null if not filled
  - `filled_avg_price` string, decimal, nullable — Filled average price. Can be 0 until order is processed in case order is passed outside of market hours
  - `filled_qty` string, decimal — Filled quantity
  - `hwm` string, decimal, nullable — The highest (lowest) market price seen since the trailing stop order was submitted.
  - `id` string, uuid, required — Order ID generated by Alpaca
  - `legs` OrderLeg[], nullable — When querying non-simple order_class orders in a nested style, an array of Order entities associated with this order. Otherwise, null.
    - `asset_class` 'us_equity' | 'us_option' | 'crypto' | 'ipo' — This represents the category to which the asset belongs to. It serves to identify the nature of the financial instrument, with options including "us_equity" for U.S. equities, "us_option" for U.S. options, "crypto" for cryptocurrencies, and "ipo" for IPO indications of interest. This `asset_class: ipo` value is distinct from the assets API `attributes: ["ipo"]` flag.
    - `asset_id` string, uuid — The asset ID (For options this represents the option contract ID)
    - `canceled_at` string, date-time, nullable — Can be null
    - `client_order_id` string — Client unique order ID
    - `commission` string, decimal — The dollar value commission you want to charge the end user.
    - `commission_bps` string, decimal — **deprecated**: Please use the commission_type = bps instead and set the desired bps value in the `commission` field. The percent commission you want to charge the end user on the order (expressed in bps). Alpaca will convert the order to a notional amount for purposes of calculating commission.
    - `commission_type` 'notional' | 'qty' | 'bps' — An enum to select how to interpret the value provided in the commission field. - notional: Charge commission on a per order basis. (When the `commission_type` field is omitted from the order request, this is used as the default). - qty: Charge commission on a per qty/contract basis, pro rated. - bps: The percent commission you want to charge the end user on the order (expressed in bps). Alpaca will convert the order to a notional amount for purposes of calculating commission. Commission value in bps can have up to two decimal places.
    - `created_at` string, date-time — Time when order was entered
    - `expired_at` string, date-time, nullable — Can be null
    - `extended_hours` boolean
    - `failed_at` string, date-time, nullable — Can be null
    - `filled_at` string, date-time, nullable — Time the order was filled. Can be null if not filled
    - `filled_avg_price` string, decimal, nullable — Filled average price. Can be 0 until order is processed in case order is passed outside of market hours
    - `filled_qty` string, decimal — Filled quantity
    - `hwm` string, decimal, nullable — The highest (lowest) market price seen since the trailing stop order was submitted.
    - `id` string, uuid, required — Order ID generated by Alpaca
    - `legs` object[], nullable — Always null for an order leg; legs are not nested beyond one level.
    - `limit_price` string, decimal, nullable — Limit price
    - `notional` string, decimal, nullable — Ordered notional amount. If entered, qty will be null. Can take up to 2 decimal points.
    - `order_class` 'simple' | 'bracket' | 'oco' | 'oto' | 'mleg' | '' — The order classes supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order classes for each category: - Equity trading: simple (or ""), oco, oto, bracket. - Options trading: - simple (or "") - mleg (required for multi-leg complex option strategies) - Crypto trading: simple (or "").
    - `order_type` 'market' | 'limit' | 'stop' | 'stop_limit' | 'trailing_stop' — The order types supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order types for each category: - Equity trading: market, limit, stop, stop_limit, trailing_stop. - Options trading: market, limit. - Options Multileg trading: market, limit. - Crypto trading: market, limit, stop_limit.
    - `position_intent` 'buy_to_open' | 'buy_to_close' | 'sell_to_open' | 'sell_to_close' — Represents the desired position strategy.
    - `qty` string, decimal, nullable — Ordered quantity. If entered, notional will be null. Can take up to 2 decimal points.
    - `replaced_at` string, date-time, nullable — Can be null
    - `replaced_by` string, uuid, nullable — The order ID that this order was replaced by. (Can be null)
    - `replaces` string, uuid, nullable — The order ID that this order replaces. (Can be null)
    - `side` 'buy' | 'sell' | 'buy_minus' | 'sell_plus' | 'sell_short' | 'sell_short_exempt' | 'undisclosed' | 'cross' | 'cross_short' — Represents what side of the transaction an order was on. Required for all order classes except for `mleg`.
    - `status` 'new' | 'partially_filled' | 'filled' | 'done_for_day' | 'canceled' | 'expired' | 'replaced' | 'pending_cancel' | 'pending_replace' | 'accepted' | 'pending_new' | 'accepted_for_bidding' | 'stopped' | 'rejected' | 'suspended' | 'calculated'
    - `stop_price` string, decimal, nullable — Stop price
    - `submitted_at` string, date-time — Time the order was submitted for execution or, if not yet submitted the created_at time. Because orders are submitted for execution asynchronous to database updates, at times this may be before the created_at time.
    - `swap_fee_bps` string — Fee in basis points on top swap rate charged by the correspondent on every order
    - `swap_rate` string — Swap rate is the exchange rate (without mark-up) used to convert the price into local currency or crypto asset
    - `symbol` string, required — The asset symbol
    - `time_in_force` 'day' | 'gtc' | 'opg' | 'cls' | 'ioc' | 'fok' — The Time-In-Force values supported by Alpaca vary based on the order's security type. Here is a breakdown of the supported TIFs for each specific security type: - Equity trading: day, gtc, opg, cls, ioc, fok. - Options trading: day. - Crypto trading: gtc, ioc. Below are the descriptions of each TIF: - day: A day order is eligible for execution only on the day it is live. By default, the order is only valid during Regular Trading Hours (9:30am - 4:00pm ET). If unfilled after the closing auction, it is automatically canceled. If submitted after the close, it is queued and submitted the following trading day. However, if marked as eligible for extended hours, the order can also execute during supported extended hours. - gtc: The order is good until canceled. Non-marketable GTC limit orders are subject to price adjustments to offset corporate actions affecting the issue. We do not currently support Do Not Reduce (DNR) orders to opt out of such price adjustments. - opg: Use this TIF with a market/limit order type to submit "market on open" (MOO) and "limit on open" (LOO) orders. This order is eligible to execute only in the market opening auction. Any unfilled orders after the open will be cancelled. OPG orders submitted after 9:28am but before 7:00pm ET will be rejected. OPG orders submitted after 7:00pm will be queued and routed to the following day's opening auction. On open/on close orders are routed to the primary exchange. Such orders do not necessarily execute exactly at 9:30am / 4:00pm ET but execute per the exchange's auction rules. - cls: Use this TIF with a market/limit order type to submit "market on close" (MOC) and "limit on close" (LOC) orders. This order is eligible to execute only in the market closing auction. Any unfilled orders after the close will be cancelled. CLS orders submitted after 3:50pm but before 7:00pm ET will be rejected. CLS orders submitted after 7:00pm will be queued and routed to the following day's closing auction. - ioc: An Immediate Or Cancel (IOC) order requires all or part of the order to be executed immediately. Any unfilled portion of the order is canceled. Most market makers who receive IOC orders will attempt to fill the order on a principal basis only, and cancel any unfilled balance. On occasion, this can result in the entire order being cancelled if the market maker does not have any existing inventory of the security in question. - fok: A Fill or Kill (FOK) order is only executed if the entire order quantity can be filled, otherwise the order is canceled.
    - `trail_percent` string, decimal, nullable — The percent value away from the high water mark for trailing stop orders.
    - `trail_price` string, decimal, nullable — The dollar value away from the high water mark for trailing stop orders.
    - `type` 'market' | 'limit' | 'stop' | 'stop_limit' | 'trailing_stop' — The order types supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order types for each category: - Equity trading: market, limit, stop, stop_limit, trailing_stop. - Options trading: market, limit. - Options Multileg trading: market, limit. - Crypto trading: market, limit, stop_limit.
    - `updated_at` string, date-time — Time of most recent change to the order
    - `usd` object — Nested object to encompass the USD equivalent fields for the local currency fields
  - `limit_price` string, decimal, nullable — Limit price
  - `notional` string, decimal, nullable — Ordered notional amount. If entered, qty will be null. Can take up to 2 decimal points.
  - `order_class` 'simple' | 'bracket' | 'oco' | 'oto' | 'mleg' | '' — The order classes supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order classes for each category: - Equity trading: simple (or ""), oco, oto, bracket. - Options trading: - simple (or "") - mleg (required for multi-leg complex option strategies) - Crypto trading: simple (or "").
  - `order_type` 'market' | 'limit' | 'stop' | 'stop_limit' | 'trailing_stop' — The order types supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order types for each category: - Equity trading: market, limit, stop, stop_limit, trailing_stop. - Options trading: market, limit. - Options Multileg trading: market, limit. - Crypto trading: market, limit, stop_limit.
  - `position_intent` 'buy_to_open' | 'buy_to_close' | 'sell_to_open' | 'sell_to_close' — Represents the desired position strategy.
  - `qty` string, decimal, nullable — Ordered quantity. If entered, notional will be null. Can take up to 2 decimal points.
  - `replaced_at` string, date-time, nullable — Can be null
  - `replaced_by` string, uuid, nullable — The order ID that this order was replaced by. (Can be null)
  - `replaces` string, uuid, nullable — The order ID that this order replaces. (Can be null)
  - `side` 'buy' | 'sell' | 'buy_minus' | 'sell_plus' | 'sell_short' | 'sell_short_exempt' | 'undisclosed' | 'cross' | 'cross_short' — Represents what side of the transaction an order was on. Required for all order classes except for `mleg`.
  - `status` 'new' | 'partially_filled' | 'filled' | 'done_for_day' | 'canceled' | 'expired' | 'replaced' | 'pending_cancel' | 'pending_replace' | 'accepted' | 'pending_new' | 'accepted_for_bidding' | 'stopped' | 'rejected' | 'suspended' | 'calculated'
  - `stop_price` string, decimal, nullable — Stop price
  - `submitted_at` string, date-time — Time the order was submitted for execution or, if not yet submitted the created_at time. Because orders are submitted for execution asynchronous to database updates, at times this may be before the created_at time.
  - `swap_fee_bps` string — Fee in basis points on top swap rate charged by the correspondent on every order
  - `swap_rate` string — Swap rate is the exchange rate (without mark-up) used to convert the price into local currency or crypto asset
  - `symbol` string, required — The asset symbol
  - `time_in_force` 'day' | 'gtc' | 'opg' | 'cls' | 'ioc' | 'fok' — The Time-In-Force values supported by Alpaca vary based on the order's security type. Here is a breakdown of the supported TIFs for each specific security type: - Equity trading: day, gtc, opg, cls, ioc, fok. - Options trading: day. - Crypto trading: gtc, ioc. Below are the descriptions of each TIF: - day: A day order is eligible for execution only on the day it is live. By default, the order is only valid during Regular Trading Hours (9:30am - 4:00pm ET). If unfilled after the closing auction, it is automatically canceled. If submitted after the close, it is queued and submitted the following trading day. However, if marked as eligible for extended hours, the order can also execute during supported extended hours. - gtc: The order is good until canceled. Non-marketable GTC limit orders are subject to price adjustments to offset corporate actions affecting the issue. We do not currently support Do Not Reduce (DNR) orders to opt out of such price adjustments. - opg: Use this TIF with a market/limit order type to submit "market on open" (MOO) and "limit on open" (LOO) orders. This order is eligible to execute only in the market opening auction. Any unfilled orders after the open will be cancelled. OPG orders submitted after 9:28am but before 7:00pm ET will be rejected. OPG orders submitted after 7:00pm will be queued and routed to the following day's opening auction. On open/on close orders are routed to the primary exchange. Such orders do not necessarily execute exactly at 9:30am / 4:00pm ET but execute per the exchange's auction rules. - cls: Use this TIF with a market/limit order type to submit "market on close" (MOC) and "limit on close" (LOC) orders. This order is eligible to execute only in the market closing auction. Any unfilled orders after the close will be cancelled. CLS orders submitted after 3:50pm but before 7:00pm ET will be rejected. CLS orders submitted after 7:00pm will be queued and routed to the following day's closing auction. - ioc: An Immediate Or Cancel (IOC) order requires all or part of the order to be executed immediately. Any unfilled portion of the order is canceled. Most market makers who receive IOC orders will attempt to fill the order on a principal basis only, and cancel any unfilled balance. On occasion, this can result in the entire order being cancelled if the market maker does not have any existing inventory of the security in question. - fok: A Fill or Kill (FOK) order is only executed if the entire order quantity can be filled, otherwise the order is canceled.
  - `trail_percent` string, decimal, nullable — The percent value away from the high water mark for trailing stop orders.
  - `trail_price` string, decimal, nullable — The dollar value away from the high water mark for trailing stop orders.
  - `type` 'market' | 'limit' | 'stop' | 'stop_limit' | 'trailing_stop' — The order types supported by Alpaca vary based on the order's security type. The following provides a comprehensive breakdown of the supported order types for each category: - Equity trading: market, limit, stop, stop_limit, trailing_stop. - Options trading: market, limit. - Options Multileg trading: market, limit. - Crypto trading: market, limit, stop_limit.
  - `updated_at` string, date-time — Time of most recent change to the order
  - `usd` object — Nested object to encompass the USD equivalent fields for the local currency fields

## Other responses

- `400` — Malformed input.
- `401` — The request is not authorized. Returned when the `Authorization: Bearer` token is missing, malformed, or invalid. Applies to every authenticated India / GIFT City Broker API request.
- `403` — The order was rejected. Buy orders are not allowed for symbols on the India / GIFT City blocked-symbols list (returned by the `GET /v1/blocked-symbols` endpoint in the GIFT City Extensions API). Sell orders for these symbols are still permitted.
- `404` — Resource does not exist.
- `422` — One or more order parameters are invalid. Returned, for example, when the order `side` is missing or is not `buy` or `sell`.
- `503` — The service is temporarily unavailable due to a transient server-side condition; retry later. Applies to every authenticated India / GIFT City Broker API request.

---

[API](https://skmtc.net/alpacahq/apis/gift-city-extensions-api.md) · [All operations](https://skmtc.net/alpacahq/apis/gift-city-extensions-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/alpacahq/gift-city-extensions-api/revisions/62e3378bb273/schema)