Policies

Limitations of Use

We set and enforce limits on your use of the APIs (e.g. limiting the number of API requests that you may make or the number of users you may serve), at our sole discretion.

The current limitation in place is a quota for the number of concurrent server process threads a given customer may use. We do not currently enforce any quotas on total amount of bandwidth or number of API requests allowed in a given time period.

Please do not attempt to circumvent limitations documented with each API. These limitations are not intended to be punitive and exist to ensure all API users enjoy the same level of quality of service.

Downtime

Z2 Systems, Inc has had 99.95% uptime since 2004. We cannot always guarantee that this will be the case, but we will do everything in our power to ensure our system is always up and running. Our current uptime and related messages are always available on our System Availability page.

Support

If you discover an issue with an API method, please submit a ticket to our support center. We will do our best to resolve the issue in a timely manner. Many issues can be solved quickly, but some may need to be resolved as part of a scheduled development cycle. Z2 Systems, Inc has a product development cycle where new features are released approximately every four weeks, which is planned months in advance. API issues will be prioritized by our support and product development teams and scheduled accordingly.

We will support and test issues with API methods, but we cannot be responsible for issues related to code hosted on third-party servers (specifically that which is not written by our team). Assistance with outside code may be provided at our sole discretion, and may incur fees from our development team.

Change Management Policies

NeonCRM is constantly being improved, and we will continue to develop API capabilities. We reserve the right to create new API methods, modify the specifications for existing API methods, and deprecate (remove) existing API methods. We strive to keep our API community informed about these updates, and will attempt to inform users of changes as early as possible.

  • New API methods may be announced at any time prior to implementation.
  • Changes to existing API methods will be announced no later than 4 weeks prior to implementation.
  • Deprecation of API methods will be announced no later than 6 weeks prior to implementation.

Information about changes will be posted to our Developer Center website and to our API developer email list.

Communication with Z2 Systems, Inc.

We may send you certain communications in connection with your use of the APIs. Please ensure our development team has your current email address for communications. You may unsubscribe at any time through a link in the email.

Feedback

If you provide feedback or suggestions about our APIs, then we (and those we allow) may use such information without obligation to you.