---
title: "PlayerLookupResponse"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.cardzone.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# PlayerLookupResponse

Path: Cardzone B2B API

## Fields

- `status` (`PlayerLookupResponse.status`; string, required) — `found`: show `profile` next to the entered ID and let the customer confirm it. `not_found`: the game reported that the ID does not exist, or it is malformed for the game. Ask the customer to check it; ordering is still allowed. `unavailable`: the game could not answer right now. Let the customer continue without a profile. `unsupported`: this product has no player lookup.
  - one of `"found"`, `"not_found"`, `"unavailable"`, `"unsupported"`
- `product_id` (`PlayerLookupResponse.product_id`; string, required)
  - format `uuid`
- `recipient` (`PlayerLookupResponse.recipient`; map<string>, required) — The recipient that was looked up, after trimming. Send the customer's own input when creating the order; the profile never replaces it.
- `profile` (`PlayerLookupResponse.profile`; object, required, nullable) — Present only when status is found.
  - `display_name` (`PlayerLookupResponse.profile.display_name`; string, required, nullable) — In-game name to show the customer.
  - `username` (`PlayerLookupResponse.profile.username`; string, required, nullable) — Account handle, when the game has one separate from the name.
  - `image_url` (`PlayerLookupResponse.profile.image_url`; string, required, nullable) — Avatar URL, when the game's source exposes one.
    - format `uri`
- `product_code` (`PlayerLookupResponse.product_code`; string, optional, nullable)


Source: https://docs.cardzone.ai/reference/schemas/PlayerLookupResponse/index.md