Updates

Join our developers mailing list for updates on important changes to the Neon CRM API, custom objects, and other developer tools in Neon CRM.

Sign up for email alerts

API v2.5 Release Notes

April 13, 2023

This page details the new features, enhancements, and fixes in API v2.5, released on April 15th, 2023. Updated documentation for v2.5 will be published soon. Follow API v2 Versions for documentation updates. New: New activities endpoints are now available:PATCH /activitiesPUT /activitiesDELETE /activitiesNew payments endpoints are now available:POST /paymentsPOST /payments/{id}/refundPUT /payments/{id}/notes An origin object for origin category and detail…

Read More

API version 2.2 deprecation

March 15, 2023

On April 15th, 2023, we will be deprecating version 2.2 of the Neon CRM API v2. After this date, requests to API v2 that include the header NEON-API-VERSION: 2.2 will receive a HTTP 410 error, indicating that the API version is no longer valid. Learn more about versioning in API v2. If your application currently…

Read More

October 2022 Updates – Potential Webhooks Breaking Changes

October 17, 2022

As part of the October 22nd Neon CRM updates, we are fixing an issue where the transaction object was not properly returned in donation and membership webhooks. After this fix, it’s possible that existing integrations utilizing these webhooks may break due to expecting to return the transaction object in a certain format. You may need…

Read More

August 2022 API Release Notes

August 5, 2022

This page details the enhancements made to the Neon CRM API as part of the August 6th, 2022 release. API v2 New Endpoints are now available for activities: POST /activities GET /activities/{id} POST /activities/search GET /activities/search/outputFields GET /activities/search/searchFields Endpoints are now available for retrieving system users: GET /properties/systemUsers GET /properties/currentSystemUser A new endpoint is now…

Read More

API v2.4 Release Notes

May 12, 2022

This page details the new features, enhancements, and fixes in API v2.4, released on May 14th, 2022. Updated documentation for v2.4 will be published soon. Follow API v2 Versions for documentation updates. New Pending payments can now be created via transaction-related endpoints. date is now an available parameter within the POST /pledgepayments endpoint. The id parameter…

Read More

API version 2.1 deprecation

April 19, 2022

On Saturday, May 14, 2022, we will be deprecating version 2.1 of the Neon CRM API v2. After this date, requests to API v2 that include the header NEON-API-VERSION: 2.1 will receive a HTTP 410 error, indicating that the API version is no longer valid. Learn more about versioning in API v2. If your application currently specifies version…

Read More

December 2021 API Release Notes

December 18, 2021

This page details the enhancements and fixes made to the Neon CRM API as part of the December 18th, 2021 release. API v2 Fixed Fixed an issue where the State/Province and Territory fields could not both be populated when sending account-based requests Fixed an issue where an error would be returned when sending account-based requests…

Read More

August 2021 API Release Notes

August 21, 2021

This page details the enhancements and fixes made to the Neon CRM API as part of the August 21st, 2021 release. API v2 Fixed Updates the error messages returned when attempting requests which are not supported due to features not being included in your Neon CRM service plan.

Read More

API version 2.0 deprecation

June 15, 2021

On Saturday, July 24, 2021, we will be deprecating version 2.0 of the Neon CRM API v2. After this date, requests to API v2 that include the header NEON-API-VERSION: 2.0 will receive a HTTP 410 error, indicating that the API version is no longer valid. Learn more about versioning in API v2. If your application…

Read More

June 2021 API Release Notes

June 5, 2021

This page details the new features, enhancements, and fixes made to the NeonCRM API as part of the June 5th, 2021 release. API v2 Fixed Fixes an issue where the Wire Transfer tender type was not supported when sending requests.

Read More