Update OpenAPI spec (9b1287c)

[workos-sdk-automation]

🤖 I see new OpenAPI changes beep boop

Automated update from https://github.com/workos/workos/tree/9b1287ca6c7e0d26af5499441927ddfdd175a296

Source PRs

• workos/workos#71978
• workos/workos#72198
• workos/workos#72259
• workos/workos#72373

Changes

├─┬Paths
│ ├──[➕] {id} (17624:3)
│ ├──[➕] organization (11199:3)
│ ├──[➕] authkit_oauth_resources (17447:3)
│ ├─┬/data-integrations
│ │ └─┬GET
│ │   ├──[🔀] description (10359:20)
│ │   ├─┬Parameters
│ │   │ └──[➕] ownership (10413:17)
│ │   └─┬Responses
│ │     ├──[➕] 404 (10436:11)
│ │     └──[➕] 422 (10451:11)
│ ├─┬/data-integrations/{slug}
│ │ ├─┬GET
│ │ │ └──[🔀] description (10469:20)
│ │ ├─┬PUT
│ │ │ └──[🔀] description (10506:20)
│ │ └─┬DELETE
│ │   └──[🔀] description (10606:20)
│ └─┬/agents/sessions
│   └─┬GET
│     └─┬Parameters
│       └──[➕] organization_id (1786:17)
├─┬Tags
│ └──[➕] user-management.authkit-oauth-resources (24913:5)
└─┬Components
  ├──[➕] schemas/CreateAuthkitOauthResourceDto (27398:7)
  ├──[➕] schemas/AuthkitOauthResource (44419:7)
  └─┬Schemas
    ├─┬CreateDataIntegrationDto
    │ └─┬Properties
    │   └─┬ownership
    │     ├──[🔀] example (27094:20)
    │     ├──[➕] enum (27086:15)
    │     ├──[➖] enum (26547:15)❌ 
    │     └──[🔀] description (27088:24)
    └─┬DataIntegration
      └─┬Properties
        └─┬ownership
          ├──[🔀] example (43102:20)
          ├──[➕] enum (43096:15)
          ├──[➖] enum (42537:15)❌ 
          └──[🔀] description (43098:24)


| Document Element | Total Changes | Breaking Changes |
|------------------|---------------|------------------|
| paths            | 11            | 0                |
| tags             | 1             | 0                |
| components       | 10            | 2                |

Date: 09/12/26 | Commit: Update OpenAPI spec from workos/workos@9b1287ca6c7e0d26af5499441927ddfdd175a296

- ❌ **BREAKING Changes**: _2_ out of _22_
- **Modifications**: _8_
- **Removals**: _2_
- **Additions**: _12_
- **Breaking Removals**: _2_

ERROR: breaking changes discovered

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with one non-blocking documentation issue remaining from the previous review.

Findings

1.  Conflict response lacks context ▶

Fix with agent prompt

### Issue 1
spec/open-api-spec.yaml:undefined-11389
The new `409` response has an empty description, so generated API references and SDK metadata cannot explain what conflict callers should handle or distinguish it from the operation's other errors. Please document the concrete conflict condition for this response.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

• Adds create, list, and delete operations for AuthKit OAuth resource indicators.
• Adds retrieve, update, and delete operations for organization-owned data integrations.
• Adds ownership and organization filters and documents associated response cases.
• Updates shared data-integration ownership enums and examples.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Source[WorkOS source revision] --> Contract[Canonical OpenAPI contract]
  Contract --> Agents[Agent sessions organization filter]
  Contract --> Pipes[Data integration ownership operations]
  Contract --> AuthKit[AuthKit OAuth resources]
  Contract --> Consumers[Generated SDKs, API docs, and Postman]

Loading

_{Reviews (2) · Last reviewed commit: "Merge branch 'main' into update-spec-202..."}

[greptile-apps]

Conflict response lacks context

The new 409 response has an empty description, so generated API references and SDK metadata cannot explain what conflict callers should handle or distinguish it from the operation's other errors. Please document the concrete conflict condition for this response.

Knowledge Base Used:

• OpenAPI service contract
• API resource surface

Prompt To Fix With AI

This is a comment left during a code review.
Path: spec/open-api-spec.yaml
Line: 11389

Comment:
**Conflict response lacks context**

The new `409` response has an empty description, so generated API references and SDK metadata cannot explain what conflict callers should handle or distinguish it from the operation's other errors. Please document the concrete conflict condition for this response.

**Knowledge Base Used:**
- [OpenAPI service contract](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/openapi-spec/-/docs/openapi-contract.md)
- [API resource surface](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/openapi-spec/-/docs/api-resource-surface.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[gjtorikian]

Superseded by #170, whose spec snapshot contains every change from this PR (verified line-by-line). CI was unblocked by the .npmrc fix in #167.