Cyclos 4.16.18 REST deprecation notes.

Use NotificationTypeEnum instead.

Starting with 4.15 the return from POST /sessions, which is to login a user being authenticated as administrator, will only return the following fields when the administrator has no visible profile fields:

• sessionToken
• group
• configuration

Starting with 4.17, only those fields will be ever returned from this operation, even if the administrator has visible profile fields.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Get the first element in dynamicValues for type dynamicSelection.

Use fieldsInBasicSearch and fieldsInAdvancedSearch instead.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Use paymentCustomValues instead.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Use forgotPasswordCaptchaInput.provider instead.

Voucher notifications are no longer only for bought.

Voucher notifications are no longer only for bought.

Voucher notifications are no longer only for bought.

Use settings.forwardMessages instead.

Voucher notifications are no longer only for bought.

Voucher notifications are no longer only for bought.

Voucher notifications are no longer only for bought.

Use type instead.

Use canPerformVoucherTransactions instead

Use voucherTransactions instead

Use voucherTransactions instead

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

Single dynamic values will change from returning value|label to only value. The catalog with the fields will be contained in the corresponding data in the property customFields.

No longer used. Use payment instead.

Use captchaInput.provider instead. The captcha provider used to requested a captcha for registration, or null if no captcha is needed.

Use viewTransactions instead.

Use view instead.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

Use paymentCustomFields instead.

The buying / sending should use a preview. So, call the preview operation and the confirmation password input will be returned on it

This value is no longer used in the vouchers search, only in the transactions search.

This value is no longer used in the vouchers search, only in the transactions search.

Use viewVouchers instead.

Use viewTransactions instead.

Use payment.id instead (handling the case when it can be null).

This field doesn't belong to the voucher itself, but to the transaction. Search for voucher transactions instead.

This field doesn't belong to the voucher itself, but to the transaction. Search for voucher transactions instead.

This field doesn't belong to the voucher itself, but to the transaction. Search for voucher transactions instead.

Use singleRedeem.payment instead.

Use singleRedeem.date instead.

Use transactionPeriod instead

Use transactionUser instead.

Use transactionUserGroups instead.

Use loginConfirmation.passwordStatus in [expired, reset]

Use loginConfirmation != null

Use loginConfirmation.passwordType

Use fieldsInList instead.

Use fieldsInBasicSearch instead.

Use fieldsInList instead.

Use fieldsInBasicSearch instead.

Since 4.16 this code is never returned, but failed is returned instead.

Since 4.16 this code is never returned, but failed is returned instead.

This was intended for internal use only and is no longer used.

This was intended for internal use only and is no longer used.

This was intended for internal use only and is no longer used.

Use passwordType.buttonsPerRow instead

Use passwordType.description instead

Use allowedCredentials instead, which should contain device.

Use passwordType.global instead

Use activeCredentials instead, which should contain device.

Use activeCredentials instead, which should contain password.

Use passwordType.id instead

Use passwordType.inputMethod instead

Use passwordType.internalName instead

Use passwordType.lowerCaseLetters instead

Use passwordType.maxLength instead

Use passwordType.minLength instead

Use passwordType.mode instead

Use passwordType.name instead

Use passwordType.numberOfButtons instead

Use passwordType.numbers instead

Use passwordType.onlyNumeric instead

Use allowedCredentials instead, which should contain pin.

Use passwordType.specialCharacters instead

Use passwordType.upperCaseLetters instead

Use mobilePhone instead, as this parameter only allows id, while mobilePhone allows either id or number

Use mobilePhone instead, as this parameter only allows id, while mobilePhone allows either id or number

Chargebacks are now only handled at transfer level. Chargeback transactions no longer exist.

Starting with Cyclos 4.16, chargebacks are only at transfer level, no transaction of kind chargeback exist anymore.

Starting with Cyclos 4.16, chargebacks are only at transfer level, no transaction of kind chargeback exist anymore.

The currencies are already sent with account types. Use accountTypes.currency instead.

Use transaction.usersWhichCanAddToContacts instead.

Use transaction.usersWhichCanViewProfile instead.

Use missingLoginConfirmationPasswordType instead.

Use missingLoginConfirmationCredentials instead, which should contain device.

Use kinds instead.

Lookup the requireVerification property in fields array for the object with basicProfileField = email.

Lookup the requireVerification property in fields array for the object with phoneKind = mobile.

Use POST /{user}/tickets instead.

Use GET /{user}/tickets/data-for-new instead

DEPRECATED

DEPRECATED

DEPRECATED

Use transactionPeriod instead

Use transactionUser instead.

Use transactionUserGroups instead.

Use transactionPeriod instead

Use transactionUser instead.

Use transactionUserGroups instead.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

The user who perform the transaction action. Only used when searching for redeemed, not bought vouchers. A user identification value, such as id, username, e-mail, phone, etc. Id is always allowed, others depend on Cyclos configuration. Note that a valid numeric value is always considered as id. For example, when using another identification method that can be numeric only, prefix the value with a single quote (like in Excel spreadsheets), for example, '1234567890;

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

The minimum / maximum voucher transaction date. Only used when searching for redeemed, not bought vouchers. Is expressed an array, with the lower bound as first element, and the upper bound as second element. When only one element, will have just the lower bound. To specify only the upper bound, prefix the value with a comma.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

This operation will be only for owned vouchers. For voucher transactions, use GET /{user}/voucher-transactions/data-for-search or GET /{user}/voucher-transactions.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

The user who perform the transaction action. Only used when searching for redeemed, not bought vouchers. A user identification value, such as id, username, e-mail, phone, etc. Id is always allowed, others depend on Cyclos configuration. Note that a valid numeric value is always considered as id. For example, when using another identification method that can be numeric only, prefix the value with a single quote (like in Excel spreadsheets), for example, '1234567890;

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

The minimum / maximum voucher transaction date. Only used when searching for redeemed, not bought vouchers. Is expressed an array, with the lower bound as first element, and the upper bound as second element. When only one element, will have just the lower bound. To specify only the upper bound, prefix the value with a comma.

For redeemed, or starting with 4.15, voucher transactions, use GET /voucher-transactions instead.

This was intended for internal use only and is no longer used.

This was intended for internal use only and is no longer used.

This was intended for internal use only and is no longer used.