-
New Feature
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
In order to find the corresponding MB entity or MBID for an external link, users currently have to use one browse request per URL, for example https://musicbrainz.org/ws/2/url?resource=http://example.com/artist/42&include=artist-rels&fmt=json.
Doing this for multiple URLs is very slow because of the rate limiting, so it would be great if there was an API endpoint which accepts multiple URLs and returns all of the results.
This would speed up importing tools which are using the API to map external identifiers/URLs to MBIDs before seeding an editing form on MB.
Using a local MB mirror is not really an option as the whole point of these lookups is also to check whether the corresponding entity already exists on MB, so the most recent data is required.
- is related to
-
MBS-6459 Allow multiple MBIDs for lookups in the webservice
-
- Open
-
Lookup multiple URLs at once with the API
-
New Feature
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
In order to find the corresponding MB entity or MBID for an external link, users currently have to use one browse request per URL, for example https://musicbrainz.org/ws/2/url?resource=http://example.com/artist/42&include=artist-rels&fmt=json.
Doing this for multiple URLs is very slow because of the rate limiting, so it would be great if there was an API endpoint which accepts multiple URLs and returns all of the results.
This would speed up importing tools which are using the API to map external identifiers/URLs to MBIDs before seeding an editing form on MB.
Using a local MB mirror is not really an option as the whole point of these lookups is also to check whether the corresponding entity already exists on MB, so the most recent data is required.
- is related to
-
MBS-6459 Allow multiple MBIDs for lookups in the webservice
-
- Open
-