Pins or unpins all symbol files of an app version. A pinned file is not deleted automatically when the symbol file storage runs out of space.
The request produces an application/json payload.
| PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/symfiles/{applicationId}/{packageName}/{os}/{versionCode}/{versionName}/pinning |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/symfiles/{applicationId}/{packageName}/{os}/{versionCode}/{versionName}/pinning |
To execute this request, you need an access token with DssFileManagement scope.
To learn how to obtain and use it, see Tokens and authentication.
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| applicationId | string | The UUID of the required mobile or custom application. It can be found in the Instrumentation Wizard of your app. | path | required |
| packageName | string | The CFBundleIdentifier (iOS) or the package name (Android) of the required mobile app. | path | required |
| os | string | The operating system of the required app.
| path | required |
| versionCode | string | The version code (Android) / CFBundleVersion (iOS) of the required app. | path | required |
| versionName | string | The version name (Android) / CFBundleShortVersionString (iOS) of the required app. | path | required |
| body | Symbol | The JSON body of the request. Contains the pinning status to set. | body | optional |
SymbolFilePinning object| Element | Type | Description | Required |
|---|---|---|---|
| pinned | boolean | The pinning status of the file: | required |
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"pinned": true}
| Code | Type | Description |
|---|---|---|
| 204 | - | Success. The pinning status of the filed has been updated. Response doesn't have a body. |
| 400 | Error | Failed. The input is invalid. |
We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.
The request consumes an application/json payload.
| PUT | SaaS | https://{your-environment-id}.live.dynatrace.com/api/config/v1/symfiles/{applicationId}/{packageName}/{os}/{versionCode}/{versionName}/pinning/validator |
| Environment ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/config/v1/symfiles/{applicationId}/{packageName}/{os}/{versionCode}/{versionName}/pinning/validator |
To execute this request, you need an access token with DssFileManagement scope.
To learn how to obtain and use it, see Tokens and authentication.
| Code | Type | Description |
|---|---|---|
| 204 | - | Validated. The submitted body is valid. Response does not have a body. |
| 400 | Error | Failed. The input is invalid. |