You can.

...or you can tell the LLM "write me a go application that adds links from this JSON dump of wallabag.it to raindrop.io" and it's done in 10 minutes.

(It did use the wrong API for checking if a link already exists, that was an additional 5 minutes)

I've been doing this shit for a LONG time and it'd take me a way longer than 10 minutes to dig through the API docs and write the boilerplate required to poke the API with something relevant.

No, you can't have it solve the Florbargh Problem, but for 100% unoriginal boilerplate API glue it's a fantastic time saver.

How do you deal with LLM hallucinating api parameter or endpoints or using imaginary library?

You notice it and tell it what to use instead

Then I write it myself or tell it to correct itself. They tend to be confidently incorrect in many cases, but especially with the online ones you can tell them that "this bit is bullshit" and they'll try again with a different lib.

Works for common stuff, not so much for highly specialised things. An LLM can't know something it hasn't been "taught".