Add PATCH /data_connectors/:id to OpenAPI spec

[ellicenelson]

Why?

API consumers need documentation for the new update endpoint so they can programmatically update their data connector configurations.

How?

Adds the PATCH endpoint definition and update_data_connector_request schema to the Unstable version spec. Field descriptions mirror the existing data_connector_detail schema for consistency. Also fixes "publish" phrasing to "set to live" in the create endpoint description. Removes the changelog file to follow existing convention (changelog lives in developer-docs, not here).

Related

• intercom/intercom#489076
• intercom/developer-docs#803

_{Generated with Claude Code}

[levindixon]

LGTM! Spec changes, request schema, and error examples are clean and consistent with the existing endpoints. One small suggestion:

Missing "Invalid state" 422 example

The 422 section covers invalid audiences and invalid http_method, but not an invalid state value. Since state is the most consequential field on this endpoint, consider adding:

Invalid state:
  value:
    type: error.list
    request_id: a1b2c3d4-e5f6-7a8b-9c0d-1e2f3a4b5c6d
    errors:
    - code: parameter_invalid
      message: "Invalid state. Must be one of: draft, live"

Not a blocker — approving as-is.