I looked in the forum and on the main site, what mentions I can find seems quite obsolete.
I have a Windows based sheet music reader app that I wrote. I'm using the wikimedia interface to search IMSLP, and then using a browser (QtWebEngine) to download a file to the user's hard drive. This takes you through the "I understand" clicks that you have to do, and then usually makes you wait 15 seconds to download the file. I think there are sometimes copyright notices as well that you have to accept. I'm a paid subscriber, as are plenty of others, it would be nice to be able to bypass the 15 second wait if you log in. It's not the end of the world, but it would be nice to get this. Nothing is otherwise automated, user has to type in search terms, and can only select and download 1 file at a time, as I don't want anyone swamping IMSLP by downloading vast amounts of material.
I saw some old messages in the forum about requesting an API key, but I suspect that is obsolete, as nothing on the main site says anything about that.
Advice is appreciated. Don't ask to see the app as it isn't released yet, maybe in a few days if I get traction here. It is free and open source (probably MIT license, haven't fully decided). If someone at IMSLP needs to see it to ensure my request is genuine of course I'll share privately, I mean random readers.
API access for open source sheet music app I'm writing
-
lauralordelaure
- Posts: 1
- Joined: Tue Jul 08, 2025 3:24 am
- notabot: 42
- notabot2: Human
Re: API access for open source sheet music app I'm writing
Geometry Dash For paid subscribers, is there a documented way (cookie/session token/login API) to programmatically authenticate and bypass the 15-second download delay?
Last edited by lauralordelaure on Wed Jul 09, 2025 1:28 am, edited 1 time in total.
Re: API access for open source sheet music app I'm writing
If you have a paid subscription, you should not be seeing any sort of 15 second delay.
Re: API access for open source sheet music app I'm writing
"f you have a paid subscription, you should not be seeing any sort of 15 second delay."
That's true with a desktop browser, but we aren't talking about that.The question is there a way to avoid this via the API. To be clear, I start a 'browser' using Qt's web engine (c++). That browser is not logged in because it is not your desktop browser with all the saved cookies, etc. I would want the user to be able to log in via my app, so that then my app can download sheet music without the 15 second wait (and preferably without all the copyright warnings). I'm not a web programmer, so maybe there is an obvious way to get that browser to log in via an API, but if so I don't know it. As it is, right now I can perform searches and return results, showing thumbnails, etc, all instantly. But if the user wants to download, the web engine then shows the "wait 15 seconds" page, counts through it, then finally lets you download. You could click "login", but again, this is an app, not your desktop browser, and the app has no idea you left the page, and then the download fails. And it doesn't remember the login so that the next time you can avoid it (this could be me, again I'm not a web programmer). So you sit there for 15 seconds each and every time.
That's true with a desktop browser, but we aren't talking about that.The question is there a way to avoid this via the API. To be clear, I start a 'browser' using Qt's web engine (c++). That browser is not logged in because it is not your desktop browser with all the saved cookies, etc. I would want the user to be able to log in via my app, so that then my app can download sheet music without the 15 second wait (and preferably without all the copyright warnings). I'm not a web programmer, so maybe there is an obvious way to get that browser to log in via an API, but if so I don't know it. As it is, right now I can perform searches and return results, showing thumbnails, etc, all instantly. But if the user wants to download, the web engine then shows the "wait 15 seconds" page, counts through it, then finally lets you download. You could click "login", but again, this is an app, not your desktop browser, and the app has no idea you left the page, and then the download fails. And it doesn't remember the login so that the next time you can avoid it (this could be me, again I'm not a web programmer). So you sit there for 15 seconds each and every time.