#API Programming

[kbvresearch]

Unlocking the Power of APIs: Becoming an API Intermediate

The world of software development is driven by connectivity and integration. APIs, or Application Programming Interfaces, lie at the heart of this digital ecosystem. They enable different software systems to communicate and share data seamlessly. As you delve deeper into the world of APIs, you’ll embark on a journey from novice to API Intermediate, acquiring a formidable skill set that empowers…

[alycesutherland]

Progress:

Okay so the authentication for spotify is hard for me to understand and requires user authentication, then making a token request that while expire in an hour. So i focused on what I did know how to do and what I had access to token wise. The Spotify developer home page has a temporary access token for demos. I took that token and made a function to make get request to the API and two functions for top tracks and top artists. Then made some functions to print them in my terminal. Here is what my end product looked like in the terminal.

The data for tracks is proving to just show a years worth of listening even though I specified long_term in my get request.

Here is my code:

I tried just doing track.artist but Spotify handles that as multiple artists so I had to handle them as such.

Next Steps: Tackling the user authentication and token requests and including it in this code.

(Also yes I know that is a concerning amount of My Chemical Romance tracks. I had my MCR phase strike up again with a passion last October and I am still balls deep in it.)

[rosepetalkitty]

if anyone sees this and has worked with Cloudflare Workers pretty please explain to me how the fuck I need to configure Vite to get my React Router v7 project to build T-T I'm losing my mind, yes I'm aware that Node APIs don't exist on Workers but for the love of God how do I get RR7 to stop trying to use them 🥲🔫

[sciencemenace]

Working with the Tumblr API is like nothing else

[multidimensionalsock]

REST APIs

REST (Representational State Transfer) is a type of API where all the information needed to perform an action is passed to the API at the time the request needs fulfilling. The server does not need previous knowledge of the clients session in order to fulfill their request.

The alternative to this is that the client having a 'session' with the server, where the server keeps information on the client while it's active, which can take up a lot of server processing power and memory. For large services handling possible hundreds of thousands of clients at a time, keeping a 'connection' can take up a lot of server processing and memory.

REST speeds up processing time for both the server and client. With sessions, they can end up split over multiple servers, meaning servers have to communicate to get data which can slow down response time. Because the server needs no prior knowledge of a client, any client can handle any client's request easily, which also makes load balancing easier, a request can be sent to any server that can handle it which is currently the least busy.

All REST APIs use HTTP methods. A client sends a request via HTTP to a specific endpoint (location on the web), along with all of the information needed to complete that request. The server will then process it and send back a response.

Core features of REST:

Client-Server Architecture - a client that sends requests to a server, or set of servers via HTTP methods.

Stateless - client information is not stored between requests and each request is handled as separate and unconnected.

Cacheability - data that is expected to be accessed often can be cached (saved for a set amount of time) on the client or server side to make client and server interactions quicker.

Uniform interface - no matter where an endpoint is accessed from, its requests have a standard format. Information returned to a client should have enough information and self description that the client knows how to process it.

Layered system architecture - calls and responses can go through multiple intermediate layers, but both the client and server will assume they're communicating directly.

Code on demand (optional) - the server can send executable code to the client when requested to extend client functionality.

[codemerything]

Introduction to APIs and Web APIs

The illustration above is the best way you can think of how APIs work and I talk more about it in my new article about APIs. I really love the concept and logic of APIs, it proves that collaboration is a huge part of programming and APIs solidify that. I hope you enjoy the read and also this is my first article and I intend to write more about technologies that interest me and maybe tips and tricks in the future.

[anndcodes]

03/10/23

i finished shecodes week 5 homework, and now the app we're building has real-time temperature, as well as description of temperature, humidity and wind! you can search the city or you can get temperature of your current location!! this is really cool!

learning about api has being really exciting, so i made a simple page using meow-facts api where you click meow to get facts about cats, you can check the repository and the live page!

really excited to learn more about api!

ps: this sakura chocolate is the cutest thing! i almost didn't eat it 🥺

[angeliqueoolala]

When in doubt, scrape it out!

Come find me on TikTok!

[bluemanedhawk]

I want to make this piece of software. I want this piece of software to be a good piece of software. As part of making it a good piece of software, i want it to be fast. As part of making it fast, i want to be able to paralellize what i can. As part of that paralellization, i want to use compute shaders. To use compute shaders, i need some interface to graphics processors. After determining that Vulkan is not an API that is meant to be used by anybody, i decided to use OpenGL instead. In order for using OpenGL to be useful, i need some way to show the results to the user and get input from the user. I can do this by means of the Wayland API. In order to bridge the gap between Wayland and OpenGL, i need to be able to create an OpenGL context where the default framebuffer is the same as the Wayland surface that i've set to be a window. I can do this by means of EGL. In order to use EGL to create an OpenGL context, i need to select a config for the context.

Unfortunately, it just so happens that on my Linux partition, the implementation of EGL does not support the config that i would need for this piece of software.

Therefore, i am going to write this piece of software for 9front instead, using my 9front partition.

[cyberm0sh]

nerdy website people!!

i am looking for a free website hosting service that supports programming languages and server-side scripting for a personal project

i’ve tried neocities and unfortunately they do not support server side scripting!!

thank you sososo much for any leads <3

[marxist-kasaneteto]

i dont think ive complained enough about how absolutely shitty the tumblr api is. the documentation is like. mediocre, to begin with. the actual api? the /blocks route gives you the blogs a blog has blocked if you GET it, but POST it? well now youre blocking a blog. dont be deceived by the plural though - to block multiple blogs you need /blocks/bulk. oh also using the... DELETE method (??) you can remove a block, still via /blocks. the /post route is the legacy post format. /posts is what youre looking for, but dont GET it, because then youre fetching a blogs posts. again, dont be deceived by the plural, but this time there is no bulk route. oh and of course /posts/{post id} gets a post... but with POST it edits the post. now with this theme of incorrect plurals, youd at least expect them to have correct plurals, but no! in order to retrieve drafts you use... /posts/draft. there are some communities routes, but guess what? theyre listed in a different format in the documentation to everything else! to be honest, its a better format, but i guess they couldnt be bothered to update their docs.

and then, the /user/dashboard route. heres what the docs say:

(this the ONLY way to get random posts btw)

simple enough... naturally you would scroll down for more info but... thats it. after that tiny description, there is a horribly layed out list of arguments and their descriptions, info on the response format, and nothing else. what dashboard is it getting? who knows! it doesnt seem to be the Following tab - which is in order of recency - so i can only assume its For You. it also, by default, returns posts in the legacy format, which is much less convenient than their Neue Post Format (??). posts are also returned without blog info and instead with just a blog name, and, for whatever reason, there is no argument to change this. i dont remember what i did to get around this, but it was probably taking that blog name and running it through the /info route or getting the posts and then getting them again with the /posts/... route (which does return blog info).

ok.. so its badly documented and inconvenient to use. big deal! except... theres more. if youre going through dashboard posts individually, like i do for my bot, youll probably use the offset argument parameter - the offset from the first post on the dash - to specify which post to get. however at somewhere around an offset of 250, it stops returning new posts. just the same one over and over. probably a rate limit right?

?????

you might be thinking "its probably that 300 api calls limit and youre just using a few extra calls" but thats wrong. for starters around 50 extra calls just doesnt sound accurate for what im doing. it would most likely be way more than that or way less. and even if im wrong, it doesnt reset after a minute. i have no idea when it resets, in fact. sometimes it feels like more than an hour, but i havent timed it. i also havent tested what happens if i go straight to 250, which i probably should do. on top of all that, i dont think this is what would actually happen if i got rate limited, its just the only remotely possible explanation i can think of.

another thing is that you cant get the full text of a post natively, only the content of the reblog. i had to write my own method for that. also - this is kinda nitpicky - you cant easily get the blog that last contributed in the thread, only whoever last reblogged it (who might have reblogged it without saying anything). by that i mean 5 people might have reblogged it without saying anything since anyone added anything to the thread, but you can only find that 5th person (easily). the workaround is to check if the person who last reblogged it said anything, if not get the last person in the 'trail', which is a list of reblogs in the thread that said something that doesnt include the last reblog. this also... doesnt work sometimes i guess? i didnt bother figuring out why, but one time out of the blue it gave me an error when trying to get the name of the last person in the trail.

i hate the tumblr api

[rabbiteclair]

today's great work conversation:

"hey, I posted to that API you wrote, and the data that came out on the other side contains stuff from the database instead of my request body. is that a bug?"

"why did you submit a request body? there's no mention of one in the story. that API doesn't expect, or look at, a request body. how did you even decide what to put in the body?"

"well it was left over from a different test and I didn't remove it"

[valaratminaforaldrar]

studying computer science atm gives me such whiplash youll be in a group project and theyre using chatgpt for?? every little google search?? and like i'm not even talking about the actual coding yesterday i witnessed someone use chatgpt to figure out where to find a feature in github like my guy! github is not a niche little website i promise you you can google that question and get an answer just as quickly????

[youling-the-ghost]

the urge to fuck around with the AO3 API is very strong right now

[scuggle]

does

does tumblr have an API

hey, @staff, do you guys have an API?

[brightgreendandelions]

what do you think is the chance it will work?

(i haven't tested this at all)