POST /forgettech/{player_identifier}
Endpoint: POST /v1/pdapi/forgettech/<player_identifier>
Auth: Bearer token
Permission: REST.Techs.Forget
Purpose
Forgets one, many, or all technologies for a player.
Path parameters
player_identifier:UserIdorPlayerUIDfor the target player.
Query parameters
None.
Request body
Technology can be a single TechID, the string "All", or an array of TechID strings. Do not put "All" inside an array.
Response schema
200 response schema
| Field | Type | Description |
|---|---|---|
ForgottenCount |
integer | Number of technologies removed from the player. |
Forgotten |
string[] or string | Removed technology IDs, or All when every unlocked technology was removed. |
Skipped |
string[] | Technology IDs skipped because they were not unlocked. |
Error responses
Error bodies use this shape:
| HTTP | Error code | When it happens |
|---|---|---|
401 |
INVALID_TOKEN |
The Authorization header is missing, malformed, or does not match a configured bearer token. |
403 |
MISSING_PERMISSION |
The token is valid, but it does not include this endpoint permission. |
400 |
INVALID_JSON |
A request body was supplied, but it could not be parsed as JSON. |
400 |
REQUEST_FAILED |
The game-thread callback threw an exception, or a shared player/resource resolver failed. |
500 |
REQUEST_TIMEOUT |
The internal game-thread callback did not complete within 5 seconds. |
400 |
INVALID_REQUEST |
Technology is missing, or it is not a string/array in the expected format. |
400 |
VALIDATION_FAILED |
The Technology array contains a non-string, All, or an invalid technology identifier. |
Examples
Forget one technology for a GDK player
Forget several technologies by PlayerUID
Forget all technologies for a Steam player
Scenarios
- Remove a technology granted by mistake.
- Reset a test account with
"All". - Confirm the current state with GET /techs before and after the request.