# Backward compatibility

Changes to the Solidgate APIs are aimed at minimizing the impact on existing integrations. However, depending on the type of change, actions might be required.

> Any API change that requires client-side adjustments is communicated in advance, with preparation time and clear guidance.
When a field or feature is marked as **deprecated** and a **deprecation notice** is added to the changelog, it serves as an early notice. Deprecated fields or features are not removed immediately.


**Breaking changes** can impact existing integrations and require adjustments. These are marked with a **breaking changes** badge in the changelog and include:

Category
Change
Operation removal
Removing an API operation.
Request
Remove or rename a field, make optional fields required, remove 
oneOf
.
Response
Remove or rename a field, change HTTP status code, remove 
oneOf
.
Type changes
Change request or response data types.
HTTP headers
Add required headers or remove existing ones.
Enum updates
Remove enum values.
Errors
Change existing error codes.
Validation rules
Add stricter or new rules.
Authentication and authorization
Change requirements.
**Non-breaking** changes modifications do not affect existing integrations and ensure backward compatibility:

Category
Change
Request
Add new optional fields, change required fields to optional.
Response
Add new optional fields, change optional fields to required.
HTTP headers
Add new optional headers, change header case.
Field length
Expand maximum length.
Identifier format
Change prefixes or formatting.
Webhook events
Add new opt-in event types.
Webhook schema
Add new fields.
Rate limiting
Changes communicated at least one month in advance.
For help, contact us. Stay informed with the Changelog.