topic Re: Cannot create Private Locations via API because org access tokens cannot receive enough of permissions in Splunk Cloud Platform

Cannot create Private Locations via API because org access tokens cannot receive enough of permissions

jiriwetter — Tue, 09 Dec 2025 13:24:48 GMT

We are unable to create Private Locations in Splunk Observability Cloud using the documented API endpoint: POST /v2/synthetics/locations

Although my user account has the admin role in the organization, organization access tokens cannot be assigned the admin role. The UI allows selecting only these roles:

power
read_only
usage

According to the documentation, these are the only roles available when creating org-tokens with API scope.
Reference: https://help.splunk.com/en/splunk-observability-cloud/administer/authentication-and-security/authentication-tokens/org-access-tokens

However, the ability to manage Private Locations via API ?requires? admin-level permissions, which are not included in the power/read_only/usage roles. Therefore, the API call fails due to insufficient permissions, even though the user who created the token is an administrator.

User-role documentation: https://help.splunk.com/en/splunk-observability-cloud/administer/user-and-team-management/manage-roles

We would like to clarify:

Whether creating Private Locations using organization access tokens is officially supported.
If yes, how we can assign the necessary admin-level permissions to the token.
If not supported, whether this is an intended product limitation and whether support for this use case is planned.
Whether the recommended workaround is to rely on short-lived user session tokens instead.

This behavior prevents the automation of Private Location provisioning, even though the API endpoint is documented and intended for such use.

Re: Cannot create Private Locations via API because org access tokens cannot receive enough of permissions

livehybrid — Tue, 09 Dec 2025 10:32:38 GMT

Hi @jiriwetter

Where did you find the url /v2/private-locations ? Can you confirm that you are talking about Splunk Synthetic private location?

From what I understand, you need to first create the private location if not done so already:

curl -X POST "https://api.{REALM}.signalfx.com/v2/synthetics/locations" \ -H "Content-Type: application/json" \ -H "X-SF-TOKEN: <value>" \ -d '{ "location": { "id": "private-data-center", "label": "Data Center" } }'

You would then request a runner token for that location:

curl -X POST "https://api.{REALM}.signalfx.com/v2/synthetics/locations/{location_id}/runner_tokens" \ -H "Content-Type: application/json" \ -H "X-SF-TOKEN: <value>"

You would then use the token received to create you private location runner: https://help.splunk.com/en/splunk-observability-cloud/monitor-end-user-experience/synthetic-monitoring/advanced-test-configurations/private-locations

🌟 Did this answer help you? If so, please consider:

Adding karma to show it was useful
Marking it as the solution if it resolved your issue
Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

Re: Cannot create Private Locations via API because org access tokens cannot receive enough of permissions

jiriwetter — Tue, 09 Dec 2025 14:48:38 GMT

@livehybrid That's my mistake. I fixed it - the correct path is /v2/synthetics/locations. However, this does not change anything in the assignment.

curl -X POST "https://api.eu1.signalfx.com/v2/synthetics/locations" -H "Content-Type: application/json" -H "X-SF-TOKEN: **********" -d '{"location":{"id":"private-data-center","label":"Data Center"}}' {"errors":["Not Authorized"]}

The token has all the available roles listed in the documentation above.

Edit: I just want to add that listing the existing ones works. So the token itself is fine, at least for this operation.