Skip to main content
Every movement of the key owner’s ruby balance, newest first: settlement payouts, positions sold in the SeeSaw app, opinion paybacks and creator fees, the rubies taken back when something is reversed, and the one-off conversion of the old sapphire balance. Scope: read · Annotations: readOnlyHint REST equivalent: GET /open/v1/me/ruby-ledger

Parameters

Over REST these are query parameters with the same names. An unknown flow or source is 400 INVALID_ARGUMENT with details.field naming it.

Returns

Each row: How type maps to source:
The sapphire_* type names are historical: those ledger lines pay rubies now that sapphires have been merged into rubies. Reversals stay on their own line, so summing a filtered page by direction gives that line’s net.
Filtering happens in the ledger query, so pages and has_more are exact. A combination that cannot match — flow=out with source=sell, say — returns an empty page. source=other matches only the classified other types (today sapphire_conversion); unclassified types appear only when source is omitted. Only rubies are listed. Sapphire movements from before the merge are not in this ledger; the balance they left behind arrives as a single sapphire_conversion row. Example:

Example prompts

  • “Where did my rubies come from this month?”
  • “When did I sell my Community Shield position, and for how much?”
  • “How many rubies have my opinions brought in?”
get_my_profile · list_my_positions · list_my_coin_ledger · Rubies and positions