Polyester REST endpoints expose public IDs as short base58 strings. The same identifiers appear in URLs, JSON fields, logs, and support workflows.
For what public IDs are and why they are opaque, see Public IDs. This page covers only how they look and behave over REST.
Using base58 IDs
Use IDs exactly as returned:
{
"orderId": "An6UebxCZd"
}You can pass the same values back in REST path, query, or JSON fields:
curl "https://api.polyester.io/v1/spot/orders/An6UebxCZd"REST clients should:
- store IDs as strings
- compare IDs as exact strings
- keep the original casing
- use the base58 value directly in REST requests, URLs, logs, and support workflows
Base58 is used because the same 64-bit public ID can become a much shorter and cleaner URL segment than its decimal representation.
Crossing to other interfaces
A raw REST integration should keep the base58 string exactly as returned and never needs to convert it. Conversion only matters when an ID crosses into an interface that carries identifiers as raw 64-bit values; see ConnectRPC identifiers for that representation.
