routePOST /v1/accounts/resolve
statusnot probed
statespecified, not deployed
map routePOST /v1/accounts/map -
aliasPOST /accounts/resolve also answers
wrong verbGET returns 405 naming POST
ladder
| 1 | lei | a legal entity identifier is the strongest rung |
| 2 | cik | the SEC registrant number |
| 3 | ticker | with the exchange where one is given |
| 4 | linkedin_url | the company page, which is also the person id elsewhere |
| 5 | domain | the registered domain, with the parent domain trap handled |
| 6 | name + jurisdiction | normalized name, never a name alone |
| - | duns | customer supplied; carried and echoed, never used to match |
answers
| resolved | one account_id, with the rung of the ladder that matched and the evidence for it |
| ambiguous | more than one candidate; the caller is given them rather than a guess |
| unresolved | nothing matched at a rung we trust; no row is invented |
| invalid | the identifier was malformed, so it was not looked up at all |
request
returned
not probed
no success example is shown while the call has not succeeded. The probe above is what the deployed API said.
unresolved
An unresolved identifier comes back as unresolved with the rungs that were tried. It is never matched on a name alone, and a row is never created to satisfy the request.
map
Send your own id alongside an identifier and it is stored against the account_id, so later answers carry your id back. Your ids are yours: they are not published and not shared.
identity/docs/identity/
docs/docs/
steadybase-$