API Deprecation Policy
Retiring or sunsetting obsolete features.
When Rapyd needs to introduce a breaking change, Rapyd initiates the deprecation process, which proceeds as follows:
Rapyd announces that the feature is deprecated. A notice will appear in the API Changelog and the API Reference, and Rapyd may also send email or add the notice to the developer newsletter. The notice will state the date that the feature will no longer be available, which is a reasonable period after the date of the notice.
During the notice period, the client is responsible for updating all code that is integrated with the feature. The deprecated feature will still be fully functional and documented in the API Reference.
At the end of the notice period, the feature becomes obsolete and will be removed from production and from the API Reference. This status is also known as end-of-life.
Endpoints
The following endpoints will be deprecated on December 31, 2024:
Deprecated Endpoint | New Endpoint | Document Link |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Deprecated Endpoint | New Endpoint | Document Link |
---|---|---|
|
| |
|
|
Deprecated Endpoint | New Endpoint | Document Link |
---|---|---|
|
|
Note
The following table includes endpoints that are in multiple lines due to their length. Please ignore the line breaks.
Deprecated Endpoint | New Endpoint | Document Link |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
The following endpoints will be deprecated on March 31, 2025:
Deprecated Endpoint | New Endpoint | Document Link |
---|---|---|
|
|
Deprecated Endpoint | New Endpoint | Document Link |
---|---|---|
|
| |
|
|