By @edent · api data finance money openbanking programming · 3 comments · 550 words · read ~468 times.
A few weeks ago I was moaning about there being no OpenBanking API for personal use. Thankfully, I was wrong! As pointed out by Dave a company called Nordigen was set up to provide a free Open Banking service. It was quickly bought by GoCardless who said: We believe access to open banking data should […]
Continue reading →By @edent · api money openbanking · 16 comments · 600 words · read ~333 times.
The recent news that MoneyDashboard is suddenly shutting down has exposed a gap in the way OpenBanking works. It is simply impossible for a user to get read-only access to their own data without using an aggregator. And there are very few aggregators around. Why is it impossible for me to get programmatic access to […]
Continue reading →By @edent · api jetpack WordPress · 600 words
People can subscribe to receive my blog via email. This is managed by the JetPack plugin. I want to be able to display something like "Join 1,234 subscribers and receive updates via email". So, how do I get the subscriber count from the API? As documented in the JetPack HTTP API, it is possible to […]
Continue reading →By @edent · api security twitter · 2 comments · 650 words · read ~170 times.
My CDN just asked me for all my Twitter API keys... WTF? This would give them complete access to my app's Twitter account, the ability to send and receive messages, and anything else that my API key allows. Giving them - or anyone - the entire set of credentials would be a very bad idea. […]
Continue reading →By @edent · api eink nook rail tfl · 2 comments · 750 words · read ~416 times.
Last year, I blogged about how I turned an old eReader into an Information Screen. I've since updated the display to show me three different sets of transport information. At a glance, I can see the next bus, whether there are delays on the Elizabeth Line, and if my regular trains are running. Here's how […]
Continue reading →By @edent · api mastodon MastodonAPI NaBloPoMo python tutorial · 1 comment · 1,500 words · read ~1,048 times.
The social network service "Mastodon" allows people to publish posts. People can reply to those posts. Other people can reply to those replies - and so on. What does that look like in the API? Here's a quick guide to the concepts you need to know - and some code to help you visualise conversations. […]
Continue reading →By @edent · api books libraries · 3 comments · 500 words
This is a mixture of lament and how-to guide. Suppose you've reviewed lots of books. It's pretty easy to generate a link to let people buy the book at Amazon or any other online store. But how do you link to a user's local library? You can't. There is no "search every library in the […]
Continue reading →By @edent · api developers · 3 comments · 300 words · read ~11,431 times.
M'colleague Charles has introduced me to the most spectacular phrase - "Time To 200". That's a measurement of the length of time it takes a new user to go from signing up to your API to getting their first HTTP 200 response. Think about the last time you started using a new API... Fill in […]
Continue reading →By @edent · api ODCafé ODcamp · 2 comments · 450 words · read ~1,309 times.
(This post written partly to tease my delightful colleague Charles, but also as a way of thinking about user needs.) During a recent Open Data Café, one of the guests made an entirely reasonable point. An API only method of getting data is elitist. Already having my assumptions tested - are APIs elitist? food for […]
Continue reading →By @edent · api hack twitter · 2 comments · 400 words · read ~819 times.
Recently, one of the accounts I follow on Twitter was hijacked. It was turned into a PS5 giveaway scam. The people who hijacked the account changed the name, avatar, and deleted all the previous Tweets. Here's how I found who the original owner was, and managed to contact them. A Twitter account has a screen […]
Continue reading →