RESTAPI:Version 1.13: Unterschied zwischen den Versionen

Aus Cryptshare Documentation
Wechseln zu:Navigation, Suche
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 1: Zeile 1:
{{WarnBox|title=Minimum Cryptshare Server Version|content=The Cryptshare REST API version 1.12 requires at least Cryptshare Server Version 7.3.0.}}
{{WarnBox|title=Minimum Cryptshare Server Version|content=The Cryptshare REST API version 1.13 requires at least Cryptshare Server Version 7.3.0.}}


= New features =
= New features =


=== New Sender/Recipient Polling APIs ===
=== Sender Name and Phone number in the transfer. ===
 
The sender’s name and phone number now is saved in the transfer and can be fetched over the Sender/Recipient Transfer polling
In addition to the already existing sender polling, recipient polling is now available. As a recipient, it is now possible to request all transfers that were sent to a specific email address (verification required). In order to reduce the number of required requests, the new endpoint is able to contain all transfer related fields.
 
Additionally, sender polling was reworked to also offer the possibility to return all transfer related fields.
 
[[{{NAMESPACE}}:Sender-recipient_Transfer_Polling|More information for the new Sender/Recipient Polling APIs can be found here.]]
 
Please note that the old sender polling endpoint was marked as deprecated and will be removed in version 2.0 of the REST API. Version 2.0 will be released in a future Cryptshare Server update. With the release of a REST API version 2.0 - to allow backwards compatibility - both, the version 1.x and 2.0 will be available in parallel for a sufficient amount of time to allow customers to migrate from version 1.x to 2.0.

Version vom 10. Juni 2025, 09:00 Uhr

Minimum Cryptshare Server Version
The Cryptshare REST API version 1.13 requires at least Cryptshare Server Version 7.3.0.

New features

Sender Name and Phone number in the transfer.

The sender’s name and phone number now is saved in the transfer and can be fetched over the Sender/Recipient Transfer polling