Get a Settlement by ID

get

Get a settlement by id

Authorizations

Ledger_API_Key & Ledger_API_UserLedger_API_Key & Ledger_API_User & Ledger_Store_Auth_TokenLedger_API_UserLedger_API_User & Ledger_Store_Auth_Token

X-Ledger-API-KeystringRequired

If you've set up your API Key when initializing your LAM, you'll need to include it as a header along with the api user header. For more details, see step 5 of the get started documentation.

X-Ledger-API-UserstringRequired

(required) Username of a registered API User

Path parameters

settlement_idintegerRequired

settlement's id

Responses

200

settlement object

application/json

404

Settlement not found

application/json

get

/settlements/{settlement_id}

HTTPcURLJavaScriptPython

GET /settlements/{settlement_id} HTTP/1.1
X-Ledger-API-Key: YOUR_API_KEY
X-Ledger-API-User: YOUR_API_KEY
Accept: */*

{
  "from_pledge_id": "123e4567-e89b-12d3-a456-426614174000",
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "inbound_transaction_intent": {
    "amount": 1,
    "to_account_id": 1,
    "to_address": "text"
  },
  "meta": {
    "ANY_ADDITIONAL_PROPERTY": null
  },
  "outbound_transaction": {
    "request_id": 1,
    "transaction_hash": "text",
    "transaction_id": 1
  },
  "repledge": {
    "repledge_id": 1,
    "request_id": 1
  },
  "repledge_intent": {
    "account_name": "text",
    "amount": "text",
    "contract_address": "text",
    "currency": "text",
    "exchange_name": "text",
    "pledge_subaccount_id": 1,
    "to_address": "text",
    "transaction_hash": "text"
  },
  "state": "text"
}