verb VS ob-restclient.el

plz-see: Interactive HTTP client, similar to restclient and verb, but using Elisp instead of a special text-based syntax.

Ah, btw. I just realized, verb's verb-send-request-on-point doesn't always properly work with source blocks. So I pushed a fix, PR is here.

have you checked this https://github.com/federicotdn/verb . Its emacs package and i am able to write and test api's with text files.

Not as usable for testing, but verb.el[1] is a great tool for doing something very similar in org-mode

[1] https://github.com/federicotdn/verb

I've been a long time user of the org-mode code blocks feature—storing runnable code block inline in the document. Something I've recently started using is verb to include HTTP requests in my documents when I'm testing out web APIs.

Looks also interesting, but it doesn't fit my use cases: I need custom functions to grab values/data from other sources (e.g. pocket-reader.el).restclient` is more about having pre-defined HTTP requests (path, headers, payload etc.) in a buffer and a major mode for executing the requests. Pretty much the same what verb offers.

There is also verb.el.

The readme mentions someone wrote an ob-restclient.el https://github.com/alf/ob-restclient.el

Adding to that, there is also ob-restclient , which could be useful.

Between org babel SQL and ob-restclient literate integration testing and devops have become a (small) part of my team's dev-QA loop. For some things, it's turned out to be indispensable. If you haven't used org-mode and restclient for API documentation yet... give it a whirl. Beautiful exports use read-the-org HTML export theme.