The current POST /api/v1/datasource endpoint (documented at https://tools4ever.stoplight.io/docs/helloid/08b4e750c6f76-add-or-update-a-data-source) does not support setting or retrieving the agent pool configuration for a datasource.

Current behavior:

POST /api/v1/datasource accepts agentPoolGUID and runInCloud in the request body without returning an error (HTTP 200/201), but the values are silently ignored and not persisted.

GET /api/v1/datasource/named/{DataSourceName} and GET /api/v1/datasource/{DataSourceGUID} do not return agentPoolGUID.

Investigation via browser devtools reveals that the HelloID UI uses an internal microservice endpoint (https://service-automation-prod-we.helloid.cloud/service/datasource/api/datasource) with Bearer token authentication to persist agent pool settings — this endpoint is not part of the public API and is not suitable for use in automation scripts.

Expected behavior:

POST /api/v1/datasource should persist agentPoolGUID and runInCloud when included in the request body.

GET /api/v1/datasource/named/{DataSourceName} and GET /api/v1/datasource/{DataSourceGUID} should return agentPoolGUID and runInCloud in the response body.

Use case:

We manage HelloID Delegated Forms via automated createform.ps1 deployment scripts. After importing a form, a post-import.ps1 script should be able to configures the agent pool on PowerShell datasources — this is required for on-premises connectivity (e.g. Active Directory, Exchange). Without API support for agentPoolGUID, this step cannot be automated and requires manual configuration in the UI after every deployment.

Requested additions to the response body:

{

"dataSourceGUID": "...",

"name": "...",

"agentPoolGUID": "2w3e4r5t-3h4b-5678-81d2-0o0b8v7c6x",

"agentPoolName": "Tenant_Agent_Pool",

"runInCloud": false

}