Integration API examples omit the required credentials.type discriminator

Description

The generated create/update integration API examples show OAuth credentials without the required credentials.type discriminator.

Copying that payload results in a validation failure:

400 invalid_body

The server schema validates credentials as a discriminated union, so an OAuth payload must include "type": "OAUTH2".

Current example shape

{
  "credentials": {
    "client_id": "example-client-id",
    "client_secret": "example-client-secret",
    "scopes": "https://www.googleapis.com/auth/gmail.readonly"
  }
}

Expected example shape

{
  "credentials": {
    "type": "OAUTH2",
    "client_id": "example-client-id",
    "client_secret": "example-client-secret",
    "scopes": "https://www.googleapis.com/auth/gmail.readonly"
  }
}

Affected documentation sources

• Create integration
• Update integration

These pages are OpenAPI-backed, so the underlying schema/example may need to be corrected rather than only the MDX wrappers.

Expected result

• OAuth examples include the required credentials.type field.
• Create and update examples render a structurally valid request.
• If multiple credential variants are documented, each example includes its corresponding discriminator.