Add applied_at and applied_by fields to tag endpoint examples

[VedranZoricic]

Summary

Intercom PR #468217 updates entity-level tag endpoints (contacts, conversations, tickets) to use VersionedTaggingPresenter, which adds applied_at and applied_by fields to tag responses. This PR updates the OpenAPI spec to match.

What changed

New fields on entity-level tag responses

POST and DELETE tag endpoints for contacts, conversations, and tickets now return two additional nullable fields:

{
  "type": "tag",
  "id": "123",
  "name": "Manual tag",
  "applied_at": 1663597223,
  "applied_by": {
    "type": "admin",
    "id": "456"
  }
}

• applied_at (integer, nullable) — Unix timestamp of when the tag was applied
• applied_by (object, nullable) — The admin who applied the tag

Both fields are null when the tag wasn't actually applied (e.g., DELETE on an already-removed tag, which returns 200 OK).

Schema reference updates

Workspace-level endpoints (POST /tags, GET /tags/{id}) use TagResponse and don't return applied_at/applied_by. Their schema references are updated from tag to the existing tag_basic schema to reflect this. The full tag schema (with the new nullable fields) is used for entity-level endpoints.

Schema	Used by
tag	Entity tag endpoints, tag_list items
tag_basic	POST /tags, GET /tags/{id}, company.tags.tags[], conversation part tags

tag schema updates

• applied_at — added nullable: true
• applied_by — changed to an inline object with nullable: true and allOf reference to reference schema

Endpoints with updated examples

Endpoint	Change
GET /contacts/{id}/tags	Example now includes applied_at/applied_by
POST /contacts/{id}/tags	Example now includes applied_at/applied_by
DELETE /contacts/{id}/tags/{tag_id}	Example now includes applied_at/applied_by
POST /conversations/{id}/tags	Example now includes applied_at/applied_by
DELETE /conversations/{id}/tags/{tag_id}	Example now includes applied_at/applied_by
POST /tickets/{id}/tags	Example now includes applied_at/applied_by
DELETE /tickets/{id}/tags/{tag_id}	Example now includes applied_at/applied_by

What stays the same

• GET /contacts/{id}/tags keeps its original { type: "list", data: [...] } response envelope
• Workspace-level GET /tags response structure is unchanged
• Conversation object tags field is unchanged

Test plan

• Verify the spec validates without errors
• Confirm GET /contacts/{id}/tags example uses type: list / data envelope (not tag.list / tags)
• Confirm entity-level POST/DELETE examples include applied_at and applied_by
• Confirm workspace-level endpoints (POST /tags, GET /tags/{id}) reference tag_basic

[levindixon]

🚢-it