Personalization applies to the main template

22 October 2026 (provisional: the final date is the day this release is published) — For a company that already works with the PDF template library, PATCH /v1/companies/{company}/personalization and its MCP tool update_account_personalization change its main template instead of the previous PDF settings. The contract does not change: same body, same scopes, same response.

What changes for a company on the library

• Write. pdf_template and accent_color are applied to the main template of the company, which publishes a new revision of it. Documents already issued keep the PDF they were captured with. language is still saved on the company, as before.
• Read. The personalization block of the Account resource returns the effective values of the main template: its design as pdf_template and its brand color as accent_color. A company without a main template reads classic and null.
• Same permissions. The plan checks (editor right to change the color or to choose Corporative or Premium) and the 422 validations of the slug and of the #RRGGBB color do not change.
• Companies not migrated yet. Nothing changes: they keep writing and reading the previous settings.

Nothing to adapt in your integration: you do not need to send new fields or call another operation. If you also manage the main template through the library, the revision published by this operation appears in its history like any other.

New error: pdf_main_template_required

When the company is on the library but has no main template, there is nothing to apply the design or the color to, and the operation answers 409 pdf_main_template_required. Nothing is changed, the invoice language included. Set a main template in the library of the company and repeat the same request.

MCP tools

update_account_personalization behaves exactly like the HTTP operation and returns the same error, so an assistant needs no new instructions.

The table below lists the operation of this release.