Preview a Marketing UTM URL
Applies the Space’s saved naming rules and preserves unrelated query parameters and the URL fragment. No link is saved and the destination is never fetched.
/api/v1/marketing/utm/previewWorkspace automation for approved Dashio products. Each token is scoped to one Space and independently granted operations. Requests spend shared minute credits, and selected operation groups also share hourly quotas.
Required token scope is marketing:utm:preview. Scopes are independent.
This operation uses 1 credit from a shared budget of 60 credits per token and 300 per Space each UTC minute.
Run these examples on a trusted server with DASHIO_API_TOKEN configured. Use a private terminal when inspecting response data. Examples send one request with a bounded timeout and do not retry automatically.
Authentication
Dashio developer token (HTTP Bearer) API authentication guide
Path parameters
None documented.
Query parameters
None documented.
Header parameters
None documented.
Request body
application/json · Required
JSON up to 8 KiB. Supply the original destination and UTM parameters.
destinationUrlstring (uri)RequiredAbsolute HTTP or HTTPS URL without embedded credentials. Maximum length: 2048.
parametersobjectRequiredNo field description supplied.
Responses
Headers on every response
X-Request-Idstring (uuid)OptionalServer-generated ID to include in a support request.
200
Generated URL, applied values and names of overwritten UTM parameters.
Response headers
RateLimit-LimitintegerOptionalPer-token capacity in the reported gateway window, expressed in requests of this operation. A shared Space budget also applies. Present when the request reaches the authenticated gateway. Minimum: 1.
RateLimit-RemainingintegerOptionalRequests of this operation remaining under the current token, Space and applicable operation-group quotas. Present when the request reaches the authenticated gateway. Minimum: 0.
RateLimit-ResetintegerOptionalUnix timestamp in seconds when the reported gateway quota resets. Present when the request reaches the authenticated gateway. Minimum: 0.
application/json
urlstring (uri)RequiredMaximum length: 2048.
appliedParametersobjectRequiredNo field description supplied.
overriddenKeysarray of stringRequiredMaximum items: 5.
400
Invalid URL, query, parameters, or resulting URL length.
application/json
statusCodeintegerRequiredMinimum: 400. Maximum: 599.
statusMessagestringOptionalA safe explanation suitable for display.
dataobjectRequiredNo field description supplied.
401
Developer token is missing or invalid.
Response headers
WWW-AuthenticatestringOptionalBearer authentication challenge. A rejected token can include the invalid_token error.
application/json
Uses the same response body schema as HTTP 400.
402
An active Marketing entitlement is required.
application/json
Uses the same response body schema as HTTP 400.
403
The token lacks the UTM preview permission.
application/json
Uses the same response body schema as HTTP 400.
415
Use an application/json request body.
application/json
Uses the same response body schema as HTTP 400.
429
The token or Space request budget is exhausted. Edge traffic limits can also return 429.
Response headers
RateLimit-LimitintegerOptionalPer-token capacity in the reported gateway window, expressed in requests of this operation. A shared Space budget also applies. Present when the request reaches the authenticated gateway. Minimum: 1.
RateLimit-RemainingintegerOptionalRequests of this operation remaining under the current token, Space and applicable operation-group quotas. Present when the request reaches the authenticated gateway. Minimum: 0.
RateLimit-ResetintegerOptionalUnix timestamp in seconds when the reported gateway quota resets. Present when the request reaches the authenticated gateway. Minimum: 0.
Retry-AfterintegerOptionalSeconds to wait before retrying, when the limiting policy supplies a retry time. Minimum: 1.
application/json
Uses the same response body schema as HTTP 400.
503
The saved naming policy is temporarily unavailable.
application/json
Uses the same response body schema as HTTP 400.
Was this helpful?