HTTP invocations from Hyperlambda

In this tutorial we will cover the following parts of Magic and Hyperlambda.

The purpose of Magic and Hyperlambda is to simplify your life as a developer without compromising scalability, execution speed, or maintainability. One example of this is how easy it is to integrate your Hyperlambda backend with other HTTP based services by utilising its HTTP slots. Let’s illustrate with some code.


If you execute the above Hyperlambda in your Magic’s dashboard “Eval” menu item, you will see something resembling the following.

      Date:"Wed, 24 Nov 2021 05:56:07 GMT"
      // etc ...
         title:sunt aut facere repellat provident occaecati excepturi optio reprehenderit
         body:"quia et suscipit\nsuscipit recusandae consequuntur expedita et cum\nreprehenderit molestiae ut ut quas totam\nnostrum rerum est autem sunt rem eveniet architecto"
         title:qui est esse
         body:"est rerum tempore vitae\nsequi sint nihil reprehenderit dolor beatae ea dolores neque\nfugiat blanditiis voluptate porro vel nihil molestiae ut reiciendis\nqui aperiam non debitis possimus qui neque nisi nulla"
... etc ...

The status code is the value of your [http.get] node after invoking your endpoint, and the headers collection is returned as [headers]. At this point you can easily traverse the array of items returned by the endpoint using code resembling the following.


   // Do stuff with '@.dp/#' here ...

Two lines of code, and you’re returning the result of an HTTP invocation in a structured format, assuming the endpoint you are invoking is returning JSON. The crucial parts as usual is what is not there; No IHttpClientFactory, no IDisposable objects you’ll need to dispose, no IoC container wiring, no async/await statements, etc. By removing the complex parts from your resulting code, maintaining things becomes much easier for both yourself in the future, in addition to making things easier for developers inheriting your project later down the road.

Everything is “syntax”

With the above we imply that the less syntax you’ve got, and the less lines of code you’ve got, the easier it becomes to maintain things in the future. The primary axiom around which Hyperlambda evolves, is that code is technical debt, implying the less code you’ve got, the less technical debt you have. Technical debt again is a bad thing!

POSTing, PUTing and PATCHing data

These three HTTP verbs requires a payload of some sort. You can easily pass in any payload by adding a [payload] node to your invocations, such as the following illustrates.""
   payload:@"{""userId"": 1, ""id"": 1}"

Notice - Due to not passing in a [convert] argument in the above snippet, any response returned by the above endpoint will not be automatically parsed into its equivalent lambda object. If you want to have the response automatically converted to a lambda object you can add a [convert] argument and set its value to boolean true the way we did in our first example above.

You can also post files directly, without loading your files into memory first, by replacing your above [payload] argument with a [filename] argument, having the value of a relative path within your “/files/” folder, that is an existing file on your server somewhere. This has the advantage of resulting in a stream copy operation, never exhausting your server’s memory, regardless of how large your files are. You can also pass in streams as your [content] value in a similar fashion, and/or as expressions leading to streams, strings, or anything really - Including a byte array. Below is an example of passing in a file to some POST endpoint.""

Most of the times you provide a request payload to some endpoint your payload is typically JSON. Hyperlambda implements a lot of helper slots and features to help you out with this. The code below for instance will automatically transform your lambda object to JSON, dynamically populate its id field with the value of [.userId], before transmitting your JSON to the endpoint.


You can do the same with [http.patch] and [http.put]. This simplifies the process of dynamically creating your payloads to some HTTP endpoint.

Changing your Content-Type

Hyperlambda also has strong support for alternative content types, and it automatically transforms the following content types for you.

To use any of the above automatic conversions, make sure you do not provide a value for your [payload], but rather provide a semantic lambda structure such as the following illustrates.""
         // ... etc ...

The above will automatically create a Hyperlambda text representation of the specified lambda object, and transfer that Hyperlambda to the specified URL. Similar things can be achieved with JSON, URL encoded payloads, and multipart form data payloads. To transmit your payload as URL encoded data, you can use something such as the following.""
      // ... etc ...

You can also have Hyperlambda automatically create a “multipart/form-data” [payload] for you. To understand how, please refer to the magic.lambda.mime project that explains how to semantically create a MIME message using Hyperlambda. Then imagine the [payload] node being your [mime.create] node, without any Content-Type, having the Content-Type automatically set to “multipart/form-data”. This allows you to simulate a form data submission, arguably automating the behaviour of a browser. If your endpoint returns any of the following content types, you can add a [convert] argument to your invocation to automatically reverse the process, and have Hyperlambda convert the response to a lambda object.

Notice - Currently there is no automatic conversion from “multipart/form-data” responses to lambda objects.

HTTP headers

Passing in your own HTTP headers is also easy. By default Hyperlambda will associate some default headers with your invocation, specifically the Accept header and the Content-Type header, depending upon whether or not your invocation is using a verb requiring a payload or not. The default values for these headers is “application/json”. If you pass in your own [headers] collection, Hyperlambda will not add these headers for you automatically, and you’ll have to manually add them if you want them to be associated with your request. Below is an example of content negotiation, telling the other party that you’re only interested in Hyperlambda being returned to you.


You can add any HTTP header you wish, including your own custom headers. However, you cannot add content headers with a request that doesn’t accept content.

HTTP slots

There are 5 HTTP slots in Hyperlambda wrapping their associated HTTP verbs. These are as follows.

The exact semantics of what your endpoints are actually doing, differs from API to API - But the above is the default (and correct) way to think of HTTP verbs. Only the 3 last slots in the list above can be given a [payload] or a [filename] argument - And you can only provide one of these arguments. To further dive into the semantics of invoking HTTP endpoints with Hyperlambda you can check out the documentation for magic.lambda.http.