New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating new UniProt.ws object fails to query uniprot.org, HTTP status '400 Bad Request' #21
Comments
Same issue here. It seems clear that the package must be update with the new API. |
Hi @proteomicsIJC @buijt |
I've made changes to the package to restore as much functionality as possible. See package version Best regards, |
Great Marcel! Thank you for your work.
El dia 9 d’ag. 2022 23:41, Marcel Ramos ***@***.***> va escriure:
Hi @proteomicsIJC<https://github.com/proteomicsIJC> @buijt<https://github.com/buijt>
I've made changes to the package to restore as much functionality as possible.
Please open up another issue if you are having trouble with the software.
See package version 2.37.1, which should be built in 24 - 48 hours.
Best regards,
Marcel
—
Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ3BEQ6FPGGGAEMDAI3QBEDVYLGBBANCNFSM52D3YN3Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I used to have this problem, but it is now totally fixed with version 2.37.5! |
Announcement on the new UniProt website:
I started encountering this error today and I believe this may be due to a change in the UniProt API coinciding with the launch of the new UniProt website. I otherwise cannot find any announcement from UniProt about the new API. The new API syntax breaks the
UniProt.ws
package and appears to have slightly different behavior in its return values.The package is trying to connect to https://www.uniprot.org/uniprot/?query=organism:9606&format=tab&columns=id which is no longer valid with the new API, and returns HTML 400 status code.
UniProt's new API (https://rest.uniprot.org/uniprotkb/) breaks the package. The closest functioning API call to the above that I can determine is: https://rest.uniprot.org/uniprotkb/search?query=organism_id:9606&format=tsv&fields=accession
The old website (https://legacy.uniprot.org/) will return the old result, but I suspect the legacy API will be retired at some point. The website says the legacy website will be available until the 2022_03 release, at which point the legacy API would also be shut down. https://legacy.uniprot.org/uniprot/?query=organism:9606&format=tab&columns=id
I believe all the API calls in the package will need to be updated to support the new UniProt API following this documentation: https://www.uniprot.org/help/return_fields
The text was updated successfully, but these errors were encountered: