├── Tools-Maps.md ├── Maps.md ├── Data.md ├── Content-NPC.md ├── Content-Fate.md ├── Content-Item.md ├── Content-Leve.md ├── Content-Mount.md ├── Content-Emote.md ├── Content-Enemy.md ├── Content-Quest.md ├── Content-Title.md ├── Content-Achievement.md ├── Content-Minion.md ├── Content-Recipe.md ├── Content-Status.md ├── Content-Weather.md ├── Content-Shop.md ├── Content-Action.md ├── Content-Instance.md ├── Content-Gathering.md ├── Content-Placename.md ├── CHANGELOG-V3.md ├── Tools-Lore-Finder.md ├── Character.md ├── Search-Order.md ├── README.md └── Search.md /Tools-Maps.md: -------------------------------------------------------------------------------- 1 | # Tools : Maps 2 | 3 | Get map data 4 | -------------------------------------------------------------------------------- /Maps.md: -------------------------------------------------------------------------------- 1 | # Maps (wip) 2 | 3 | **KNOWN ISSUES WITH THIS API ROUTE** 4 | - `pretty=1` Option does not work. 5 | 6 | |Endpoint| 7 | |---| 8 | |https://api.xivdb.com/maps| 9 | |https://api.xivdb.com/maps/get/layers/[type]| 10 | 11 | ## content 12 | 13 | > `/maps` 14 | 15 | Get a structure list of maps grouped by regions. 16 | 17 | eg: http://api.xivdb.com/maps 18 | 19 | > `/maps/get/layers/[type]` 20 | > Options: `id`, `region`, `placename`, `zone`, `territory_id` 21 | 22 | Get a list of map layers grouped by a specific `type` 23 | 24 | eg: http://api.xivdb.com/maps/get/layers/id 25 | 26 | 27 | -------------------------------------------------------------------------------- /Data.md: -------------------------------------------------------------------------------- 1 | # Data 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/data/{content}| 6 | 7 | ## data 8 | 9 | Get game data 10 | 11 | ## content 12 | 13 | > `/data/exp_table` 14 | 15 | Get the current EXP Table data 16 | 17 | > `/data/classjobs` 18 | 19 | Get the list of classjobs and their ids 20 | 21 | > `/data/cabinet` 22 | > `/data/armoire` 23 | 24 | Get a list of items that can go into the cabinet, there are 2 routes because in game it is called armoire, in the data files it is called cabinet. 25 | 26 | > `/data/gc` 27 | 28 | Get a list of grand company ranks 29 | 30 | > `/data/patchlist` 31 | 32 | Get the XIVDB patch list. 33 | 34 | -------------------------------------------------------------------------------- /Content-NPC.md: -------------------------------------------------------------------------------- 1 | # NPC 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/npc/[id]| 6 | |https://api.xivdb.com/npc| 7 | 8 | ## content 9 | 10 | > /npc/[id] 11 | 12 | Get information about the npc: `[id]`. 13 | 14 | eg: https://api.xivdb.com/npc/1019613 15 | 16 | ## list 17 | 18 | > /npc 19 | 20 | Get a list of all npcs 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/npc?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/npc?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Fate.md: -------------------------------------------------------------------------------- 1 | # FATE 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/fate/[id]| 6 | |https://api.xivdb.com/fate| 7 | 8 | ## content 9 | 10 | > /fate/[id] 11 | 12 | Get information about the fate: `[id]`. 13 | 14 | eg: https://api.xivdb.com/fate/624 15 | 16 | ## list 17 | 18 | > /fate 19 | 20 | Get a list of all fates 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/fate?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/fate?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Item.md: -------------------------------------------------------------------------------- 1 | # Item 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/item/[id]| 6 | |https://api.xivdb.com/item| 7 | 8 | ## content 9 | 10 | > /item/[id] 11 | 12 | Get information about the item: `[id]`. 13 | 14 | eg: https://api.xivdb.com/item/17433 15 | 16 | ## list 17 | 18 | > /item 19 | 20 | Get a list of all items 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/item?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/item?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Leve.md: -------------------------------------------------------------------------------- 1 | # Leve 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/leve/[id]| 6 | |https://api.xivdb.com/leve| 7 | 8 | ## content 9 | 10 | > /leve/[id] 11 | 12 | Get information about the leve: `[id]`. 13 | 14 | eg: https://api.xivdb.com/leve/1196 15 | 16 | ## list 17 | 18 | > /leve 19 | 20 | Get a list of all leves 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/leve?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/leve?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Mount.md: -------------------------------------------------------------------------------- 1 | # Mount 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/mount/[id]| 6 | |https://api.xivdb.com/mount| 7 | 8 | ## content 9 | 10 | > /mount/[id] 11 | 12 | Get information about the mount: `[id]`. 13 | 14 | eg: https://api.xivdb.com/mount/56 15 | 16 | ## list 17 | 18 | > /mount 19 | 20 | Get a list of all mounts 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/mount?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/mount?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Emote.md: -------------------------------------------------------------------------------- 1 | # Emote 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/emote/[id]| 6 | |https://api.xivdb.com/emote| 7 | 8 | ## content 9 | 10 | > /emote/[id] 11 | 12 | Get information about the emote: `[id]`. 13 | 14 | eg: https://api.xivdb.com/emote/137 15 | 16 | ## list 17 | 18 | > /emote 19 | 20 | Get a list of all emotes 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/emote?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/emote?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Enemy.md: -------------------------------------------------------------------------------- 1 | # Enemy 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/enemy/[id]| 6 | |https://api.xivdb.com/enemy| 7 | 8 | ## content 9 | 10 | > /enemy/[id] 11 | 12 | Get information about the enemy: `[id]`. 13 | 14 | eg: https://api.xivdb.com/enemy/5554 15 | 16 | ## list 17 | 18 | > /enemy 19 | 20 | Get a list of all enemys 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/enemy?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/enemy?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Quest.md: -------------------------------------------------------------------------------- 1 | # Quest 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/quest/[id]| 6 | |https://api.xivdb.com/quest| 7 | 8 | ## content 9 | 10 | > /quest/[id] 11 | 12 | Get information about the quest: `[id]`. 13 | 14 | eg: https://api.xivdb.com/quest/67912 15 | 16 | ## list 17 | 18 | > /quest 19 | 20 | Get a list of all quests 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/quest?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/quest?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Title.md: -------------------------------------------------------------------------------- 1 | # Title 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/title/[id]| 6 | |https://api.xivdb.com/title| 7 | 8 | ## content 9 | 10 | > /title/[id] 11 | 12 | Get information about the title: `[id]`. 13 | 14 | eg: https://api.xivdb.com/title/324 15 | 16 | ## list 17 | 18 | > /title 19 | 20 | Get a list of all titles 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/title?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/title?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Achievement.md: -------------------------------------------------------------------------------- 1 | # Achievements 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/achievement/[id]| 6 | |https://api.xivdb.com/achievement| 7 | 8 | ## content 9 | 10 | > /achievement/[id] 11 | 12 | Get information about the achievement: `[id]`. 13 | 14 | ## list 15 | 16 | > /achievement 17 | 18 | Get a list of all achievements 19 | 20 | > Parameter: `schema=XXX` 21 | 22 | The schema can be adjusted for lists, eg: 23 | 24 | - https://api.xivdb.com/achievement?schema=1 25 | 26 | This will list all fields that can be selected using the `columns` option 27 | 28 | > Parameter: `columns=xxx,yyy,zzz` 29 | 30 | eg: 31 | 32 | - https://api.xivdb.com/achievement?columns=id,name,icon 33 | 34 | -------------------------------------------------------------------------------- /Content-Minion.md: -------------------------------------------------------------------------------- 1 | # Minion 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/minion/[id]| 6 | |https://api.xivdb.com/minion| 7 | 8 | ## content 9 | 10 | > /minion/[id] 11 | 12 | Get information about the minion: `[id]`. 13 | 14 | eg: https://api.xivdb.com/minion/189 15 | 16 | ## list 17 | 18 | > /minion 19 | 20 | Get a list of all minions 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/minion?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/minion?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Recipe.md: -------------------------------------------------------------------------------- 1 | # Recipe 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/recipe/[id]| 6 | |https://api.xivdb.com/recipe| 7 | 8 | ## content 9 | 10 | > /recipe/[id] 11 | 12 | Get information about the recipe: `[id]`. 13 | 14 | eg: https://api.xivdb.com/recipe/32225 15 | 16 | ## list 17 | 18 | > /recipe 19 | 20 | Get a list of all recipes 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/recipe?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/recipe?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Status.md: -------------------------------------------------------------------------------- 1 | # Status 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/status/[id]| 6 | |https://api.xivdb.com/status| 7 | 8 | ## content 9 | 10 | > /status/[id] 11 | 12 | Get information about the status: `[id]`. 13 | 14 | eg: https://api.xivdb.com/status/1145 15 | 16 | ## list 17 | 18 | > /status 19 | 20 | Get a list of all statuss 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/status?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/status?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Weather.md: -------------------------------------------------------------------------------- 1 | # Weather 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/weather/[id]| 6 | |https://api.xivdb.com/weather| 7 | 8 | ## content 9 | 10 | > /weather/[id] 11 | 12 | Get information about the weather: `[id]`. 13 | 14 | eg: https://api.xivdb.com/weather/51 15 | 16 | ## list 17 | 18 | > /weather 19 | 20 | Get a list of all weathers 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/weather?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/weather?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Shop.md: -------------------------------------------------------------------------------- 1 | # Shop (WIP) 2 | 3 | This is not really supported anymore, because Shop stuff is crazy... 4 | 5 | |Endpoint| 6 | |---| 7 | |https://api.xivdb.com/shop/[id]| 8 | |https://api.xivdb.com/shop| 9 | 10 | ## content 11 | 12 | > /shop/[id] 13 | 14 | Get information about the shop: `[id]`. 15 | 16 | ## list 17 | 18 | > /shop 19 | 20 | Get a list of all shops 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/shop?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/shop?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Action.md: -------------------------------------------------------------------------------- 1 | # Action 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/action/[id]| 6 | |https://api.xivdb.com/action| 7 | 8 | ## content 9 | 10 | > /action/[id] 11 | 12 | Get information about the action: `[id]`. 13 | 14 | eg: http://api.xivdb.com/action/3559/the+wanderer's+minuet 15 | 16 | ## list 17 | 18 | > /action 19 | 20 | Get a list of all actions 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/action?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/action?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Instance.md: -------------------------------------------------------------------------------- 1 | # Instance 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/instance/[id]| 6 | |https://api.xivdb.com/instance| 7 | 8 | ## content 9 | 10 | > /instance/[id] 11 | 12 | Get information about the instance: `[id]`. 13 | 14 | eg: https://api.xivdb.com/instance/7 15 | 16 | ## list 17 | 18 | > /instance 19 | 20 | Get a list of all instances 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/instance?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/instance?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Gathering.md: -------------------------------------------------------------------------------- 1 | # Gathering 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/gathering/[id]| 6 | |https://api.xivdb.com/gathering| 7 | 8 | ## content 9 | 10 | > /gathering/[id] 11 | 12 | Get information about the gathering: `[id]`. 13 | 14 | eg: https://api.xivdb.com/gathering/300000355 15 | 16 | ## list 17 | 18 | > /gathering 19 | 20 | Get a list of all gatherings 21 | 22 | > Parameter: `schema=XXX` 23 | 24 | The schema can be adjusted for lists, eg: 25 | 26 | - https://api.xivdb.com/gathering?schema=1 27 | 28 | This will list all fields that can be selected using the `columns` option 29 | 30 | > Parameter: `columns=xxx,yyy,zzz` 31 | 32 | eg: 33 | 34 | - https://api.xivdb.com/gathering?columns=id,name,icon 35 | 36 | -------------------------------------------------------------------------------- /Content-Placename.md: -------------------------------------------------------------------------------- 1 | # Placename 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/placename/[id]| 6 | |https://api.xivdb.com/placename| 7 | 8 | Square-Enix terminology of placenames are the main areas that contain map. "Zones" are sections of a map and "Regions" are the regions! 9 | 10 | ## content 11 | 12 | > /placename/[id] 13 | 14 | Get information about the placename: `[id]`. 15 | 16 | eg: https://api.xivdb.com/placename/125 17 | 18 | ## list 19 | 20 | > /placename 21 | 22 | Get a list of all placenames 23 | 24 | > Parameter: `schema=XXX` 25 | 26 | The schema can be adjusted for lists, eg: 27 | 28 | - https://api.xivdb.com/placename?schema=1 29 | 30 | This will list all fields that can be selected using the `columns` option 31 | 32 | > Parameter: `columns=xxx,yyy,zzz` 33 | 34 | eg: 35 | 36 | - https://api.xivdb.com/placename?columns=id,name,icon 37 | 38 | -------------------------------------------------------------------------------- /CHANGELOG-V3.md: -------------------------------------------------------------------------------- 1 | # WIP CHANGELOG V3 2 | 3 | These are work-in-progress change logs for version 3 of the XIVDB API 4 | 5 | ### Major changes 6 | 7 | 8 | ### Minor changes 9 | 10 | - All empty/null responses should now be "false". 11 | - All lists should now be an Array (not an Object). 12 | - Patch data will only be on primary content at the top level. 13 | - Data that is intended to be an array will be an empty array when no data available. 14 | 15 | ### Minor additions 16 | 17 | - It is now possible to exclude content pieces from top level datsets, eg: 18 | ``` 19 | https://api.xivdb.com/item/5056?exclude=recipe_crafts_into,recipe_created_from 20 | ``` 21 | 22 | This will exclude `recipe_crafts_into` and `recipe_created_from` data if you do not need it, allowing for a smaller payload of data. 23 | 24 | 25 | ### Data removed 26 | 27 | 28 | ### Data added 29 | 30 | 31 | ### Data changed 32 | 33 | - HQ values will no longer be included when they're the same of the NQ value (Thus no HQ benefit). 34 | -------------------------------------------------------------------------------- /Tools-Lore-Finder.md: -------------------------------------------------------------------------------- 1 | # Lore Finder 2 | 3 | |Endpoint| 4 | |---| 5 | |`http://api.xivdb.com/lore-finder`| 6 | 7 | You can use the API to search lore! This uses the same tool that can be found here: http://xivdb.com/lore-finder 8 | 9 | Currently you can search: 10 | - Quest Dialogue 11 | - Speech Bubbles 12 | - Content Descriptions 13 | - Instance Text Data 14 | - NPC Shouts 15 | - Public Content Data 16 | 17 | ## parameters 18 | 19 | > `loresearch=[string]` 20 | 21 | eg: `http://api.xivdb.com/lore-finder?loresearch=kupo` 22 | 23 | Search all lore material for the word "kupo" 24 | 25 | **RESPONSE SNIPPET** 26 | 27 | ```json 28 | { 29 | "string": "kupo", 30 | "totals": { 31 | "xiv_quests_to_text": 93075, 32 | "xiv_balloons": 3383, 33 | "xiv_contents_description": 145, 34 | "xiv_instances_text_data": 1693, 35 | "xiv_npc_yells": 4228, 36 | "xiv_public_content_text_data": 144 37 | }, 38 | "results": { 39 | "xiv_quests_to_text": [ 40 | 41 | ], 42 | ``` 43 | -------------------------------------------------------------------------------- /Character.md: -------------------------------------------------------------------------------- 1 | # Character 2 | 3 | |Endpoint| 4 | |---| 5 | |https://api.xivdb.com/character/[id]| 6 | |https://api.xivdb.com/character| 7 | 8 | |**Note on language parameter**| 9 | |---| 10 | |Currently XIVDB parses the English version of Lodestone and stores some of the data in plain text. This includes: Titles, grand company names, races, gender. This will be English only. I am working on moving this to object state so it can be multiple languages.| 11 | 12 | 13 | 14 | ## content 15 | 16 | > /character/[id] 17 | 18 | Get information about the character: `[id]`. 19 | 20 | --- 21 | 22 | ## list 23 | 24 | There is no list feature for characters, this is due to the high volume of characters in the same. 25 | 26 | --- 27 | 28 | ## parameters 29 | 30 | > `data=events` 31 | 32 | Get characters timeline events 33 | 34 | eg: https://api.xivdb.com/character/730968?data=events 35 | 36 | > `data=tracking` 37 | 38 | Get characters timeline tracking events, these are things such as name changes, race changes, server changes, etc. 39 | 40 | - eg: https://api.xivdb.com/character/730968?data=tracking 41 | 42 | > `data=gearsets` 43 | 44 | Get all recorded gearsets on the character. XIVDB saves gearsets for each class. 45 | 46 | - eg: https://api.xivdb.com/character/730968?data=gearsets 47 | 48 | > `data=achievements` 49 | 50 | Get all achievements for a character 51 | 52 | - eg: https://api.xivdb.com/character/730968?data=achievements 53 | 54 | > `data=achievements_possible` 55 | 56 | Get a list of achievements ID that this character can possible get. As of March 2017 this is currently a list of all achievements excluding/including Legacy achievements based on the characters creation date. 57 | 58 | - eg: https://api.xivdb.com/character/730968?data=achievements_possible 59 | 60 | |**Note regarding restricted achievements**| 61 | |---| 62 | |Some achievements are exclusive, for example a character can only get the "Leaving [nation]" achievement for the town nation they joined when the character was created. For 1.0 characters they can have 2 of the 3 nation achievements (as players could change nation in 2.0 release). Characters created after 2.0 can only get 1 of the 3 achievements. Lodestone will always show all 3 achievements as possible to obtain. 63 | 64 | You would need to handle this manually in your application as XIVDB currently does not do anything about it (will do at some point). If SE ever fix their achievements pages, the route will automatically reflect the correct achievements.| 65 | 66 | > `data=achievements_obtained` 67 | 68 | Get a list of achievement ID that this character has obtained. This is useful if you want a very lightweight list of obtained achievements and their obtained date 69 | 70 | - eg: http://api.xivdb.com/character/730968?data=achievements_obtained 71 | 72 | -------------------------------------------------------------------------------- /Search-Order.md: -------------------------------------------------------------------------------- 1 | # Order fields 2 | 3 | If someone can make this pretty, I'd appreciate it! 4 | 5 | | Achievements | Action | Characters | emotes | 6 | |---------------------------------------------------------------|-----------------------------------------------|---------------------------------------------------------------|----------------------------------------| 7 | | `id` - `ID` | `id` - `ID` | `lodestone_id` - `ID` | `id` - `ID` | 8 | | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name` - `Name` | `name_{lang}` - `Name` | 9 | | `points` - `Points` | `level` - `level` | `server` - `Server` | `emote_category` - `Category` | 10 | | `achievement_category` - `Category` | `cost` - `Cost` | `achievements_score_reborn` - `ARR 2.0+ Achievement Points` | `patch` - `Patch` | 11 | | `patch` - `Patch` | `cast_range` - `Cast Range` | `achievements_score_legacy` - `Legacy 1.0 Achievement Points` | | 12 | | | `cast_time` - `Cast Time` | `data_last_changed` - `Last Active` | | 13 | | | `recast_time` - `Recast Time` | `last_updated` - `Last Updated` | | 14 | | | `classjob` - `Class Job` | `added` - `Added` | | 15 | | | `type` - `Type` | | | 16 | | | `can_target_self` - `Can Target Self` | | | 17 | | | `can_target_party` - `Can Target Party` | | | 18 | | | `can_target_friendly` - `Can Target Friendly` | | | 19 | | | `can_target_hostile` - `Can Target Hostile` | | | 20 | | | `is_target_area` - `Is AOE` | | | 21 | | | `is_pvp` - `Is PVP` | | | 22 | | | `patch` - `Patch` | | | 23 | | | | | | 24 | | instance | items | leves | leve | 25 | | `id` - `ID` | `id` - `ID` | `id` - `ID` | `id` - `ID` | 26 | | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | 27 | | `level` - `Level` | `slot_equip` - `Slot` | `patch` - `Patch` | `patch` - `Patch` | 28 | | `level_sync` - `Sync Level` | `level_equip` - `Equipment Level` | | | 29 | | `time_limit` - `Time Limit` | `level_item` - `Item Level` | | | 30 | | `players_per_party` - `Players per Party` | `rarity` - `Rarity` | | | 31 | | `tanks_per_party` - `Tanks per Party` | `stack_size` - `Stack Size` | | | 32 | | `healers_per_party` - `Healers per Party` | `price_sell` - `Price Sell` | | | 33 | | `melees_per_party` - `Melees per Party` | `price_sell_hq` - `Price Sell HQ` | | | 34 | | `ranged_per_party` - `Ranged per Party` | `salvage` - `Salvage` | | | 35 | | `party_count` - `Party Count` | `materia_slot_count` - `Materia Slots` | | | 36 | | `free_role` - `Can free role` | `pvp_rank` - `PvP Rank` | | | 37 | | `item_level` - `Item Level Required` | `cooldown_seconds` - `Cooldown` | | | 38 | | `item_level_sync` - `Item Level Sync` | `aetherial_reduce` - `Aetherial Reduce` | | | 39 | | `is_echo_default` - `Echo by Default` | `can_be_hq` - `Can HQ` | | | 40 | | `is_echo_annihilation` - `Echo upon Death` | `reducible_level` - `Reducible Level` | | | 41 | | `week_restriction` - `Weekly Restricted` | `is_pvp` - `Is PvP` | | | 42 | | `is_in_duty_finder` - `Is in duty-finder` | `is_untradable` - `Is Untradable` | | | 43 | | `allow_alliance_registration` - `Allow Alliance Registration` | `is_reducible` - `Is Reducible` | | | 44 | | `patch` - `Patch` | `is_legacy` - `Is Legacy` | | | 45 | | | `is_dated` - `Is Dated` | | | 46 | | | `is_crest_worthy` - `Is Crest Worthy` | | | 47 | | | `is_desynthesizable` - `Is Desynthesizable` | | | 48 | | | `is_projectable` - `Is Projectable` | | | 49 | | | `is_dyeable` - `Is Dyeable` | | | 50 | | | `is_convertible` - `Is Convertible` | | | 51 | | | `is_indisposable` - `Is Indisposable` | | | 52 | | | `is_collectable` - `Is Collectable` | | | 53 | | | `updated` - `Last Updated` | | | 54 | | | `parsed_lodestone` - `Verified on Lodestone` | | | 55 | | | `patch` - `Patch` | | | 56 | | | `attributes` - `Attributes` | | | 57 | | | | | | 58 | | placename | quest | recipe | shop | 59 | | `id` - `ID` | `id` - `ID` | `id` - `ID` | `id` - `ID` | 60 | | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | 61 | | `region` - `Has Region` | `journal_genre` - `Journal` | `level` - `Recipe Level` | `patch` - `Patch` | 62 | | `patch` - `Patch` | `class_level_1` - `Level` | `level_diff` - `Stars` | | 63 | | | `class_level_2` - `Level (Sub cCass)` | `level_view` - `Craft Level` | | 64 | | | `gil_reward` - `Gil Reward` | `durability_factor` - `Durability` | | 65 | | | `exp_reward` - `EXP Reward` | `quick_synth_craftsmanship` - `Quick Synth Craftsmanship` | | 66 | | | `gc_seals` - `Grand Company Seals` | `quick_synth_control` - `Quick Synth Control` | | 67 | | | `tomestone_count_reward` - `Tomestones` | `required_craftsmanship` - `Required Craftsmanship` | | 68 | | | `reputation_reward` - `Reputation Points` | `required_control` - `Required Control` | | 69 | | | `beast_reputation_rank` - `Beast Tribe Rank` | `status_required` - `Status Required` | | 70 | | | `grand_company_rank` - `Grand Company Rank` | `item_required` - `Item Required` | | 71 | | | `journal_genre` - `Journal` | `material_point` - `Material Point` | | 72 | | | `patch` - `Patch` | `quality` - `Quality` | | 73 | | | | `durability` - `Durability` | | 74 | | | | `difficulty` - `Difficulty` | | 75 | | | | `work_max` - `Max Work` | | 76 | | | | `patch` - `Patch` | | 77 | | | | | | 78 | | weather | special shop | status | title | 79 | | `id` - `ID` | `id` - `ID` | `id` - `ID` | `id` - `ID` | 80 | | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name (Male)` | 81 | | `patch` - `Patch` | `patch` - `Patch` | `patch` - `Patch` | `name_female_{lang}` - `Name (Female)` | 82 | | | | | `patch` - `Patch` | 83 | | | | | | 84 | | enemy | fate | gathering | npc | 85 | | `id` - `ID` | `id` - `ID` | `id` - `ID` | `id` - `ID` | 86 | | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | `name_{lang}` - `Name` | 87 | | `patch` - `Patch` | `class_level` - `Level` | `level` - `Level` | `patch` - `Patch` | 88 | | | `class_level_max` - `Level (Max)` | `level_view` - `Difficulty Level` | | 89 | | | `patch` - `Patch` | `level_diff` - `Difficulty Rating` | | 90 | | | | `is_hidden` - `Is Hidden` | | 91 | | | | `patch` - `Patch` | | 92 | | | | | | 93 | | minion | mount | | | 94 | | `id` - `ID` | `id` - `ID` | | | 95 | | `name_{lang}` - `Name` | `name_{lang}` - `Name` | | | 96 | | `minion_race` - `Race` | `patch` - `Patch` | | | 97 | | `cost` - `Cost` | | | | 98 | | `skill_cost` - `Skill Cost` | | | | 99 | | `hp` - `Health` | | | | 100 | | `attack` - `Attack` | | | | 101 | | `defense` - `Defense` | | | | 102 | | `speed` - `Speed` | | | | 103 | | `has_area_attack` - `Has AOE` | | | | 104 | | `strength_gate` - `Strong against Gate` | | | | 105 | | `strength_eye` - `Strong against Search Eye` | | | | 106 | | `strength_shield` - `Strong against Shield` | | | | 107 | | `strength_arcana` - `Strong against Arcana Stones` | | | | 108 | | `patch` - `Patch` | | | | 109 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | |XIVDB API| | 2 | |---|---| 3 | | Endpoint | https://api.xivdb.com/ | 4 | | Protocol| `https` and `http` supported. | 5 | | Language| **JSON** | 6 | | Methods | **GET** only | 7 | | SDK | Soon.. | 8 | 9 | --- 10 | 11 | ## about 12 | 13 | The XIVDB API allows you to access various different game content in a very structured format. The entire site runs on top of the API so it is heavily modular and integrates well with web technologies. 14 | 15 | --- 16 | 17 | ## documentation 18 | 19 | ### search 20 | - [Search](Search.md) 21 | - [Search Order Fields](Search-Order.md) 22 | - [Lore Finder](Tools-Lore-Finder.md) 23 | 24 | ### content 25 | - [Achievement](Content-Achievement.md) 26 | - [Action](Content-Action.md) 27 | - [Emote](Content-Emote.md) 28 | - [Enemy](Content-Enemy.md) 29 | - [Fate](Content-Fate.md) 30 | - [Gathering](Content-Gathering.md) 31 | - [Instance](Content-Instance.md) 32 | - [Item](Content-Item.md) 33 | - [Leve](Content-Leve.md) 34 | - [Minion](Content-Minion.md) 35 | - [Mount](Content-Mount.md) 36 | - [NPC](Content-NPC.md) 37 | - [Placename](Content-Placename.md) 38 | - [Quest](Content-Quest.md) 39 | - [Recipe](Content-Recipe.md) 40 | - [Shop](Content-Shop.md) 41 | - [Status](Content-Status.md) 42 | - [Title](Content-Title.md) 43 | - [Weather](Content-Weather.md) 44 | 45 | ### characters 46 | - [Characters](Character.md) 47 | 48 | ### base data 49 | 50 | - [Maps](Maps.md) 51 | - [Game Data](Data.md) 52 | - EXP Table 53 | - ClassJobs 54 | - Cabinet 55 | - Armoire 56 | - Grand Companies 57 | - Patch List (XIVDB Built in patch system) 58 | - *... request more ...* 59 | 60 | ### Lodestone Information + Dev Tracker 61 | 62 | - Lodestone Data - http://xivdb.com/assets/lodestone.json 63 | - Dev Tracker - http://xivdb.com/assets/devtracker.json 64 | 65 | Both the lodestone data and the dev tracker update every 5 minutes and are always in English. You can use these on your sites freely. 66 | 67 | ### Examples 68 | 69 | - [chat bot type scenario](https://codepen.io/viion/full/xLYELO/) 70 | 71 | --- 72 | 73 | ## wip 74 | *No particular order* 75 | 76 | - PHP SDK 77 | - Javascript SDK 78 | - Map Embeds 79 | - Add Custom Gearsets to the API 80 | - Add Shopping Carts to the API 81 | - Providing Achievement Ranking data to the API 82 | - Provide more information for characters 83 | - Provide schema column selection for core data 84 | 85 | --- 86 | 87 | ## routing 88 | > API Endpoint: `https://api.xivdb.com/` 89 | 90 | Accessing content pages from the API is as simple as putting `api.` infront of the URL, here are some examples: 91 | 92 | - `http://xivdb.com/item/1675/curtana` 93 | - --> `http://api.xivdb.com/item/1675/curtana` 94 | - `http://xivdb.com/instance/43/the+antitower` 95 | - --> `http://api.xivdb.com/instance/43/the+antitower` 96 | - `http://xivdb.com/character/730968/premium+virtue/phoenix` 97 | - --> `http://api.xivdb.com/character/730968/premium+virtue/phoenix` 98 | 99 | The Names (and for characters: Server) is optional and not required, eg: 100 | 101 | - `http://api.xivdb.com/item/1675/curtana` 102 | - OR `http://api.xivdb.com/item/1675` 103 | - `http://api.xivdb.com/character/730968/premium+virtue/phoenix` 104 | - OR `http://api.xivdb.com/character/730968` 105 | 106 | --- 107 | 108 | ## global commands 109 | > `language=[LANG]` 110 | 111 | > `[LANG]` **Options:** English `en`, German `de`, French `fr`, Japanese `ja` 112 | 113 | Set the language for the data. This is primarally for content pieces (Character data is mostly English for now, more on that in the Character section), here are some examples: 114 | 115 | - German: https://api.xivdb.com/item/1675?language=de 116 | - French: https://api.xivdb.com/item/1675?language=fr 117 | - Japanese: https://api.xivdb.com/item/1675?language=ja 118 | 119 | **language during search/filters** 120 | 121 | Sometimes you may not always know what the language is. Search content will often fetch results in all 4 languages for named content, eg: `name_en`, `name_fr`, `name_de`, `name_ja` in this case you can use the placeholder `{lang}` and the system will handle it for you, eg: `name_{lang}` or `description_{lang}` 122 | 123 | 124 | > `pretty=1` 125 | 126 | Enables a pretty view for the JSON. This is very helpful for debugging and reading what is in the response, eg: 127 | 128 | - https://api.xivdb.com/item/1675?pretty=1 129 | 130 | **Before:** 131 | ```json 132 | {"achievements":null,"action":0,"aetherial_reduce":0,"attributes_base":{"auto_attack":34.02,"auto_attack_hq":34.02,"block_rate":0,"block_rate_hq":0,"block_s ... 133 | ``` 134 | 135 | **After:** 136 | ```json 137 | { 138 | "achievements": null, 139 | "action": 0, 140 | "aetherial_reduce": 0, 141 | "attributes_base": { 142 | "auto_attack": 34.02, 143 | "auto_attack_hq": 34.02, 144 | "block_rate": 0, 145 | "block_rate_hq": 0, 146 | ``` 147 | 148 | --- 149 | 150 | ## protocol notes 151 | Both `http` and `https` are supported. The reason for this is because the API isn't intended to be crawled by Google or used in SEO it is setup to make it easy for developers to jump in. 152 | 153 | Accessing `https` urls in some languages requires extra code or SSL verification and it might be simplier to stick to the `http` version. If you're using the API in a frontend library (eg: Javascript) and your site is behind an SSL certificate, you will have to use the `https` endpoint. 154 | 155 | *There is no sensitive data on the API and you can only retrieve game related data, nothing regarding members, comments or screenshots.* 156 | 157 | --- 158 | 159 | ## rate limiting 160 | There are no strict limits on the API at this time, however this does not excuse bad coding practices. Do not query the API in a `for/foreach/while` loop and leverage caching, game content updates every patch so it is not needed to query every time! 161 | 162 | The API sits behind Redis and should be fairly responsive, think about what kind of calls you will be doing to the API and what kind of data you need. 163 | 164 | If you are looking for all of the game data then you may find it more useful to extract the CSV's yourself, Information on that can be found here: https://github.com/viion/XIV-Datamining 165 | 166 | --- 167 | 168 | ## support 169 | 170 | If you need help with the API please don't hesitate to contact me, I am happy to answer all questions, fix any issues or add in additional information. Just bcause some data doesn't exist doesn't mean I can't add it! 171 | 172 | Please join the Discord: https://discord.gg/6XT7FTJ and there is a channel called `web-dev` for API Stuff 173 | 174 | --- 175 | 176 | # rate limit 177 | 178 | The XIVDB has a 15 requests/second rate limit before it will begin denying requests. Please code respectfully, this means no `foreach` or `while` loops firing off requests, either use recurrsion, promises or callbacks. 179 | 180 | Here is a Javascript gist that shows bad/good query code: 181 | 182 | - https://gist.github.com/viion/d30684c402995b9f4b91d2e95faf1ef4 183 | -------------------------------------------------------------------------------- /Search.md: -------------------------------------------------------------------------------- 1 | # search 2 | 3 | |Endpoint| 4 | |---| 5 | |`https://api.xivdb.com/search`| 6 | 7 | The search allows you to search! You can find information for all main content types as well as characters. Search provides some small additional fields that can help you present user friendly views. The API also has an extremely robust filter system which is easy to grow (if you need more filters, let me know!) 8 | 9 | The search API is best used for: 10 | - Wildcard Content finding 11 | - Character searching 12 | - Visually pleasing search results for frontend applications 13 | 14 | It is not good for: 15 | - Rapid fire searching 16 | - Auto-completion 17 | 18 | --- 19 | 20 | ## quick tip 21 | 22 | If you are building an application that requires the search then the best way to view what kind of things you can do is to use your browsers built in Developer Tools. If you go to the XIVDB's home page, open up developer tools, go to the: `Network` tab, filter requests by `XHR` and then click on one of the search options in XIVDB you will see the request. You can then click on that request to see the kinds of parameters that were sent. 23 | 24 | ![example](http://i.imgur.com/fQDKtQj.png) 25 | 26 | You can then play around with the filters on the site and view the `Query String Parameters` to get a real-time demo of how it's used! 27 | 28 | --- 29 | 30 | ## core parameters 31 | > `string=[some string]` 32 | 33 | > eg: `string=allagan braclets of aiming` 34 | 35 | Search titles for some piece of content, use this to find item names, instance names, or even character names! For titles this will search both Male and Female titles. 36 | - **Character limit:** 2 37 | 38 | > eg: `string=maiming,belt` 39 | 40 | Using a comma will split words by "AND", eg: `maiming,belt` will return stuff with `maiming` AND `belt` in the name, eg: 41 | - Heavy Metal Plate **Belt** of **Maiming** 42 | - Hero's **Belt** of **Maiming** 43 | 44 | > eg: `string=maiming/belt` 45 | 46 | Using a forward slash will split words by "OR", eg: `maiming/belt` will return stuff with `maiming` OR `belt` in the name, eg: 47 | - Diabolic **Belt** of Casting (not maining) 48 | - Filibuster's Heavy Boots of **Maiming** (not a belt) 49 | 50 | You can also search **characters**: 51 | 52 | > eg: `string=[character name]` 53 | > eg: `string=Premium Virtue` 54 | 55 | This includes partial names 56 | 57 | > eg: `string=Virtue` 58 | 59 | 60 | 61 | --- 62 | 63 | > `one=[type]` 64 | 65 | > `one=items` 66 | 67 | Filters a specific content type, the list of content types are: 68 | 69 | |Types||||||| 70 | |---|---|---|---|---|---|---| 71 | |items|recipes|quests|actions|instances|achievements|fates 72 | |leves|places|gathering|npcs|enemies|emotes|status 73 | |titles|minions|mounts|weather|characters 74 | 75 | If ommited or set to "All", all content types are searched. 76 | 77 | --- 78 | 79 | > `order_field=[field]` 80 | 81 | Set the field in which to order the content by. All content has the field `id`, `name` and `patch`. `name` is special in that is the name based on your current language. So if you provide the parameter `language=fr` then ordering by `name` will be ordered by French names. 82 | 83 | Possible fields: [Search Orders](Search-Order.md) 84 | 85 | > `order_direction=[asc|desc]` 86 | 87 | Provide the direction for the results, this will either by: `ASC` or `DESC`, (case insensitive, can be lower case) 88 | 89 | --- 90 | 91 | > `page=[x]` 92 | 93 | Which page to start on, if you implement pagination on your use-case then you will need to provide a page. When ommited it defaults to `1` 94 | 95 | > `limit=[x]` 96 | 97 | Limit the number of results to return from the API. 98 | - **Maximum:** 90 99 | 100 | --- 101 | 102 | > `strict=[on|off]` 103 | 104 | Toggle search strict mode, by default all string searches are wildcard and search both sides, for example: 105 | - OFF: `aim` would find items with the word: M**aim**ing--- 106 | - ON: `aim` would only find items starting with Aim--- 107 | 108 | The purpose of this is if you really need to use the search for auto-complete, then `strict=ON` would make it more obvious to the user. It also provides a faster response than without it for smaller values. 109 | 110 | --- 111 | 112 | ## commands 113 | > `string=!patch+{patch version}` 114 | 115 | This is a special command in that it will return all new content for a specific patch, you can find the list of patches here: http://api.xivdb.com/data/patchlist?pretty=1, for example: 116 | - https://api.xivdb.com/search?string=patch+3.5 117 | 118 | --- 119 | 120 | ## filters 121 | 122 | There are many filters for all the different types of content 123 | 124 | **STRUCTURE** 125 | > `{filter}|{operator}` 126 | 127 | For example: 128 | - `level|gt=X` means `Level Greater Than X` 129 | - `level|lt=X` means `Level Less Than X` 130 | - `level|et=X` means `Level Equal To X` 131 | 132 | Some variables only have an equal to because they're boolean based, eg: 133 | 134 | - `is_pvp=1` means `Items that are PVP` 135 | 136 | **CONTENT FILTERS** 137 | 138 | ### Achievements 139 | ``` 140 | points|et 141 | achievement_category|et 142 | item 143 | title 144 | patch|et 145 | ``` 146 | ### Actions 147 | ``` 148 | level|gt 149 | level|lt 150 | action_category|et 151 | can_target_dead 152 | is_target_area 153 | can_target_self 154 | can_target_party 155 | can_target_friendly 156 | can_target_hostile 157 | is_pvp 158 | patch|et 159 | classjobs 160 | classjobs_andor 161 | ``` 162 | ### Characters 163 | ``` 164 | server|et 165 | achievements_public 166 | ``` 167 | ### Emotes 168 | ``` 169 | patch|et 170 | ``` 171 | ### Enemies 172 | ``` 173 | patch|et 174 | ``` 175 | ### Fates 176 | ``` 177 | class_level|gt 178 | class_level|lt 179 | class_level_max|gt 180 | class_level_max|lt 181 | placename|et 182 | patch|et 183 | ``` 184 | ### Gathering 185 | ``` 186 | level|gt 187 | level|lt 188 | level_view|gt 189 | level_view|lt 190 | ``` 191 | ### Instances 192 | ``` 193 | level|gt 194 | level|lt 195 | level_sync|gt 196 | level_sync|lt 197 | item_level|gt 198 | item_level|lt 199 | item_level_sync|gt 200 | item_level_sync|lt 201 | instance_content_type|et 202 | content_roulette|et 203 | is_echo_default 204 | is_echo_annihilation 205 | new_player_bonus 206 | content_roulette 207 | alliance 208 | is_in_duty_finder 209 | patch|et 210 | ``` 211 | ### Items 212 | ``` 213 | level_item|gt 214 | level_item|lt 215 | level_equip|gt 216 | level_equip|lt 217 | item_ui_category|et 218 | item_ui_kind|et 219 | item_series|et 220 | materia_slot_count|et 221 | rarity|et 222 | patch|et 223 | 224 | source|et 225 | Values: 226 | =achievement 227 | =craftable 228 | =instance 229 | =instance_reward 230 | =instance_chest 231 | =quest 232 | =enemy 233 | =shop 234 | =gathering 235 | 236 | attributes 237 | Group a set of attributes in the format: ID|OPERATOR|VALUE|HQ 238 | eg: 22|gt|5|0,25|gt|10|1 239 | Attribute 22 Greater Than 5 NQ 240 | AND|OR 241 | Attribute 25 Greater Than 10 HQ 242 | 243 | attributes_andor 244 | Set the AND|OR for attribute filters. 245 | 246 | classjobs 247 | A list of class/job ids 248 | eg: 2,17,24,26 249 | Pugilist, Arcanist, White Mage, Botanist 250 | 251 | classjobs_andor 252 | Set the AND|OR for classjobs filter. 253 | classjobs_exclusive 254 | ``` 255 | ### SearchLeves 256 | ``` 257 | class_level|gt 258 | class_level|lt 259 | placename|et 260 | patch|et 261 | ``` 262 | ### SearchMinions 263 | ``` 264 | patch|et 265 | ``` 266 | ### SearchNPC 267 | ``` 268 | patch|et 269 | ``` 270 | ### SearchPlacenames 271 | ``` 272 | patch|et 273 | ``` 274 | ### SearchQuests 275 | ``` 276 | class_level_1|gt 277 | class_level_1|lt 278 | patch|et 279 | ``` 280 | ### SearchRecipes 281 | ``` 282 | level|gt 283 | level|lt 284 | level_view|gt 285 | level_view|lt 286 | can_quick_synth 287 | can_hq 288 | level_diff|et 289 | recipe_element|et 290 | patch|et 291 | classjobs 292 | classjobs_andor 293 | ``` 294 | ### SearchStatus 295 | ``` 296 | patch|et 297 | ``` 298 | ### SearchTitles 299 | ``` 300 | patch|et 301 | ``` 302 | ### SearchWeather 303 | ``` 304 | patch|et 305 | ``` 306 | --------------------------------------------------------------------------------