Documentation

​
​

Development

User Acquisition

Monetization

Industry

Unity Services Web APIs

Open Unity Dashboard

Unity Services Web APIs

​
​
Unity Services Web APIs
  • Overview
  • Get started
Web API guides
  • Authentication
  • API lifecycle
  • Response status and error codes
  • Response headers
  • Unity Version Control CM API
    • Overview
    • How to use the API
    • Examples
    • Current limitations
  • Unity Version Control server API
Admin Settings
  • Access
  • Unity Releases
Analytics
  • Analytics
Identity and Access Management
  • Application and Deep Linking
Monetization
  • Monetize
Viewers and Collaboration
  • Annotations
  • Presence
Access
  • Access
Assets
  • Assets
Auth
  • Auth
Collaboration
  • Collaboration
Content Management
  • DataStreaming
  • Storage
  • Workflow Engine
DevOps
  • Automation
  • Build Automation
  • Unity Version Control
Growth
  • Ads Unified Platform
  • User Acquisition
Identity
  • SCIM
In-App Purchases
  • Webshop
Live Operations
  • Game Backend
  • Observability Logs
Multiplayer
  • Distributed Authority
  • Friends
  • Lobby
  • Matchmaker
  • Player Names
  • QoS Discovery
  • Relay Allocations
  • Session Observability
  • Vivox Voice and Text Chat
Unity
  • Projects and Apps
Unity Pipeline
  • Asset Pipeline
  1. Unity Services Web APIs

How to use the Unity Version Control client REST API

Learn how to start the Unity Version Control client REST API with the cm api command and troubleshoot the API server.
Read time 2 minutes
Last updated a month ago
The Unity Version Control Client REST API supports command execution through standard HTTP requests. Use any programming language capable of making HTTP calls to interact with the API. Make sure you use the right HTTP method and include the request body that the endpoint expects.
Note
If you're looking for a starting point, refer to our API client examples or these advanced examples on GitHub.
The 
cm api
command runs a simple, standalone HTTP server that listens for your API requests.
Warning
The user account that runs the 
cm api
command needs a valid Unity Version Control client configuration. To check your setup, run 
cm checkconnection
from your terminal.
Note
You'll find the 
cm
application in your Unity Version Control client directory:
  • Windows: 
    C:\Program Files\PlasticSCM5\client
  • macOS: 
    /Applications/PlasticSCM.app/Contents/Applications
  • Linux: 
    /opt/plasticscm5/client

Start the API

To start the client API HTTP server, run the 
cm api
command in your shell.
Note
To see all the options for the 
cm api
command, run 
cm api --help
.
Refer to the following syntax for the 
cm api
command:
cm api [(-p | --port) <portnumber>] [-r | --remote]
The following parameters are available:
  • -p | --port <portnumber>
    : Sets the port number for the API server. If you don't specify one, the default is 
    9090
    .
  • -r | --remote
    : Allows the server to accept remote connections from other hosts, not just the local machine.

Examples

To start the API on the default port (
9090
) and accept only local connections:
cm api
To start the API on port 
65000
and accept only local connections:
cm api -p 65000
To start the API on the default port (
9090
) and accept remote connections:
cm api -r
To start the API on port 
65000
and accept remote connections:
cm api -p 65000 -r
When the API server starts successfully, you'll receive the following message:
Unity VCS client REST API: Press <ENTER> to exit.

Troubleshooting

If the API server does not start

If the API fails to start, you'll receive a message like the following:
Unable to start the REST API listener. Please make sure that you have HTTP permissions for the current port and user.
The most common reason 
cm api
doesn't start is an unconfigured Unity Version Control user.
The user account running 
cm api
needs a valid client configuration for a Unity Version Control server (Cloud or on-premises). To check your configuration, run 
cm checkconnection
in a terminal with the same user account.
If the command returns the following message, your configuration is valid:
Test connection executed successfully
If you get a different message, follow the instructions in the output to fix your configuration.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Start the API

      • Examples

    • Troubleshooting

      • If the API server does not start