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

# Order Requests

# Requests

Requests represent executable operational instructions created from active quotes.

Partners may create:

* subscription requests
* redemption requests

Each request is associated with a previously issued quote.

***

# Supported Request Types

## Subscription

```text theme={null}
USDT → USTBL
```

***

## Redemption

```text theme={null}
USTBL → USDT
```

***

# Request Creation

Partners create requests using:

* quote ID
* settlement address
* operational parameters

A valid active quote is required.

***

# Request Lifecycle

Requests support the following lifecycle states.

## CREATED

The request was successfully created.

***

## PENDING\_FUNDING

The request is awaiting funding.

***

## PARTIALLY\_FILLED

Funding was partially received.

The request remains operationally open.

***

## FILLED

Required funding has been fully received.

***

## PROCESSING

Settlement is currently in progress.

***

## FULFILLED

The request has been fully completed and settled.

***

## CANCELLED

The request was cancelled before completion.

***

## REJECTED

The request was operationally rejected.

***

## EXPIRED

The request expired before successful completion.

***

# Funding Model

Requests support:

* partial funding
* multiple funding events
* asynchronous settlement lifecycle

A single request may receive funding through multiple funding events.

***

# Settlement Rules

Settlement only occurs after:

* operational validation
* funding validation
* lifecycle eligibility checks

Settlement timing may vary depending on operational conditions.

***

# Request Cancellation

Requests may only be cancelled while operationally pending.

Completed or fulfilled requests cannot be cancelled.

***

# Funding Requirements

Funding must:

* match the expected asset
* originate from approved operational sources
* satisfy request funding requirements

Invalid or incompatible funding may prevent fulfillment.

***

# Address Validation

Settlement addresses must:

* be approved
* be active
* match the request asset/network combination

Invalid settlement addresses cause request rejection.

***

# Precision Rules

| Asset | Precision        |
| ----- | ---------------- |
| USTBL | Up to 6 decimals |
| USDT  | Up to 2 decimals |

***

# Operational Visibility

Partners may track:

* request lifecycle
* funding lifecycle
* balances
* operational statuses

through the Partner API.

***

# Error Scenarios

Request creation or processing may fail for reasons including:

* expired quote
* invalid address
* unsupported asset
* insufficient funding
* invalid lifecycle state
* operational restrictions

***

# Future Scope

The following capabilities are currently out of scope for V1:

* request amendments
* request cloning
* batch requests
* partial request cancellation
* webhook notifications
* advanced settlement controls