When the API is not documented.

An API Wrapper: (src: @jcsrb)

Client "Can you change your API? If a POST return 201 ours system crashes reading it"
Me "Your system WHAT?????"

GitHub: a marketplace for publicly available API keys

When you start wiring your api and front end together...

The CEO at the company I work at has been telling our partners that our PIA is ready. It took me a week to figure out what the hell a PIA was but he actually meant API

Vision API fail

Day 1: Integrates a new API
Day 2: Updates LinkedIn skills!

This rant just fucked up devRant unofficial for Windows 10.
It causes a JSON syntax error in the API response. 🤣

Thanks @kwilliams! 😁

When your API gives a successful response after 30 hours.
Pure bliss😇

Guys i guess i did it.. more than a year ago i started developing an API.. every admin of it could create new endpoints through the webui.. for rach endpoint you can create an own auth system.. a local company just fucking bought my shit.. a fucking simple API for 12k€.. im kinda proud now because i am only 18

Rant! I found a bug in payment provider's api. The bug involves sending an invalid (!) Stripe ID to that API, (which I send on purpose btw) Which causes a complete white page when you login to their systems and view the details of that customer. Btw the API will accept that invalid Stripe ID without questioning and returns a 200 status code back.

So I send a mail to there support saying "look I found this bug by accident, this is how you can reproduce it"

And the support team send me a message back saying "then don't send an invalid Stripe ID"...

You don't freaking say... *sigh*

I finally get in the mood to work on my side project and GUESS WHAT? THE API IM USING FOR IT IS FUCKING DOWN 😂🔫

I guess Elon Musk is too focused on colonizing mars to the point that he forgot to improve PayPal's API docs.

The API they gave me.

Don't let the guy writing the client define the API. You'll end up with an API that only works for that client.

"I want my API to return insults as error messages if they forget shit"

Uh no, I prefer helping them out by writing proper documentation than sending a giftbox with me flipping them off like Linus Fucking Torvalds for their spaghetti usage of your API

Worked 8 hours on a feature to send attachments from our system (A) to another (B) via B's API. Perfect code, yet I couldn't make it work. B's API has full and extensive documentation for said feature. Contacted B to ask about it, got reply: "Oh yeah - we havent enabled that yet but thought it was handy to have it ready in the docs"

FML

Api means monkey in icelandic, and this is what comes to mind when someone says that a function calls the api.

I'm nearly done importing almost half a million records to Shopify and they just formal email asking me to stop hitting their API so hard.

Why on Earth would an API require me to provide input like this?

{"this": "{\"is\": \"not\"}", "how": "{\"json\": \"works\"}"}

😡

This was posted from my devRant api wrapper. (pls work now ok?)

That moment that the need for a certain service rises and the domain name you want isn't available so you randomly think of another genius one which you can also do a fun 'joke' with and you start building an api around that idea.

This is gonna be fun 😆

Task:
- Replace a 4 year old PHP API.
Old API:
- PHP script writing PHP scripts to /var/www/ for every endpoint needed
- Answers everthing with 200 (not even 404)
DB:
- MySQL 5.6
- ~ 1000 Tables, NO FUCKING FK's
Documentation:
- "Wasn't worth the effort"
New API:
- Not allowed to behave any different
.
.
.
😭

Wondering why there isn’t API documentation.

Published a well documented and tested API with project examples for basic use cases

- "Yeah we didn't use yours because we didn't know how to use it"
- "Did you look at the documentation or code examples?"
- "What where?"
- "In the repo you just cloned"
- "Yeah no <random guy> found a hacky way of doing what we want, his thing just works"
- "I..."

Postman Makes API Development Simple.

Yesterday I received the API documentation from an external company. Over half of the endpoints are either wrong or send invalid data and even the given test requests are fucking failing.
It's a nightmare. We have to finish a website until friday and that company did nothing for 2 months and now we have 2 days left.
The sheer incompetence is too damn high.
My boss said it would have been much better if we had implemented the API on our own. Damn right.

Note to self: ALWAYS cache API calls.

You know what's more irritating than working with a partner who doesn't understand how to properly build an API?

Working with one who fully understands the best practices but doesn't give a shit to implement them until something breaks.

software engineers be like “i don’t read books” then proceed to read api documentation for 4 hours straight

Creating an API to access another API in order to secure your apikey feels... weird

Well... I found the bug...
Thanks Sun/Oracle for the clever API design. ;)

Also... I feel like a noob now :D

Google's API docs are some of the worst I've ever seen... :(

Dear dev at my company:

FUCK YOU AND YOUR PIECE OF SHIT API.

Always satisfying when clients say our API doesn't work and it's shit, only to find out their firewall prevented external calls.

Yea, that's seems about right.When the user gives incorrect password,throw an Internal Server Error.
Great API design!

I can't complain about clients on devRant because I make a REST API and some of my clients use devRant. Oh wait.

Fuck you you fucking fuck, why would you change an api without any notification?

Background: built an app for a customer, it needs to fetch data frlman external api, and save it to a db.
Customer called: it's broken what did you do?!?
Me: I'll look into it.

Turned out the third party just changed their api... Guess I should implenent some kind of notification, if no messages come in for some time...

The Slack API is as pleasant as crabs from a street hooker

Finally I understand what it is like to use a language that does not have any extra resources like stackoverflow or tutorials.

Using ReasonML for my final year project and the only resource I have is the API doc ☹️

Argh! What are HTTP status codes for if you're not using them in your API implementation?!

Fucking morons!

*Creates a rest api that runs on localhost:8080*
*Creates React front end that runs on localhost:3000*
*Sends a GET request to api*
*Cross-Origin Request Blocked: The Same Origin Policy...*

Thats my fucking dev environment and its my local fucking host! Let me just send a fucking request to my own fucking machine you piece of shit! Why the fuck they didn't add an exclusion to fucking localhost?!?

Arghhhh!

The screen I'm looking at that is supposed to be the documentation portal for an API I need to consume :(

!$rant

Playing around with pxgamer's php wrapper for the devrant api and was able to display my devrants avatar image in my portfolio project :D

The avatars items can be updated via the secret api, without an app update

@JS96 seems to be the only person who knows this api (3rd party) since there is a black raven in UWP avatar editor.

@Skayo searching for the api...

@Floydian thanking @trogus

@dfox staying quiet

devRant being an avatar fam.

The company I am currently working for is partnering with another startup. Nothing special about that. We should integrate their API into our system. I wasn't involved in the process when it came to checking there API and if it would work with our Systems. The Person who did that already left the company so I was left behind with some internal documentation. In that Documentation is already written that API is basically trash....

After I started integrating the API I found more and more flaws in the design. They are not sending any responses that would help, when a param is missing or the authentication isn't correct, only 500's . I got some documentation from the partner company so i thought it will be fine as long as the Documentation would be accurate. Turns out the documentation isn't even close to be up to date. Wrong content types wrong endpoints, wrong naming. Basically we could not work with that. We shortly contacted the partner Company. After a few WEEKS we got a response that they updated the Documentation what was right but still not everything was correct. At this point I lost my mind. I researched a little bit about them, the company is founded from 2 young people who basically came strait out of the University and doest have any experience or idea how to build an API. I investigated a little bit there websites.

They have an Admin panel on the base domain from their API but it is only accessible via HTTP. Like WTF , They use HTTP for an Admin Panel this must be a joke right?

They use Cloudflare without a HTTP to HTTPS redirection ???

I really had not that much time to research in there website but if I find these things in 5 minutes I don't want to know what I can find in like an hour.

At the end we will still use them as partners because surprise surprise our company already sold the product that uses their API.

I know that I will be the person who has to help fixing this shit when it breaks and it will break 1000% JUST FUCK THIS SHIT. FUCK THE PARTNER COMPANY. FUCK THERE API.

Just got a response back from an API "you must authenticate to get the goodies"

Oh my god, document your god damn API so I know what to expect! So many bloody edge cases!

Using a library with a terrible API.

Manage to convince management to purchase new library.

Using new library.

Slowly creeps in that new library has a terrible API.

Spent 3+ hours trying to debug an issue I was having with the AdWords API - tore apart my code. Turns out it was AdBlock that was blocking images displayed from the API call. Sigh.

What in the name of fuck is this API?

Hard at work moving the unofficial devRant api documentation to GitBook.

Note: The previous link provided will stop working in due course.

Leader: Meeting starts in 10 mins, we have to show this to the boss
*Team member breaks database silently
*I notice the API has stopped working
Leader: Anyone , anything you want to tell me before the meeting.
*I raise my hand
Me: Yep, the API is not working :)
*Everybody ... FACEPALM

I feel like Coronavirus related API endpoints should only be made available using SOAP

Thats why I hate fucking facebook API.

I came here to rant about how bad Twitter API is but I found out that I already made a rant about that before.

When I use an undocumented API

Why do XML API-s still exist? WHY? It's like walking up to a hot chick hoping to get a number, but she turns around and smiles with no teeth.

Working with Facebook api is the equivalent of being at a dentist where a dentist is an ivory poacher.

1. a client asks you to create an API for their system
2. you do what's requested
3. a year later you are curious how's that API doing. Client's devs decided to

[
"com.client.app.some.Datamodel$Subclass",
{
"someField": [
"java.util.ArrayList",
["SMTH","SMTH_ELSE"]
]}
]

sure, why not, right.....?

Making an API REST endpoint in laravel, adding this just for the fun XD

Developing: An API

Excited: Right now!

Trying to make a basic api, i now have a head ache. Thanks php

When the only "api" documentation you have is a wsdl file...

Creating an API is not too difficult. However, OAuth2.0 is a bitch. Who the hell thought this was reasonable?

Try out foaas.com..best api ever!

How NOT to design an API
¯\_(ツ)_/¯

(After several hours of debugging a returned "mal formed xml" error)

Me: We found out your api does accept our XML only if its elements are in certain order.

They: Oh! yes. :)

Me: ... and since XML should not depend on order, maybe you should fix that. Or at least alert about it in docs.

They: Yes, maybe we should. :)

Me: ... OK

I really hate api response variable names like this. I mean why type "targetitemid" when "target_item_id" is so much more readable?

The world: we found a cure for AIDS.
Hacker news: I don't see a RESTful api endpoint for that, so it's useless.

when the API docs aren't very clear 🥴

What's the most complex programming task you ever had to solve? Or: A "hack"* of a framework/API you came up with to make something work?

*undocumented or unintended use

Locating undocumented API endpoints be like …

Api with no documentation and obscure endpoints

Trying to work with an API that has no response object (it just returns empty arrays if something breaks) and it's JSON is not key-value.. just a bunch of dynamic nested values. just wow.

“The documentation of this API is left as an exercise to the reader.”

"The free plan allows 200 API calls per month, while the paid plan offers unlimited API calls."

wtf is this, 1990 and you're running a raspberry pi as your server? give me a fuckin break

Does anyone know how to post a rant via their api. Trying to make a custom devRant app.

Colleagues of mine, even though they show signs of versioning their api by having "v1" in the URL, keep committing breaking changes to that version. 😂

Me: Could you please provide us with api key so we can add this feature?
Client's IT person: You don't need the api key to develop, their site has documentation so it's not a blocker. I will get you the api key when we are ready to go live.
Me: ...

Not only Synology's REST API documentation is outdated, but I have to deal with this.

Let alone the fact that login in a GET request where username and password are passed as query string in URL.

Microsoft APIs documentation, best API documentation ever!

This API I'm working with has started responding with invalid JSON. I'm going home now.

That moment an API updates and breaks everything.

I worked for this Chinese company, one of their systems that was supposedly handling millions of US$ in transactions per day had an API that returned HTML tables...

I stop you right there commenter, there was no format=json parameter.

Another of their API I gave up on:

Status = 200
Content = "error"

When you click on the github wiki of the API you wanted to use and it shows you the "Create the first page" banner....

Guess I'll have to find another API with proper fucking documentation.

Why is Google so bad in creating good documentations for their API ?

I send exactly what they specify and on some values I just get a 400. thanks for nothing

when youre working on a API and every testCase is all green plus manual testing thru Postman extension is all good..

then makes a web app use that API, authorization works as intended but the token is immedially invalid...

just..how..

Does devrant have a public api? Tempted to write an atom plugin so I can pretend to work, but actually rant.

The flipside of too much googling for each and every API references is that one fails to answer simple interview questions..

Yesterday I've finished the basics of my first api at work. Now going to start on the mvc front end.

Finally learning C# ASP .NET and how to do it right.

So far everyone is happy at work

Before I learned software development, API sounded like a kind of beer.
Today I used the term so often that I have in fact recently tried to order an API at a bar.

So I spent the last 2 hours trying to figure out why my co-workers source when hitting the API I built was not working. They kept saying that the problem was the API and I kept saying that it's their implementation.

Turns out it was their implementation and as well as the API. Their implementation problem was not setting the "Accept" in the header. The API problem is how Laravel will return a JSON error response ONLY IF the "Accept" is set in the header.

I actually documented this into the API documentation but it's obvious that none of my co-workers read that you need to set the headers correctly. I think the more scary thing is that they didn't know the difference between Accept and Content-Type!!

Twitter API really sucks!

oh boy

this api capitalizes properties

...yayyyy

Fixing the API by documenting correct use

By AirspeedSwift @ Twitter

all documentation points to an Invalid auth token being code 400 (ignore the fact that this is a code in the JSON response and not HTTP)

Me: here iz credential. Plz send datas
API: haha fock off and die mate, then credentials you got there aren’t workin’
API: code 998 invalid auth token
Me: *speechless* so that’s why it took me longer than it did to find that error, because YOUR CODE WAS MISSING ALL MY CHECKS FOR CODE 400.

Why can’t people design apis properly.

Weeks after our partner has been nagging us to release to production because we've been putting it off because their API sucks and wouldn't properly work.... we finally did....

except their production API doesnt even work LMAO

When they want you to make stored procedures instead of an API... And there's no DBA.

Wrote a image generation api which uses a headless browser within 2 days ^^ it generates an image like the one below in around 500ms while also loading external resources like that avatar and the icons. ^^

So company x decides that they're depreciating their REST API v1 in favor of v2 which came out like 2 months ago. But I figure: "I'm okay because I use their official Python module". Well v1 went offline two days ago and they still have not updated their own library to work with v2.

Well shit... There really is an API for everything these days huh.

Not sure how these devs made such a system.

Fuck API that can't handle asynchronous operations!

Is there an api to fetch avatars?
@dfox

I mailed to you a long time ago, but not getting any responses.

The moment when your ecommerce site relies completely in 3rd party vendor, and their API is changing without any heads up or announcement

My current project: PHP microframework that makes building REST API kinda 'easy'

But I've read some articles online that building APIs using PHP is a really bad idea. I guess I just wasted my time. Lol. I hate myself.

When you contact the API communication support of the supplier, and several emails and test cases later they still fail to understand your problem.

Which is the worst API you've worked with? Facebook? LinkedIn?

I am writing an api to get data from another api, mix it with some data from a database and then send it back.
I am using nodejs (javascript) to write it but I would like to learn something new. Can you recommend me any languages that I could use for my backend? I was thinking maybe go but I am open for ideas.

When the whole api is using just GET requests, even when updating

Why doesn't Twitter have a public API without authentication for simple stuff, such as reading tweets. One can do that without logging in on the website, why shouldn't code be able to do it.

I am developing a REST api for my android app using laravel.I want to implement web to mobile chat like Facebook's messenger.Any suggestions?

Is there a way to recreate Windows File Explorer? Is there an API for it?

Developed a very simple REST api with pure php. Eventually "api/users/" worked but "api/users" was 301 moved!!.. it was a big problem

See my awesome WhatsApp API using web automation.

I'm selling it though.

When you finally fully integrated an API, fixed the obvious bugs and want to demonstrate it to the client... and just out of the blue your API key is not accepted anymore.

1st post of a series, which I might start called wolkes weird api queries.
Today we have a user that was looking for "big bobs"

RESTful API Question

Let's say when a user do an action, I need to insert a record into a table and then update a record in different table.

Should I write two API routes (PUT, POST) or one route (POST) ?

So I've spent the past 2 months or so integrating a payments provider with a terrible API, only to find that the provider is missing a core feature that they claimed to have in their sales pitch. I have no idea what will become of a large part of my work, it's so draining to work around a total garbage API

Fuck api docs which are blatantly wrong. Wasted several hours on building an API client with pagination according to the api docs.

Turns out the actual implementation did not follow its own spec / api doc and returns values without pagination. And some objects are not objects but arrays.

I mean, next time I build an API client, I'll just fire a dozen requests on the endpoint, see what it wants and see what I get and maybe guess right what it actually does.

That moment when you build your app around a clients development API only to find out their production API responds about 8x slower... I'm sorry, it's not my fault your API server takes 4000 ms for a SIMPLE response. My app isn't the problem. Fix your shit.

How come devRant doesn't have an easy way to find out how their API works? I'm reading off of wrappers to figure out what responses may contain and what the endpoints even are arghh

Does devRant have a public API?

How does the created time work in Devrant's API?
I get 'created_time': 1563478239

It makes literally no sense

APIs, APIs, APIs... I feel like building an API for everything which goes over the wire is a must-have today! Yes it makes sense for decoupling purpose, access control etc (all the things we learned from OOP design principle books when we were in school) but come on, REST API for internal database access when there is something like SQL over JDBC/ODBC/WhateverBC ?? So I have to study the REST API documentation for applying simple where-statements but in API manner...

I always end up building my own wrapper using the REST API rather than using the already existing SDKs to just avoid going through the docs!

Instagram new API app submission models is a piece of crap ..
Mostly developers can not get applications approved ..
Public data should be accessible to developera

How would you support multiple versions of an API and why?

- Multiple version instances behind a load balancer.
- Versioned controllers behind a proxy.

Curious to hear yours thoughts and reasoning.

I'm regretting writing my API in node.... But GoLang is kinda a pain in the ass too.

There's a production site with api call limits. We experienced waaaaay more visitors than usual and I forgot to increase the api call limit, so new users weren't able to do anything. FML again, update emails sent out.

API provider: include a signature based on these fields in this order. DO NOT ENCODE IT!

Implementation works a while, then..

*a wild apostrophe appears*

Signature no longer works.

API Provider: "oh, yeah we escape those."

Arrghhghghghhhghvhxmchsoxnsoxnwl

Not only is it a poor design for signing payloads, the documentation is shockingly poor in it.
Even the implementation example (which is supposedly from their code) doesn't account for any type of escaping or encoding.

Before anyone asks, I can't into details about the implementation.

Wen an api has decided that -1 should === true...

Whoever created the google adsense/admob report api and its documentation : choke on my dick and die you fucking asshole.

I need to link two APIs such that data sent on one API gets processed and it hits a second API with the processed data.
The first API needs to format the data and decide according to data format which second API needs to be used. I checked Zapier and it's working but it is not exactly what i need to do. So are there any options other than setting up my own server?

SMS vs telegram bot vs WhatsApp api ?
Do or die question

So I was reverse proxying this new Social network app's API and saw an interesting endpoint

It was a websocket relaying what each live user's doing every 2.5s, to power the "xyz typing" under a post, or a simple online/idle.
The app's "live posts" ie most-recently created posts was also powered by it since they knew each user's state (instead of a periodic API call)

The performance is good even tho it's a new company + enough users

but now im curious how prevelant state-management is using such websockets .-.

if not taxing, i might move any API call which ive to ping every 15s or less to a live WS

Currently we have to make a new REST API at work. I want to have a clear and functional API (with HAL JSON, that is given). But my colleagues don’t like this, because they don’t like the design (the look and feel) of the HAL JSON responses. They just want an easy API with a nice design, so they want to ignore half of the HAL JSON specification. But a REST API don’t has to be easy and don’t need a fancy design, REST APIs are not for humans but for computers! How can I explain this to them?

Small rant because I’m new here, but…I hate async functions in JavaScript.
Especially when dealing with an API.

"The API will be ready soon", but it comes in late and nothing like the agreed upon spec.

Why the fuck do the browsers need to implement the same API in a different way?

Does anyone know where are the *official* devrant api docs? Tried web searching but could not find them.

Jesus so help me god. I just come here to rant about this FUCKING API PLATFORM. It uses doctrine, i set annotations, YET IT FUCKING KEEPS PUSHING the IRI's. IRI FOR IRITANT. What a fuck fuck fuck fuck fuck fuck system. Bah bah... lost 2 hours because of this SHIT!

Ok, that helps. THANK YOU!

> mfw I created a responsive API totally unconsciously, if not by complete accident

Does the devRant API provide for authenticating and posting new rants?

I've found several unofficial docs that mention grabbing rants and profiles but none that I've found have a method to post rants.

For everybody wondering what's the new endpoint is..

/api/me/subscribed-feed

you can also provide an `filter`, which is comma-seperated with the possible values:
- posted
- commentedOn
- liked

"View more suggested users" does NOT load more. It simply doesn't show everything from the response.

Fucking google maps JS api. One should think that a company as large as google should be capable of providing a reliable api. But this fucking api just decided for the second time in two weeks just to stop working.

After the api failed for the first time i found out that the provided url actually fetches the experimental version of the api (yes you read that correctly a fucking unstable version is the default version). To get the stable version of the api one has to add v=3 to the request. But even after adding the version the api just broke again today!

Fuck it! Google get your shit together!

Just thinking about switching to OSM...

!rant

build me a little tool today, which make use of the spotify API.
Just want to thank the devs of this API. Well documented, good examples, easy to use.
There are some good devs Out there 😊

I setup a Firebase project, and then remove the authentication completely, so I can send API call freely.

After 2 weeks I am still alive...

That's amazing!

Developer tools needs to tell us from which file the API was called.

What's a good REST API to learn from where I can make some simple gets puts and posts without too much setup?

I'm creating a messenger app (I know there are many, but it's different)

Any suggestion for API gateway? I was looking for ready made solutions to save time. I heard Kong is good. But I want to know your suggestions.

The Amazon MWS API is so utterly shite! Offers error messages sometimes then others tells you to upload your file to their file checker. Their file checker doesn’t accept XML so why say that?

Who on earth develops and documents their shit APIs?

Fuck you Amazon

Is logout useless on a Rest API that uses JWT token?

Discuss

Hey guys, is graphQl worth learning? Rest API is so easy to work with...

Laravel + bootstrap vs Vue + standalone API?

Trying to make a site that requires an external API and that API limits you to certain calls per certain time before they ban you for 24 hours and asking yourself how not to get banned :| *I'm new to webdev*

I am trying to implement an API. It has a very good documentation, everything is written clear and simple, along with

- HTTP 401 on unauthorized request and
- Error codes from 1-35 with definitions

Opened the provided sample file, changed the username, password and client code fields to our own in the source, then tried the request. The Response:

HTTP 200
{"ErrorCode":-1,"ErrorDescription":"Unauthorized."}

Well, thank you very much! 🤬

Can anyone give me links to any Devrant API? Thinking of starting work on creating a Native Android Devrant app as a side-project.

So we had a service provider which would provide climate info. The service is paid for. Then suddenly we started getting irrational or no data. When asking the provider, he said their job is to provide the api and they're not responsible for the quality of the data which apparently comes from other places. So we basically pay for an api which we could have done ourself....

Trello has an explicable REST API documentation. I like it.

Damn writing api documentation is such a pain, I am following bunch of flow at the same :(

I've got a bit funny situation.
I wanted to make small application to speed up my dad's job, app is about duplicating models in X website (I don't want to say directly what website).
So I started by checking it has API, Yup, It has, but you need OAuth ID, to get it you need to write to support.
So I did it, my mail was something like that: "Hello, can I get access to your API, I want to make app to duplicate models with same settings, Thanks"
I've got an answer like that "Hello, our website doesn't have duplicating feature."
My reaction was: Wtf? I know it doesn't have that feature, That's why I want to make it. How did he get hired as technical support?
Maybe it's not the most exciting story, but I thought it could be intresting :)

Just removed an API key from one of my GitHub repos (yeah I know API keys don't belong there) and at the moment i pushed the corrected file, I got an email from GitGuardian that it discovered a key in my Repo although i deleted it. Anyone else experienced something similar?

Third party asks to remove access_token from the API URL.

BTW, they are a unicorn here in India.

Your API returns, encoded as json, the ENTIRE FUCKING CSS FILE!?!?

Anyone know how to make an API for sites that dont have an API (or pull information from sites)

What do you guys desire from an API, apart from well-written documentation? One of the things I want to work on is a website with an API, and I want to know what you would want from one. Eg version numbers, error fields, authentication, stuff like that.

If 99% of fetch use case is fetch(url).then(r=>r.json()), API should have been fetch.json(url)

When you have to debug getting data from an api that is only accessible for a couple of hours a day. 1 am to 5 am...

When a REST API developer is bored. He sends message to everyone.

Need some help finding a free weather api please.

I need to be able to search the api based on temperature or humidity. Alternatively I could locally store the next 2 weeks of data for every country in a database and update it every night with a cron.

Has anyone used weather APIs before? Could you suggest me some?

Document your API properly or use Swagger!

My colleague has been up my ass for a google api key but they don‘t want to pay, smh my head twice

I've decided that I want to make a REST API using Flask/Python. I've researched it for a few days, but can't seem to find anything close to a definitive answer: How should I structure the application?

I've found a lot of people talking about using Blueprints, and I'm leaning towards that, but I'm wondering if there aren't "better" frameworks for building a REST API? What do people here recommend that I look into?

Testing API endpoints