1. General
itemdb API Guide
  • General
    • Getting Started
    • API Access
    • Slugs
    • Widget
      • Widget
      • Tab Example
  • v1
    • Item
      • Get latest items
      • Get an item
      • Get item's price history
      • Get item's auction history
      • Get item's restock history
      • Get item's trade history
      • Get items color palette
      • Get item's color palette
      • Get many items
      • Get many items
      • Get Item Drops Data
      • Get Dyeworks Variants
      • Get MME Paths
      • Get Item Effects
      • Get Cooking Pot Recipes
    • Search
      • Search for an item
    • Lists
      • Get List Info
      • Get List Item Info
      • Get List Item Data
    • Misc
      • Get all ways to change a Pet Color/Species
      • Get wearable preview
      • Get cached item's thumbnail
    • Schemas
      • Schemas
        • SaleStatus
        • ItemMallData
        • UseTypes
        • ListData
        • ListItemInfo
        • ItemData
        • itemColorData
        • ItemPriceData
        • OwlsData
        • ItemRestockData
        • ItemAuctionData
        • TradeData
        • TradeItem
        • UserList
        • ListItemInfo
        • ColorData
        • SearchFilters
  • v2
    • Intents & Cache
    • Items
      • Get a single item
      • Get many items
      • Get many items
    • Search
      • Search items
    • Lists
      • Get a list's items
    • Schemas
      • ItemIntent
      • ItemFlags
      • ItemPriceField
      • ItemPriceV2
      • NCValue
      • ItemSaleStatusV2
      • UseTypes
      • ThreeStateBoolean
      • ItemV2Minimal
      • ItemV2Card
      • ItemV2Pricer
      • ItemV2Full
      • Error
  1. General

API Access

Access Rules
Server side applications will need an API Key to access our resources.
Client-side applications (including userscripts) will require a session cookie, which requires a visit to itemdb.com.br every 24 hours (for non-logged-in users) or every 14 days (for logged-in users).

Client Side Applications#

You will need to send cookies with your request. If using Fetch, you need to add credentials: "include"
Some domains may need to be whitelisted to avoid CORS issues when using fetch. Hit us at lucca[at]itemdb.com.br if that's your case.
Userscripts can leverage the GM_xmlhttpRequest function and probably no other changes are required.
Caution
After the session expires, users will need to visit itemdb.com.br again to get a new session cookie. Until then the api will return status code401
Be mindful when fetching items or you might trigger the Rate Limit. Learn more

Server Side Applications#

You will need to generate an API Token using an API Key. This key will be linked to your itemdb account and can be revoked if used against our Terms of Use
Attention
Do NOT use API Tokens/Keys on client side (especially userscripts...)
With your API Key in hands, hit the /api/auth/token endpoint sending your key using the x-itemdb-key header.
You will receive a JSON Web Token (JWT) as response. Send this token using x-itemdb-token header.
Note
API Tokens are short lived, you will need to generate a new one every 60 minutes.
Learn more about JWTs
Each API Key starts with a default item limit. If your use case need a bigger limit hit us at lucca[at]itemdb.com.br
Tip
You can use a function like this to get your tokens
Modified at 2026-07-20 01:03:06
Previous
Getting Started
Next
Slugs
Built with