Automate Visualstudio VSOnline

What Visualstudio VSOnline is

Public APIs for managing VS Codespaces

API host: online.visualstudio.com

What HumDay can do in Visualstudio VSOnline

122 documented operations change something in Visualstudio VSOnline. The 74 most useful are listed here.

• POSTUpdate tunnelauth/tunnelauth
• POSTUpdate Secrets/api/v1/Secrets
• POSTUpdate HeartBeat/api/v1/HeartBeat
• POSTUpdate Environments/api/v1/Environments
• POSTUpdate AgentTelemetry/api/v1/AgentTelemetry
• DELETEDelete UserSubscriptions/api/v1/UserSubscriptions
• POSTUpdate UserSubscriptions/api/v1/UserSubscriptions
• PATCHUpdate folder/api/v1/Environments/{environmentId}/folder
• POSTUpdate notify/api/v1/Environments/{environmentId}/notify
• POSTUpdate delete/api/v2/prebuilds/delete
• POSTUpdate templates/api/v2/prebuilds/templates
• POSTUpdate standalone/api/v1/AgentTelemetry/standalone
• DELETEDelete tenantId/api/v1/Tenant/{tenantId}
• PUTUpdate tenantId/api/v1/Tenant/{tenantId}
• DELETEDelete secretId/api/v1/Secrets/{secretId}
• PUTUpdate secretId/api/v1/Secrets/{secretId}
• DELETEDelete VnetPoolDefinitions/api/v1/GenevaActions/VnetPoolDefinitions
• POSTUpdate VnetPoolDefinitions/api/v1/GenevaActions/VnetPoolDefinitions
• DELETEDelete environmentId/api/v1/Environments/{environmentId}
• PATCHUpdate environmentId/api/v1/Environments/{environmentId}
• POSTUpdate updatemaxversions/api/v2/prebuilds/templates/updatemaxversions
• POSTUpdate target/api/v1/GenevaActions/Pools/{target}
• POSTUpdate start/api/v1/Environments/{environmentId}/start
• POSTUpdate export/api/v1/Environments/{environmentId}/export
• POSTUpdate archive/api/v1/Environments/{environmentId}/archive
• PATCHUpdate restore/api/v1/Environments/{environmentId}/restore
• PUTUpdate secrets/api/v1/Environments/{environmentId}/secrets
• POSTUpdate target/api/v1/GenevaActions/Configuration/{target}
• POSTUpdate shutdown/api/v1/Environments/{environmentId}/shutdown
• POSTUpdate change resource deletion setting/api/v1/GenevaActions/Pools/change-resource-deletion-setting
• POSTUpdate callback/api/v1/Environments/{environmentId}/_callback
• POSTUpdate delete/api/v1/GenevaActions/Prebuilds/pools/delete
• DELETEDelete environmentId/api/v1/GenevaActions/Environments/{environmentId}
• POSTUpdate refresh profile telemetry properties/api/v1/GenevaActions/Privacy/refresh-profile-telemetry-properties
• POSTUpdate instances/api/v1/Prebuilds/pools/{poolId}/instances
• PUTUpdate instances/api/v1/Prebuilds/pools/{poolId}/instances
• POSTUpdate createorupdatesettings/api/v1/GenevaActions/Prebuilds/pools/createorupdatesettings
• POSTUpdate writeDelegates/api/v1/Tokens/plans/{planName}/writeDelegates
• POSTUpdate writeCodespaces/api/v1/Tokens/plans/{planName}/writeCodespaces
• POSTUpdate readAllCodespaces/api/v1/Tokens/plans/{planName}/readAllCodespaces
• POSTUpdate rotate pool/api/v1/GenevaActions/Pools/{poolCode}/rotate-pool
• POSTUpdate deleteAllCodespaces/api/v1/Tokens/plans/{planName}/deleteAllCodespaces
• POSTUpdate updatestatus/api/v2/prebuilds/templates/{templateId}/updatestatus
• DELETEDelete poolName/api/v1/tenant/{tenantId}/Pool/{poolName}
• PATCHUpdate poolName/api/v1/tenant/{tenantId}/Pool/{poolName}
• PUTUpdate poolName/api/v1/tenant/{tenantId}/Pool/{poolName}
• PUTUpdate archive/api/v1/GenevaActions/Environments/{environmentId}/archive
• PUTUpdate shutdown/api/v1/GenevaActions/Environments/{environmentId}/shutdown
• DELETEDelete port/api/v1/Environments/{environmentId}/ports/{port}
• PUTUpdate port/api/v1/Environments/{environmentId}/ports/{port}
• POSTUpdate under investigation/api/v1/GenevaActions/Resources/{resourceId}/under-investigation
• DELETEDelete key/api/v1/GenevaActions/Configuration/{target}/{key}
• DELETEDelete poolGroupName/api/v1/tenant/{tenantId}/PoolGroup/{poolGroupName}
• PATCHUpdate poolGroupName/api/v1/tenant/{tenantId}/PoolGroup/{poolGroupName}
• PUTUpdate poolGroupName/api/v1/tenant/{tenantId}/PoolGroup/{poolGroupName}
• POSTUpdate logs/api/v1/GenevaActions/Environments/{environmentId}/upload/running/vm/logs
• DELETEDelete branchName/api/v2/prebuilds/repository/{repoId}/branch/{branchName}
• DELETEDelete vmName/api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName}
• PUTUpdate vmName/api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName}
• POSTUpdate stop/api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName}/stop
• POSTUpdate start/api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName}/start
• POSTUpdate resourceReadBegin/api/v1/subscriptions/{subscriptionId}/providers/Microsoft.VSOnline/plans/resourceReadBegin
• POSTUpdate resourceReadBegin/api/v1/subscriptions/{subscriptionId}/providers/Microsoft.Codespaces/plans/resourceReadBegin
• PUTUpdate SubscriptionLifeCycleNotification/api/v1/subscriptions/{subscriptionId}/providers/Microsoft.VSOnline/plans/SubscriptionLifeCycleNotification
• PUTUpdate SubscriptionLifeCycleNotification/api/v1/subscriptions/{subscriptionId}/providers/Microsoft.Codespaces/plans/SubscriptionLifeCycleNotification
• POSTUpdate resourceReadBegin/api/v1/subscriptions/{subscriptionId}/providers/GitHub.Network/{resourceType}/resourceReadBegin
• PUTUpdate SubscriptionLifeCycleNotification/api/v1/subscriptions/{subscriptionId}/providers/GitHub.Network/{resourceType}/SubscriptionLifeCycleNotification
• POSTUpdate resend/api/v1/GenevaActions/Billing/resend
• POSTUpdate resourceReadBegin/api/v1/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.VSOnline/plans/resourceReadBegin
• POSTUpdate resourceReadBegin/api/v1/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Codespaces/plans/resourceReadBegin
• PUTUpdate resourceName/api/v1/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.VSOnline/plans/{resourceName}
• POSTUpdate deleteDelegates/api/v1/subscriptions/{subscriptionId}/{resourceGroup}/providers/Microsoft.VSOnline/plans/{resourceName}/deleteDelegates
• PUTUpdate resourceName/api/v1/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Codespaces/plans/{resourceName}
• POSTUpdate deleteDelegates/api/v1/subscriptions/{subscriptionId}/{resourceGroup}/providers/Microsoft.Codespaces/plans/{resourceName}/deleteDelegates

What HumDay can read from Visualstudio VSOnline

These are the operations a schedule or a trigger can watch.

• GETRead health/health
• GETRead warmup/warmup
• GETRead tunnelauth/tunnelauth
• GETRead Sas/api/v1/Sas
• GETRead Secrets/api/v1/Secrets
• GETRead Locations/api/v1/Locations
• GETRead Environments/api/v1/Environments
• GETRead default/api/v1/pools/default
• GETRead family/api/v1/Agents/{family}
• GETRead tenantId/api/v1/Tenant/{tenantId}
• GETRead location/api/v1/Locations/{location}
• GETRead environmentId/api/v1/Environments/{environmentId}
• GETRead portInfo/api/v1/Tunnel/{environmentId}/portInfo
• GETRead state/api/v1/Environments/{environmentId}/state
• GETRead environmentId/api/v1/Prebuilds/template/{environmentId}
• GETRead archive/api/v1/Environments/{environmentId}/archive
• GETRead updates/api/v1/Environments/{environmentId}/updates
• GETRead environmentId/api/v1/GenevaActions/Environments/{environmentId}
• GETRead heartbeattoken/api/v1/Environments/{environmentId}/heartbeattoken
• GETRead poolName/api/v1/tenant/{tenantId}/Pool/{poolName}
• GETRead key/api/v1/GenevaActions/Configuration/{target}/{key}
• GETRead poolGroupName/api/v1/tenant/{tenantId}/PoolGroup/{poolGroupName}
• GETRead Vm/api/v1/tenant/{tenantId}/pool/{poolName}/Vm
• GETRead targetBlob/api/v1/GenevaActions/Environments/{environmentId}/archived_storage_sas/{targetBlob}
• GETRead vmName/api/v1/tenant/{tenantId}/pool/{poolName}/Vm/{vmName}
• GETRead correlation/internal/Netmon/correlation

How automating Visualstudio VSOnline works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Visualstudio VSOnline account.
4. Grant access, then go live. You approve the specific Visualstudio VSOnline operations it may use — and only those.

Automate Visualstudio VSOnline with these

• OData for namespace microsoft.graph11412 operations
• GitHub811 operations
• Atlassian The Jira Cloud platform474 operations
• Gitlab358 operations
• JIRA 7.6.1324 operations
• Appcenter App Center Client323 operations
• Gitea .321 operations
• Bitbucket292 operations
• Keycloak Admin281 operations
• Apple App Store Connect251 operations
• Files.com222 operations
• Vmware vRealize Network Insight Reference161 operations

Categories

• Developer tools
• Collaboration

Questions about Visualstudio VSOnline automation

Can HumDay connect to Visualstudio VSOnline?

Yes. HumDay reads Visualstudio VSOnline's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 152 operations are documented.

Do I need to write code to automate Visualstudio VSOnline?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Visualstudio VSOnline account.

What can HumDay do in Visualstudio VSOnline?

122 of the 152 documented operations change something in Visualstudio VSOnline, and 30 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Visualstudio VSOnline account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Visualstudio VSOnline is held behind that approval.

Where this came from

The operations above are read from a published API description for Visualstudio VSOnline at online.visualstudio.com/api/v1/swagger. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.