Skip to main content
A URN (Uniform Resource Name) is the stable identifier for a catalog resource on Managem. We chose to use URNs as our primary identity key across the platform because they provide a flexible, extensible, and human-readable way to represent resources in a hierarchical manner. URNs are used for items such as cards and products, as well as related resources like images and set symbols. If you know an item’s URN, you can resolve it directly with lookup endpoints instead of relying on text search.

​
What a Managem URN looks like

All URNs follow this canonical base shape:
Example:

​
Canonical rules

URNs are canonicalized with strict rules:
  1. Must start with urn:managem:
  2. Must be lowercase
  3. Must not end with /
If a URN violates these rules, treat it as invalid.

​
URN composition and path segments

In a URN like urn:managem:lorcana:set/rise-of-the-floodborn/card/1:
  1. urn is the URI namespace identifier
  2. managem is the namespace owner
  3. lorcana is the game slug
  4. set/rise-of-the-floodborn/card/1 is the resource path

​
Supported URN shapes

​
Primary resources

​
Derived image-like resources

​
How cards and products are composed

​
Card URNs

Card URNs are composed by appending a card ID under a set URN:
The parent must be a set URN.
Card IDs come from game-specific source data and are not always numeric.
Examples:

​
Product URNs

Product URNs are composed under a set URN:
Current product ID generation uses a stabilised version of the product name along with its classification. Observed product IDs end with an 8-character lowercase hex suffix:

​
Per-game behavior

Game slug is the <game> segment in the URN.

​
Examples