Legacy fuzzy name match service (Version 1 - flat format)
Changed onVersion 1 - Warning: this method will be removed and users are advised to migrate to the version 2 API v2/species/match.
Fuzzy matches scientific names against the GBIF Backbone Taxonomy with the optional classification provided. If a classification is provided and strict is not set to true, the default matching will also try to match against these if no direct match is found for the name parameter alone.
Additionally, a lookup may be performed by providing the usageKey which will short-circuit the name-based matching and ONLY use the given key, either finding the concept or returning no match.
Request
- Base URLhttps://api.gbif.org
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
The usage key to look up. When provided, all other fields are ignored.
The scientific name to fuzzy match against. May include the authorship and year
The scientific name authorship to fuzzy match against.
Filters by taxonomic rank as given in our https://api.gbif.org/v1/enumeration/basic/Rank[Rank enum].
Generic part of the name to match when given as atomised parts instead of the full name parameter.
Specific epithet to match.
Infraspecific epithet to match.
If true it fuzzy matches only the given name, but never a taxon in the upper classification.
If true it shows alternative matches which were considered but then rejected.
Kingdom to match.
Phylum to match.
Order to match.
Class to match.
Family to match.
Genus to match.
Response
Name usage suggestions found
Changes
- info
added the new optional
queryrequest parameterscientificName - info
added the new optional
queryrequest parameterscientificNameAuthorship - info
added the new optional
queryrequest parameterscientificNameID - info
added the new optional
queryrequest parametertaxonConceptID - info
added the new optional
queryrequest parametertaxonID - info
added the new optional
queryrequest parametertaxonRank
- info