Deprecations
Stay informed about APIs, features, and infrastructure components that are being phased out or scheduled for retirement across Senmo's platforms.
This page provides information about deprecation notices, migration requirements, and end-of-support timelines for InfraRails, Hyperhash, and Foundry.
Our goal is to communicate changes clearly and help developers maintain reliable integrations as our infrastructure evolves.
Current deprecations
No official deprecations have been announced.
There are currently no published deprecation notices for InfraRails, Hyperhash, or Foundry.
| Platform | Published deprecations |
|---|---|
| Infrarails | None announced |
| Hyperhash | None announced |
| Foundry | None announced |
This page will be updated when an API, feature, or supported integration is formally scheduled for retirement.
Understanding deprecations
A deprecation indicates that an existing API or feature is no longer recommended for new integrations and may be removed in a future release.
Deprecated functionality may continue operating during a transition period, depending on the applicable release and service arrangements.
Deprecation does not necessarily mean immediate removal.
Deprecation lifecycle
The typical deprecation process consists of four stages:
| Stage | Description |
|---|---|
| Active | The API or feature is supported for its intended use |
| Deprecated | Retirement has been announced and migration is recommended |
| End of Support | Regular support or maintenance is discontinued according to the notice |
| Removed | The API or feature is no longer available |
Not every change follows the same timeline. Security issues, external provider requirements, or other exceptional circumstances may require a different approach.
Deprecation notices
When a deprecation is announced, the notice will identify the relevant information where applicable.
- Platform: The affected Senmo product.
- Component: The endpoint, feature, or integration being deprecated.
- Announcement date: When the deprecation was communicated.
- Replacement: The recommended alternative, if available.
- Migration guidance: Changes developers should make.
- End-of-support date: The applicable support deadline, if established.
- Removal date: The planned retirement date, if established.
Dates and migration requirements will be published when confirmed.
API deprecations
API deprecations may affect:
- Individual endpoints.
- Authentication methods.
- Request or response fields.
- API versions.
- Transaction workflows.
- Provider integrations.
- Legacy configuration options.
When a replacement is available, developers should follow the published migration guidance.
Breaking changes and deprecations
A breaking change modifies existing behavior in a way that may require an application update.
A deprecation announces that a capability is being phased out.
These events are related but not identical.
For example, an API may be deprecated before it is removed, giving developers time to migrate.
However, some breaking changes may occur without a deprecation period when necessary to address urgent security or operational requirements.
See API Changes for published modifications to API behavior.
Migration guidance
When a feature is deprecated, we recommend the following approach.
1. Review the notice
Identify the affected endpoints, features, and supported environments.
2. Assess your integration
Determine whether your application depends on the deprecated functionality.
3. Review the replacement
Consult the relevant API Reference and migration instructions.
4. Update your implementation
Modify authentication, requests, responses, or business workflows as required.
5. Test the changes
Validate your integration in an appropriate testing environment where available.
6. Deploy before retirement
Complete migration before the announced removal date.
Version compatibility
API compatibility depends on the supported version and deployment environment.
Developers should avoid assuming that undocumented or deprecated behavior will remain available indefinitely.
We recommend using documented endpoints, supported authentication methods, and current request and response schemas.
Deprecation history
No historical deprecation entries have been published.
Future notices will use the following format.
Component name — Deprecation notice
Platform: InfraRails / Hyperhash / Foundry
Status: Deprecated
Announced: YYYY-MM-DD
End of support: To be announced
Removal date: To be announced
Affected functionality
Description of the API, feature, or integration being retired.
Reason for deprecation
Explanation of the change.
Recommended replacement
Information about the supported alternative, where available.
Required developer action
Migration steps and relevant documentation.
Stay informed
Review the following resources for related information:
- Platform Updates — Product and infrastructure developments.
- API Changes — Endpoint additions, improvements, and breaking changes.
- API Reference — Current technical integration specifications.
- Support — Assistance with integration and migration questions.
Deprecation timelines are established individually and become effective only when formally announced. This page does not establish a universal notice period or guarantee continued availability of deprecated functionality.
Updated about 2 hours ago