# Technical MTA (tMTA)

Interactive content available
All ledger endpoints can be interacted with through interactive [API Registry](/apis/ledger/bundled)

## What is tMTA?

A **Technical Mid-Term Adjustment (tMTA)** is a simplified, technical process used to change data or attach documents to an already issued policy, without initiating a full commercial MTA (which might impact pricing, coverage, or contract structure). This adjustment is purely administrative and should influence only the fields that don't affect final premium .

### Use Case

tMTA is typically used in scenarios where:

- Some data needs to be changed post policy issue
- A signed contract, scanned certificate, or supporting documentation needs to be added post-issuance.
- No financial, legal, or coverage-related parameters of the policy are being changed.
- No new documents or policy version needs to be created or shared with the customer


### Summary

tMTA serves as a lightweight and technical mechanism to change specific data and/or add supplementary documents to active policies. It is designed for backend or system-level integrations and should not be confused with a full MTA that triggers recalculations or business rules.

## Endpoint - tMTA

This endpoint is used to upload documents (e.g., PDFs or images) for a given insurance policy and/or change specified data. It supports file uploads encoded in **Base64 format** and allows categorizing the document under types like `"other"` by default.

## Notes

No Premium Impact: tMTAs must not affect pricing, premium calculations, or financial flows. If a change could influence the premium or coverage, a full MTA should be used instead.

Only PDF and PNG files are currently supported via MIME types.