We're letting API users know early about changes coming to the Visibuild Core API over the next few months, so you have plenty of time to plan.
What's happening now
We've recently promoted Defect from an Issue subtype to its own top-level Visi type in the web and mobile apps. The API has not changed — your existing integrations and ETL pipelines will continue to work exactly as they do today. No immediate action is required.
What's coming
In the next month or two, we'll release V2 of the core API. V2 will include:
Updated Visi category structure reflecting Defect as a top-level type
Unifying Issue types
Support for custom Visi types (a major upcoming feature)
We'll publish full V2 documentation, migration notes, and a detailed changelog closer to release.
What this means for your integrations
V1 will keep working when V2 launches — there is no hard cutover
V1 will be deprecated a few months after V2 is released, giving you a clear window to migrate at your own pace
Your existing ETL pipelines will continue to function in the meantime
We'll provide a migration guide with field-by-field mapping when V2 is available
Need help or have questions?
If you'd like to discuss how V2 will affect your specific integration, reach out to your account contact or reply to this article. We'll update this page as the V2 release approaches with concrete details, endpoint references, and migration steps.