Version: 1.0.0 Workflow: get-player-and-planets Category: Query
Get player information and their planets - Multi-step API workflow.
None.
webapp-player-by-idGEThttp://localhost:8080/api/player/{player_id}Parameters:
| Parameter | Example Value |
|---|---|
| player_id | 1-11 |
Data Extraction:
player_id from response.player.idguild_id from response.guild.idExpected Response:
200schemas/responses.md#/definitions/WebappPlayerResponseError Handling:
| Status | Action |
|---|---|
| 404 | Player not found - verify player_id |
| 500 | Server error - retry with exponential backoff |
planet-by-playerGEThttp://localhost:1317/structs/planet_by_player/{playerId}Parameters:
| Parameter | Value |
|---|---|
| playerId | `` |
Data Extraction:
planets from response.PlanetExpected Response:
200schemas/entities.md#/definitions/Planet[]Error Handling:
| Status | Action |
|---|---|
| 404 | No planets found for player (may be empty array) |
| 500 | Server error - retry with exponential backoff |
{
"player": "",
"guild": "",
"planets": ""
}
This workflow demonstrates chaining API calls where step 2 depends on data from step 1.