GET /techs/{player_identifier}

Endpoint: GET /v1/pdapi/techs/<player_identifier>

Auth: Bearer token

Permission: REST.Techs.Read

Purpose

Lists technology information for a player. Technology identifiers can be searched on paldeck.cc/technology.

None.

No request body.

Field	Type	Description
`Meta`	object	Technology count metadata for the target player.
`Techs`	object	Technology data for the target player.

Meta object schema:

Field	Type	Description
`PlayerUID`	string	Player UID used by Palworld save data.
`Player`	string	Player identifier supplied in the request path.
`UnlockedCount`	integer	Number of currently unlocked technologies.
`LockedCount`	integer	Number of currently locked technologies.
`TotalCount`	integer	Total number of recipe technologies known to the player data.

Techs object schema:

Field	Type	Description
`Unlocked`	string[]	Technology IDs currently learned by the player.

Error bodies use this shape:

{
    "Error": {
        "Code": "ERROR_CODE",
        "Message": "Human-readable message",
        "Details": {}
    }
}

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 target player, player account, technology data, or technology table could not be resolved.
`500`	`REQUEST_TIMEOUT`	The internal game-thread callback did not complete within 5 seconds.

GET /v1/pdapi/techs/gdk_2533274812345678

GET /v1/pdapi/techs/f0a1c3e9-7d5b-4a28-8c33-411fdc2e6b74