API v2.10 Release Notes

December 18, 2024

This page details the changes and fixes included in API v2.10, released on December 14, 2024.

New:

  • Added creditCardMasterCardFee property to the GET /payments/donorCoveredFees endpoint
  • Updated schema for GET/POST /customFields and GET/PUT /customFields/{id} endpoints
    • Added displayName field
  • Added isEventSpecificField and attendeeQuestion as query parameters for the GET /customFields Event endpoint
  • Added validation for custom field data types
    • Supported data types:
      • Whole Number (previously “Integer” – 0 decimal places allowed)
      • Decimal (previously “Float” – allows decimal places)
      • Currency (previously “Amount” – requires 2 decimal places)
      • Date
      • Text
      • Email
    • Deprecated data types:
      • Time (migrated to One-Line Text)
      • Area Code (migrated to One-Line Text)
      • Boolean (migrated to “null” data type)
      • Phone (migrated to One-Line Text)
    • Added a character limit of 255 to the custom field name
  • Added support for Grant and Prospect custom fields
  • Added support for the DAFpay tender type
    • DAFpay transactions can be retrieved but not edited due to restrictions with the Chariot interface.
  • Added support for the ACSS tender type (uses the existing ECheckPayment schema)
  • Added the parameter isCurrentEmployee to the GET memberships/{memberId}/subMembers endpoint

Fixed:

  • Fixed an issue where attempting to remove a custom field option via omitting it in a PUT customFields/{id} request did not remove the option as expected