# List Strict Send Payment Paths

The strict send payment path endpoint lists the paths a payment can take based on the amount of an asset you want to send. The source asset amount stays constant, and the type and amount of an asset received varies based on offers in the order books.

For this search, Horizon loads a list of assets that the recipient can recieve (based on destination_account or destination_assets) and displays the possible paths from the different source assets to the destination asset. Only paths that satisfy the source_amount are returned.

GET/paths/strict-send?source_asset_type={native,credit_alphanum4,credit_alphanum12}&source_asset_code={:asset_code}&source_asset_issuer={:account_id}&source_amount={:amount}&destination_account={:account_id}&destination_assets={:asset_list}
• ARGUMENTREQUIRED

DESCRIPTION

• source_asset_typerequired

The type for the source asset. Either native, credit_alphanum4, or credit_alphanum12.

• source_asset_issueroptional

The Stellar address of the issuer of the source asset. Required if the source_asset_type is not native.

• source_asset_codeoptional

The code for the source asset. Required if the source_asset_type is not native.

• source_amountrequired

The amount of the source asset that should be sent.

• destination_accountoptional

The Stellar address of the reciever. Any returned path must end with an asset that the recipient can receive. Using either source_account or source_assets as an argument is required for strict send path payments.

• destination_assetsoptional

A comma-separated list of assets that the recipient can receive. Any returned path must end with an asset in this list. Each asset is formatted as CODE:ISSUER_ACCOUNT. For example: USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX. Using either source_account or source_assets as an argument is required for strict send path payments.