Site
Home / Forum / Developers / v2 event search not finding events
Home / Forum / Developers / v2 event search not finding events
v2 event search not finding events |
| Posted: 05 Mar 2026 11:00 | |||
Posts: 3 Joined: 2026 | I am trying to build a dropdown menu to help me find metadata of events but the v2 event search does not work as expected. For example, i am trying to find this event: https://www.thesportsdb.com/event/2267361-tottenham-hotspur-vs-crystal-palace I would have expected that i can will get a list of events including "tottenham" using a query like this: https://www.thesportsdb.com/api/v2/json/search/event/tottenham but i don't get a single event in return, just a "{"Message":"No data found"}". What is going on? | ||
 | |||
| Posted: 05 Mar 2026 11:09 | |||
Posts: 1,169 Joined: 2020 | It is not a fuzzy search, the search term needs to be like the documentation example "/api/v2/json/search/event/fifa_world_cup_2022-12-18_argentina_vs_france". It should contain the league name, date, and then home team vs away team. You can omit the later parts like "/api/v2/json/search/event/fifa_world_cup_2022-12-18" which will provide only matches for the World Cup on that date. As there is no league called 'Tottenham' the result is correct. zag | ||
| |||
| Posted: 05 Mar 2026 12:11 | |||
Posts: 3 Joined: 2026 | Meh, that's not gonna work for me then. Any chances we can get a "fuzzy search" of teams to look for an event? Happy to start searching from 5 chars if that helps. | ||
| |||
| Posted: 05 Mar 2026 12:12 | |||
Posts: 3 Joined: 2026 | Also, your v1 search does Fuzzy just fine. The problem there is it only returns 2 items - that rarely contains the correct event looking for popular teams. | ||
| |||
| Posted: 06 Mar 2026 15:34 | |||
 zag Posts: 3,953 Joined: 2020 | I've just checked the code and v1 is the same as v2 on the search endpoints. I'm interested in an example if you can provide one. Just omit your api key from the url if you post here. Basically the search uses a wildcard at the end but not the beginning of the string so it wont be full text at the moment sorry. EDIT: The main frontend website does use fulltext search, but there are also issues with that that might affect api users if I introduced it there and changed the logic. | ||
|