Redis API Endpoints
This section documents all Redis Endpoints for real-time time data retrieval.

🔍 Pokéstops
Endpoint:
/api/redis/get_cached_pokestopsDescription:
Retrieves all Pokéstops counts per Area based on your Koji Geofences from Golbat SQL Database.
Examples:


🌐 Koji Geofences
Endpoint:
/api/redis/get_cached_geofencesDescription:
Retrieves all Areas Geofences with name, coordinates and timezone offset.
Examples:


👻 Pokémon Counter Series
Endpoint:
/api/redis/get_pokemon_counterseriesDescription:
Retrieves counter series for Pokémon (totals, time-to-hatch (TTH), and weather counters) with configurable intervals (hourly, weekly, or monthly).
Query Parameters:
counter_type:totals (Pokémon totals per id/form if specified per Area or Global).
tth (Provides information into time ranges/buckets for each Pokémon Despawn Timer Per Area or Global).
weather (Aggregates Pokémon information into IV ranges/buckets and their total number for each type of weather condition per Area or Global).
interval:hourly
weekly
monthly - weather only
start_time,end_timeISO or relative times) addressed here.mode(sum, grouped, surged - note: surged only works with hourly).area(e.g., global or specific area from your Koji Geofences).metric:Totals:
iv100,iv0,pvp_little,pvp_great,pvp_ultra,shiny.Weather: Based on pogo data
0-9I think.TTH: allowed values are e.g.
0_5,5_10, etc.
pokemon_id(all or specific Pokémon ID).form(all or specific form ID).response_format(json, text).
Examples & Response Formats:





👹 Raid Counter Series
Endpoint:
/api/redis/get_raids_counterseriesDescription:
Retrieves raid counter series (totals) with options for hourly or weekly aggregation.
Query Parameters:
Similar to the Pokémon endpoint.
Specific parameters:
raid_pokemon(Raid Pokémon ID or all)raid_form(Raid Pokémon Form ID or all)raid_level(Raid level or all)raid_costume(Raid Pokémon Costume ID or all)raid_is_exclusive(Raid Exclusive 0 - 1 or all)raid_ex_eligible(Raid Ex Eligible 0 - 1 or all)
Examples:

🕴️ Invasion Counter Series
Endpoint:
/api/redis/get_invasions_counterseriesDescription:
Retrieves invasion counter series (totals) for hourly or weekly intervals.
Query Parameters:
Similar to all other Counter Series.
Specific parameters:
display_typeInvasion Display Type ID or allcharacterInvasion Character ID or allgruntInvasion Grunt ID or allconfirmedLine-up confirmed, 0 - 1 or all
Examples:

🔎 Quest Counter Series
Endpoint:
/api/redis/get_quest_counterseriesDescription:
Retrievies Quest Counter Series (totals) aggregated hourly or weekly.
Query Parameters:
Similar to all other Counter Series.
Specific parameters:
with_artrue(AR),false(Normal) or allreward typesbased in AR or Normal:_typeQuest Type ID or all_item_idQuest Item ID or all_item_amountQuest Item Amount or all_poke_idQuest Pokémon ID or all_poke_formQuest Pokémon Form or all
Examples:

👻 Pokémon TimeSeries
Endpoint:
/api/redis/get_pokemon_timeseriesDescription:
Provides timeseries data for Pokémon counters filtered by Pokémon ID and form.
Query Parameters:
Similar to Counter Series, except there are no Counter Type.
Query for individual Pokémons and their forms.
Examples:


👻 Pokémon TTH TimeSeries
Endpoint:
/api/redis/get_pokemon_tth_timeseriesDescription:
Retrieves timeseries data for time-to-hour (TTH) values with filtering for specific TTH buckets/ranges.
Query Parameters:
Similar to Counter Series.
Examples:

👹 Raid TimeSeries
Endpoint:
/api/redis/get_raid_timeseriesDescription:
Retrieves timeseries data for raids, allowing filtering by raid Pokémon, form and level.
Query Parameters:
Similar to Counter Series.
Query for individual pokémons/forms and raid levels.
Examples:

🕴️Invasion TimeSeries
Endpoint:
/api/redis/get_invasion_timeseriesDescription:
Provides timeseries data for invasions allowing filtering by display, grunt and confirmed.
Query Parameters:
Similar to Counter Series.
Additions:
display
grunt
confirmed
Allows you to query for individual display type, grunt and if their line ups have been confirmed.
Examples:


🔎 Quest TimeSeries
Endpoint:
/api/redis/get_quest_timeseriesDescription:
Provides timeseries data for quests, allowing filtering based on quest mode and type.
Query Parameters:
Similar to Counter Series.
Additions:
quest_mode
quest_type
Allows you to query for individual quest_mode and quest_type.
Examples:

Last updated