Skip to content

chore(related_message): add new related message for invoice.status_up…#281

Merged
raul-facturapi merged 1 commit into
mainfrom
codex/add_new_related_resource_messages_webhook
Jul 1, 2026
Merged

chore(related_message): add new related message for invoice.status_up…#281
raul-facturapi merged 1 commit into
mainfrom
codex/add_new_related_resource_messages_webhook

Conversation

@raul-facturapi

Copy link
Copy Markdown
Collaborator

…dated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the OpenAPI v2 webhook documentation for invoice.status_updated to include a new related_resource_messages field, allowing webhook consumers to receive structured, resource-scoped messages (e.g., stamping errors) alongside the event payload.

Changes:

  • Adds related_resource_messages (array) to the invoice.status_updated webhook request body schema.
  • Introduces a new RelatedResourceMessage schema in components/schemas.
  • Adds request body examples demonstrating payloads with and without related messages (Spanish and English specs).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
website/openapi_v2.yaml Documents related_resource_messages for invoice.status_updated, adds examples, and defines RelatedResourceMessage schema (ES).
website/openapi_v2.en.yaml Same documentation updates as above for the English OpenAPI spec (EN).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@raul-facturapi raul-facturapi merged commit fa38283 into main Jul 1, 2026
1 check passed
@raul-facturapi raul-facturapi deleted the codex/add_new_related_resource_messages_webhook branch July 1, 2026 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants