# GET /api/v1/nfts > NFTs at floor, with their own total, which is not in net worth. Source: https://docs.getport.app/api/reference/nfts/ ## Example The key is read from `PORT_API_KEY`, so the command never prints it. ```sh curl -s https://getport.app/api/v1/nfts -H "Authorization: Bearer $PORT_API_KEY" ``` ## Parameters | Name | In | Type | What it does | | -------- | ----- | ------- | -------------------------------------------------------------------------------- | | `hidden` | query | boolean | Set to 1 or true to include pieces with a phishing name and collections you hid. | ## Response A 200 with the [envelope](https://docs.getport.app/api/#the-envelope) every endpoint answers, and this endpoint's answer in `data`. Amounts and USD figures are strings. What `data` looks like, with sample values: the shape is the schema's, checked when these pages are built, and the figures are made up, not anyone's port. ``` { "nfts": [ { "id": "3f6c2a1e-8b7d-4e2f-9a1c-5d4b3e2f1a0c", "walletAddress": "0x8f3c0e7b2a91d4c6f5e3b2a1908d7c6b5a4fc21a", "chainId": "ethereum", "name": "Pudgy Penguin #4821", "collection": "Pudgy Penguins", "imageUrl": null, "contract": "0xbd3531da5cf5857e7cfaa92426877b022e612cf8", "floorLabel": "9.8 ETH", "floorUsd": "24269.70", "costUsd": "19810.00", "spam": false, "spamReason": null, "hiddenByYou": false } ], "floorTotalUsd": "24269.70", "note": "Floors are not in net worth.", "folded": { "phishing": 1, "hiddenByYou": 1 } } ``` | Field of `data` | Type | Always present | | --------------- | -------------------------------- | -------------- | | `nfts` | `array of object` | yes | | `floorTotalUsd` | `string` | yes | | `note` | `"Floors are not in net worth."` | yes | | `folded` | `object` | no | The whole schema of `data` As the OpenAPI document at [`https://getport.app/api/v1/openapi.json`](https://getport.app/api/v1/openapi.json) states it. Objects are left open, because a response only ever gains fields. ``` { "type": "object", "properties": { "nfts": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string" }, "walletAddress": { "type": "string" }, "chainId": { "type": "string" }, "name": { "type": "string" }, "collection": { "type": "string" }, "imageUrl": { "type": [ "string", "null" ] }, "contract": { "type": "string" }, "floorLabel": { "type": "string" }, "floorUsd": { "type": [ "string", "null" ] }, "costUsd": { "type": [ "string", "null" ] }, "spam": { "type": "boolean" }, "spamReason": { "type": [ "string", "null" ] }, "hiddenByYou": { "type": "boolean" } }, "required": [ "id", "walletAddress", "chainId", "name", "collection", "imageUrl", "floorLabel", "floorUsd" ] } }, "floorTotalUsd": { "type": "string" }, "note": { "type": "string", "const": "Floors are not in net worth." }, "folded": { "type": "object", "properties": { "phishing": { "type": "integer", "minimum": -9007199254740991, "maximum": 9007199254740991 }, "hiddenByYou": { "type": "integer", "minimum": -9007199254740991, "maximum": 9007199254740991 } }, "required": [ "phishing", "hiddenByYou" ] } }, "required": [ "nfts", "floorTotalUsd", "note" ] } ``` ## From an agent The MCP tool `port_nfts` answers the same question ("what NFTs do I hold and what are their floors") with the same figures, over the [MCP server](https://docs.getport.app/api/mcp/). ## Refusals Every endpoint shares three: `401` for a missing or dead key, `402` for an account whose plan has no API ("Agents, MCP and the API are on Pro+ and above."), and `429` past the minute or day limit. The [errors](https://docs.getport.app/api/#errors) section has each body.