Get Shared Object Collections
horizon_get_shared_collectionsReads a single permanent collection catalog page to retrieve shared object definitions for world-map or async-PvP access; requires userId and sessionToken.
Instructions
Reads one permanent collection catalog page. Use when: explicit world-map/async-PvP object access after reading horizon://docs/shared-objects. Not for: background polling, automatic page traversal, interpreting opaque bytes or using this as a combat validator. Requires: userId and the player's session: sign in with horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. Side effects: Read only; retain catalogRevision across pages. Returns: {revision,definitions,nextAfterKey,limits,serverTime} Errors: 409 revision/state/permission conflict or lost response: explicitly reread owned objects/usage and reconcile original intent, never automatically retry with newer revisions or a replacement ID. 404 does not distinguish missing/private/expired data. 422 retains existing data on quota/archive failure. 401 means the session is missing or expired: sign in again and retry with the new accessToken. 403 for a session means the token belongs to another user: pass the userId that signed in. Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Explicit page size from one to fifty; no automatic page traversal | |
| userId | Yes | Active player UUID matching the authenticated session and project | |
| afterKey | No | Previous nextAfterKey, omitted on the first catalog page | |
| sessionToken | Yes | Player accessToken, sent only as Bearer | |
| catalogRevision | No | Original first-page catalog revision retained across later pages |