Mobile Symbolication API - PUT pin files
Pin or unpin all symbolication files of a app version. A pinned file will not be deleted automtically, when running out of space.
The request produces an application/json payload.
| PUT |
|
Authentication
To execute this request, you need the Mobile symbolication file management (DssFileManagement) permission assigned to your API token. To learn how to obtain and use it, see Tokens and authentication.
Parameters
| Parameter | Type | Description | In | Required |
|---|---|---|---|---|
| applicationId | string |
The application id used in Dynatrace of the app which should be (un)pinned |
path | required |
| packageName | string |
The CFBundleIdentifier (iOS) or the package name (Android) which identifies the app associated with the files to be (un)pinned |
path | required |
| os | string |
The operating system for which the files will be (un)pinned |
path | required |
| versionCode | string |
The version code (Android) / CFBundleVersion (iOS) the file belongs to |
path | required |
| versionName | string |
The version name (Android) / CFBundleShortVersionString (iOS) the file belongs to |
path | required |
| body | SymbolFilePinning |
JSON body of the request, containing the pinning status to set. |
body | optional |
Body format
The SymbolFilePinning object
| Element | Type | Description | Required |
|---|---|---|---|
| pinned | boolean |
New setting for file pinning. True to pin the file, false to unpin 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. See the Example expandable section for working sample request.
{
"pinned": true
}
Response
Response codes
| Code | Description |
|---|---|
| 204 | Success. The pinning status of the filed has been updated. Response doesn't have a body. |
| 400 | Failed. The input is invalid. |
Response body
A successful request doesn't return any content.
Validate payload
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 |
|
Authentication
To execute this request, you need the Mobile symbolication file management (DssFileManagement) permission assigned to your API token. To learn how to obtain and use it, see Tokens and authentication.
Response
Response codes
| Code | Description |
|---|---|
| 204 | Validated. The submitted body is valid. Response does not have a body. |
| 400 | Failed. The input is invalid. |
Response body
A successful request doesn't return any content.