ApiV2-GraphQL-Docs VS interfaces

I know when people are trying to do those kind of things, and fancy graphs like this one they use MAL's API, or Anilist's API. Those let you get any kind of info in their database, including anime and genre.

https://github.com/AniList/ApiV2-GraphQL-Docs/issues/32 either I'm misunderstanding but looks like you can as this user had trouble with it but then got it working

My question is this - I plan on using an API because one of the requirements is to implement an API, and I've found this https://github.com/AniList/ApiV2-GraphQL-Docs but I honestly don't even know where to start cause I never worked with API's before, and I'm like a month into android dev so I literally am new and confused. I am kinda regretting choosing this idea since it looks like I'm kinda over my head LOL but I do have a good month and a half, two months.

I like how wasmCloud does things - they define the interface using smithy like this https://github.com/wasmCloud/interfaces/blob/main/httpserver/httpserver.smithy (in the httpserver interface, the wasm side receives http requests as structs, and replies with responses as structs. The native-code side is responsible for listening on the TCP port etc. There are a bunch of other first-party interfaces, including an httpclient interface, for outgoing requests initiated by wasm). They then generate basic interface code for all supported languages from the smithy definitions. They also hand-write some helper functions, to make things easier on the wasm side (this isn't the same from language to language - there are more helpers for rust than other languages).