From 5d0b560ba5a6300c353796fcc887c4513a914965 Mon Sep 17 00:00:00 2001
From: cryptam <102138190+CryptAm@users.noreply.github.com>
Date: Sat, 3 Oct 2026 09:04:23 +0300
Subject: [PATCH] Fix invalid operationId in README example
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The README usage example references an operation ID that does not exist in the current OpenAPI spec:

```ts
type ListingsResult = OperationResponse<"get_listings_1">;
```

### Verification

Searched `opensea-api.json` for:

* `get_listings_1` — no matches found
* `list_listings_collection_all` — found as the `operationId` for `GET /api/v2/listings/collection/{slug}/all`

The README example therefore uses a stale/invalid operation ID.

### Change

Replace `get_listings_1` with the operation ID currently defined in `opensea-api.json`:

```ts
type ListingsResult = OperationResponse<"list_listings_collection_all">;
```

This keeps the README example consistent with the OpenAPI source of truth.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3064e31..6f4f1ff 100644
--- a/README.md
+++ b/README.md
@@ -24,7 +24,7 @@ The `opensea-api.json` file is committed to git intentionally — it's the versi
 import type { Schemas, OperationResponse, OperationQueryParams } from "@opensea/api-types";
 
 type Collection = Schemas["CollectionResponse"];
-type ListingsResult = OperationResponse<"get_listings_1">;
+type ListingsResult = OperationResponse<"list_listings_collection_all">;
 type ListParams = OperationQueryParams<"list_collections">;
 ```