XRPL.to
GET /submit/account/{address}/inbound-tags
GET

/v1/submit/account/{address}/inbound-tags

Destination-tag usage of recent inbound payments (send-screening advisory; tagsExpected = recent deposits overwhelmingly tagged)

AuthNone — works without a key

Request

GEThttps://api.xrpl.to/v1/submit/account/rJqiMb94hyz41SBTNr2AyPNW8AzELa8nE/inbound-tags
Path parameterValueDescription
addressAn XRPL account, its r-address
curl 'https://api.xrpl.to/v1/submit/account/rJqiMb94hyz41SBTNr2AyPNW8AzELa8nE/inbound-tags'

Response

200Example response2 ms · just now · 0.2 KB · 10 lines
https://api.xrpl.to/v1/submit/account/rJqiMb94hyz41SBTNr2AyPNW8AzELa8nE/inbound-tags
{
  "success": true,
  "took": 1,
  "account": "rJqiMb94hyz41SBTNr2AyPNW8AzELa8nE",
  "sampleSize": 0,
  "tagged": 0,
  "taggedPct": 0,
  "distinctSenders": 0,
  "tagsExpected": false
}
Shapeas documented
{
  success,
  took,
  account,
  sampleSize,
  tagged,
  taggedPct,
  distinctSenders,
  tagsExpected
}

What it does

Destination-tag usage of recent inbound payments (send-screening advisory; tagsExpected = recent deposits overwhelmingly tagged)

Transaction hashes are 64-character hex. Submit relays whatever you signed: the type list below is what the ledger accepts today. Every transaction type you can submit →
OpenAPI
PrevGET/submit/account/{address}/sequenceNextGET/submit/tx/{hash}