fix: remove apiId from verifyKey request

go/apps/api/openapi/openapi-generated.yaml

@@ -1,5 +1,5 @@
 # Code generated by generate_bundle.go; DO NOT EDIT.
-# Generated at: 2025-07-24T13:37:52Z
+# Generated at: 2025-07-28T10:13:32Z
 # Source: openapi-split.yaml
 
 components:
@@ -1393,18 +1393,8 @@ components:
             type: object
             additionalProperties: false
             required:
-                - apiId
                 - key
             properties:
-                apiId:
-                    type: string
-                    minLength: 3
-                    maxLength: 255
-                    pattern: "^[a-zA-Z0-9_]+$"
-                    description: |
-                        The API namespace this key belongs to.
-                        Ensures environment isolation (dev keys can't access prod data).
-                    example: api_1234
                 key:
                     type: string
                     minLength: 1
@@ -1466,7 +1456,7 @@ components:
                 meta:
                     $ref: "#/components/schemas/Meta"
                 data:
-                    "$ref": "#/components/schemas/KeysVerifyKeyResponseData"
+                    "$ref": "#/components/schemas/V2KeysVerifyKeyResponseData"
             additionalProperties: false
         V2LivenessResponseBody:
             type: object
@@ -2782,8 +2772,9 @@ components:
                     minimum: 0
                     description: Optionally override the duration of the rate limit window duration.
                     example: 600000
-        KeysVerifyKeyResponseData:
+        V2KeysVerifyKeyResponseData:
             type: object
+            additionalProperties: false
             properties:
                 valid:
                     type: boolean
@@ -4973,6 +4964,8 @@ paths:
                 Your root key needs one of:
                 - `api.*.verify_key` (verify keys in any API)
                 - `api.<api_id>.verify_key` (verify keys in specific API)
+
+                If you are getting a NOT_FOUND error, ensure your root key has the required verify key permissions.
             operationId: verifyKey
             requestBody:
                 content:

go/apps/api/openapi/spec/paths/v2/keys/verifyKey/V2KeysVerifyKeyRequestBody.yaml

@@ -8,25 +8,15 @@ examples:
       apiId: api_1234abcd
       key: sk_1234abcdef
   withPermissions:
-    summary: Check permissions  
+    summary: Check permissions
     description: Verify key has required permissions
     value:
       apiId: api_1234abcd
       key: sk_1234abcdef
       permissions: "documents.read"
 required:
-  - apiId
   - key
 properties:
-  apiId:
-    type: string
-    minLength: 3
-    maxLength: 255
-    pattern: "^[a-zA-Z0-9_]+$"
-    description: |
-      The API namespace this key belongs to.
-      Ensures environment isolation (dev keys can't access prod data).
-    example: api_1234
   key:
     type: string
     minLength: 1

go/apps/api/openapi/spec/paths/v2/keys/verifyKey/V2KeysVerifyKeyResponseBody.yaml

@@ -6,7 +6,7 @@ properties:
   meta:
     $ref: "../../../../common/Meta.yaml"
   data:
-    "$ref": "./KeysVerifyKeyResponseData.yaml"
+    "$ref": "./V2KeysVerifyKeyResponseData.yaml"
 additionalProperties: false
 examples:
   validKey:

go/apps/api/openapi/spec/paths/v2/keys/verifyKey/KeysVerifyKeyResponseData.yaml → go/apps/api/openapi/spec/paths/v2/keys/verifyKey/V2KeysVerifyKeyResponseData.yaml

@@ -1,4 +1,5 @@
 type: object
+additionalProperties: false
 properties:
   valid:
     type: boolean

go/apps/api/openapi/spec/paths/v2/keys/verifyKey/index.yaml

@@ -19,6 +19,8 @@ post:
     Your root key needs one of:
     - `api.*.verify_key` (verify keys in any API)
     - `api.<api_id>.verify_key` (verify keys in specific API)
+
+    If you are getting a NOT_FOUND error, ensure your root key has the required verify key permissions.
   operationId: verifyKey
   x-speakeasy-name-override: verifyKey
   security: