---
sourceDocument: Xanadu API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/api-reference

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Enable versioning for a scripted REST API

# Enable versioning for a scripted REST API {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Enable versioning for a scripted REST API to provide multiple versions of the API
while maintaining compatibility with existing integrations.

## Before you begin

There must be a scripted REST API defined before you can enable versioning.

Role
required: web_service_admin

## Procedure

1. Navigate to AllSystem Web ServicesScripted REST APIs.
2. Select a scripted REST API.
3. Under Related Links, click Enable versioning.  
   The Enable versioning pop up appears. The Make version v1 default check box is selected by default.
4. **Optional:** Clear the Make version v1 default check box to enable versioning without a default version.  
   Versioned APIs without a default version are accessible only by using the version-specific URI. Make version v1 default, or select a different version as default after you enable versioning.
5. Click OK.  
   The Versioning embedded list is added to the Scripted REST Service form. You can add new versions or control which version is default from this list.
{#t_EnableVersioning__steps_xx4_45p_ls}
* **[Add a version to a scripted REST API](https://servicenow-prod.fluidtopics.net/TdJzLRkme7sJhNFUkd0tcA)**   
  Add a new version to a versioned scripted REST API to define new API behavior without impacting older versions.

*[\>]: and then