I’m new here and this is my first post on the Drafts community forum.
Drafts has a rich and extensive documentation on it’s functionality and various use-cases, including integration of x-callback-url.
The official x-callback-url website introduced a list of (third-party) Apps that support the specification.
Throughout the years, several attempts have been made by members of the community to update / document the list of Apps.
I.e
One Tap Less_https://onetapless.com/library
AppTalk_https://app-talk.com/
Opener_https://github.com/timonus/OpenerManifest
I’ve noticed that it can be quite a challenge to find official documentation on the use of x-callback-url for certain iOS Apps. That’s why I decided to gather all information I could find and list it in an Airtable base.
Nicely done. I’ve been really bad at maintaining the list on the x-callback-url site, mostly updating it when a developer contacts me and asks to be added. It will be good to have a better resource. I will add a link to the apps page.
Thank you so much! I think you write the best App documentation out there.
What I would like to suggest is to (at some point) deliver the data I gathered to you, formatted the right way so that you could easily update the page with a few clicks. That would save you a lot of work and I would be more than happy to spend some of my time by contributing to the page.
I’m brand new to drafts.app and was looking for Spark’s x-callback-url scheme; unfortunately I couldn’t find it on your site. (Apologizes if it’s there and I overlooked it.)
However, I did find it here:
Perhaps you’d like to look at this page and incorporate some of its information into your site. (No offense meant.)
Are you sure there is x-callback-url support and not just URL support? I’ve looked at the old cached URL scheme info from Read let and the site you link to. Both only discuss URL schemes. When I tried to modify it to an x-callback-url, Spark gives me an “Oops” error message.
In case is helps, you can read about x-callback-url here:
Essentially they are a way of transferring control back to a calling app, with details of any success or failure, whereas a typical URL will transfer control to an app, but not back again - that is where the callback element comes in.
Exactly! I had included it in a seperate list of Apps with unverified x-callback-url support. I’ve noticed that it’s still quite common for people to mix up URL schemes with x-callback-urls. There are also some developers / bloggers who mix these up in their own documentation or write-ups, so I get why this is confusing.