Show data needed for API more clearly in meshStack UI | Feature Requests

Show data needed for API more clearly in meshStack UI

Jelle den Burger

Non-admin users do not have access to certain information that is mandatory for using the API. For example if you want to create a new tenant in a project, you need a 'fullPlatformIdentifier' and 'landingZoneIdentifier' which cannot be found in the UI.

January 20, 2025

Johannes Rudolph

Update: Project Identifiers Now Visible in Workspace Overview in meshStack v2026.18.0

We've added project identifiers to the workspace overview project list:

Project identifier visible:
Each project now shows its identifier alongside its display name.
Click to copy:
Click the identifier to instantly copy it to your clipboard — no more digging through settings.

See meshStack v2026.18.0 for details.

We know there are still other identifiers and API parameters that are hard to discover (e.g.

fullPlatformIdentifier

marketplaceIdentifier

). This ticket remains open and we'll continue addressing these gaps. If you have a specific identifier or parameter that's still hard to find, please share it here — it helps us prioritize what to tackle next. You can also reach us at support@meshcloud.io.

Johannes Rudolph

Update: Workspace ID now clearly displayed and copyable

meshStack v2026.13.0 makes workspace IDs (and many other identifiers) much easier to work with:

Workspace IDs are now displayed using a consistent identifier widget
Click the identifier to copy it to your clipboard instantly
Same improvement applies to project, tenant, platform, and building block UUIDs
See meshStack v2026.13.0 for details

We will keep this request open as there a still other valid scenarios described here in the comments that we should still address. Thanks so much for the detailed feedback so far from everyone who contributed.

Sergi Domingo Basora

Just for completion, I found a similar situation today: when creating a Service instance via API (POST request), I struggled finding the right value for the marketplaceIdentifier parameter. It turned out that the identifier was not the marketplace tenant identifier (which can be found in the Cloud Portal UI), but rather, it was a hidden identifier that can only be found by querying an existing Service Instance via a GET request. I had to open a support ticket to sort this out.

Sergi Domingo Basora

Another example:
The user cannot check the values of tag keys, needed for creating projects via API. (In the project creation form, only the tag display name can be seen). To discover these keys, hey have to create a project manually in the Cloud Portal UI, then go to project Settings > Tags and check the tag key that was applied to that project.
Given that some tags are required in our environment, it is difficult for the user to tackle this scenario. The error responses for invalid tag values are also quite unclear when an invalid API request is sent.

Jelle den Burger

Sergi Domingo Basora Thanks Sergi for that example. We will consider that too when building a better experience.

Jelle den Burger

updated the status to

open