Roblox avatar shop catalog · Roblox API

GET https://api.api.sh/roblox/v1/catalog

1 credit / call media & music try it in the playground →

Search the Roblox avatar shop, or open one item with id: name, description, item and asset type, creator, price in Robux, lowest price and lowest resale price, favourites, total quantity, limited flags, sale status, categories and bundled items. Paged with a cursor.

Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`q`	string	Search words, e.g. `hat`.
`id`	string	One catalog item id, e.g. `1028606` (Red Baseball Cap). Gives that item's detail. Example: `1028606`
`type`	asset \| bundle	With `id`: asset (default) or bundle.
`sort`	relevance \| favorited \| sales \| updated \| price_asc \| price_desc \| recent	relevance (default), favorited, sales, updated, price_asc, price_desc or recent.
`creator`	string	Only items by this creator name, e.g. `Roblox`.
`category`	string	Catalog category id, e.g. 1 all, 11 clothing, 12 accessories.
`min_price`	string	Lowest price in Robux.
`max_price`	string	Highest price in Robux.
`limit`	string	Items per page: 10, 28, 30, 60 or 120 (default 30).
`cursor`	string	Paging cursor: pass `next_cursor` from the previous answer.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/roblox/v1/catalog" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/roblox/v1/catalog",
    params={},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/roblox/v1/catalog");


const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.