Support
What Business NXT API support service covers
We provide support for:
- API endpoint usage
- Addressing API feature requests and bug reports
- Providing code examples and documentation for API usage
- API troubleshooting
Before contacting API Support, please first check the API documentation and training materials available on Visma Learning Universe and Discord API Community. Your question might have been answered already.
What is not covered by API support
We don’t provide support for:
- Assistance in writing code and general code debugging for third-party software and integrations and applications
- Troubleshooting and technical support for external software and applications written by third parties
- Business NXT UI related topics
Support methods
When seeking support, please be prepared to provide information on your attempts to debug and isolate the Business NXT API problem.
Information needed:
- GraphQL query
- Returned response body
- Request Trace ID (see Tracing query execution)
These details are crucial for API Support consultants to help diagnose your issue. For example, we may ask you to provide a simple test case that demonstrates the problem or replicate the problem outside of your application.
If we cannot diagnose a problem with the APIs, we may be limited to providing suggestions on how you can resolve the issue.
For more details on how to report cases, please view Troubleshooting and reporting.
Support channels
Business NXT API Support channels:
- The forum Discord API Community
- For One-to-one email support, Partners can create tickets via the Partner Portal while others can send email to cloud.api.support@visma.com
- One-to-one consulting meeting is available with hourly charges via the Partner Portal and cloud.api.support@visma.com
Section Content
Troubleshooting and reporting
Steps to troubleshoot and report issues for timely resolution.
Discord Community
Join our Discord community! A peer-to-peer platform where you can connect and share knowledge with others. Join, contribute, and make the most of it. High engagement will allow integrators to support one another and create better conditions for our APIs to evolve.