Magic Cloud

An Open Source Application Generator

Magic Endpoint

Magic Endpoint is a dynamic endpoint URL controller, allowing you to declare endpoints that are dynamically resolved using your IExecutorAsync service implementation. The default implementation of this interface, is the class called ExecutorAsync, and the rest of this file will be focused on documenting this implementation, since it’s the default service implementation for Magic Endpoint - Although, technically, you could exchange this with your own implementation if you wish, completely changing the behaviour of the library, if you wish to for instance resolve endpoints to Python, Ruby, or any other dynamic programming language implementation, and you have some means to execute such code from within a .Net 5 environment.

The resolver will be invoked for all relative URLs starting with “magic/”, for the following verbs.

The default service implementation will resolve everything after the “magic/” parts in the given URL, to a Hyperlambda file that can be found relatively beneath your “/files/” folder. Although, technically, exactly where you physically put your files on disc, can be configured through your “appsettings.json” file. The HTTP VERB is assumed to be the last parts of your filename, before its extension, implying an HTTP request such as the following.

GET magic/modules/foo/bar

Will resolve to the following physical file on disc.


Notice, only the “magic” part of your URL is rewritten, before the verb is appended to the URL, and finally the extension “.hl” appended. Then the file is loaded and parsed as Hyperlambda, and whatever arguments you pass in, either as query parameters, or as your JSON payload URL encoded form arguments, etc, is appended into your resulting lambda node’s [.arguments] node, as arguments to your Hyperlambda file invocation. The resolver will never return files directly, but is only able to execute Hyperlambda files, so by default there is no way to simply get files.

The default resolver will never allow the client to resolve files outside of your main “/files/modules/” folder. This allows you to safely keep files that other parts of your system relies upon inside your dynamic “/files/” folder, without accidentally creating endpoints, clients can resolve, resulting in breaches in your security. Only characters a-z, 0-9 and ‘-‘, ‘_’ and ‘/’ are legal characters for the resolvers, and only lowercase characters, to avoid file system incompatibilities between Linux and Windows.

Below is probably the simplest HTTP endpoint you could create. Save the following Hyperlambda in a file at the path of modules/magic/foo1.get.hl using for instance your Magic Dashboard’s “Files” menu item.

   result:Hello from Magic Backend

Then invoke the endpoint using the following URL.



The default implementation can explicitly declare what arguments the file can legally accept, and if an argument is given during invocation that the file doesn’t allow for, an exception will be thrown, and the file will never be executed. This allows you to declare what arguments your Hyperlambda file can accept, and avoid having anything but arguments explicitly declared in your Hyperlambda file from being sent into your endpoint during invocation of your HTTP endpoint.

An example Hyperlambda file taking two arguments can be found below.

   .:" - "

If you save this file on disc as /files/modules/magic/foo2.get.hl, you can invoke it as follows, using the HTTP GET verb.


Assuming your backend is running on localhost, at port 55247 of course.

JSON payloads and form URL encoded payloads are automatically converted to lambda/nodes - And query parameters are treated indiscriminately the same way as JSON payloads - Except of course, query parameters cannot pass in complex graph objects, but only simply key/value arguments. Only POST, PUT and PATCH endpoints can handle payloads.

Notice - To allow for any arguments to your files, simply ommit the [.arguments] node in your Hyperlambda althogether. Alternatively, you can also partially ignore arguments sanity checking of individual nodes, by setting their values to *, such as the following illustrates.


In the above arguments declaration, [arg1] and [arg2] will be sanity checked, and input converted to string or date (DateTime) - But the [arg3] parts will be completely ignored, allowing the caller to invoke it with anything as arg3 during invocation - Including complete graph JSON objects, assuming the above declaration is for a PUT, POST or PATCH Hyperlambda file. The ‘*’ value for an argument also turn off all conversion, implying everything will be given your lambda object with the JSON type the argument was passed in as.

All arguments declared are considered optional, and the file will still resolve if the argument is not given, except of course the argument won’t exist in the [.arguments] node.

To declare what type your arguments can be, set the value of the argument declaration node to the Hyperlambda type value inside of your arguments declaration, such as illustrated above. Arguments will be converted if possible, to the type declaration in your arguments declaration. If no conversion is possible, an exception will be thrown.

Although the sanity check will check graph objects, passed in as JSON payloads, it has its restrictions, such as not being able to sanity check complex objects passed in as arrays, etc. If you need stronger sanity checking of your arguments, you will have to manually check your more complex graph objects yourself.

Accepted Content-Type values

The POST, PUT and PATCH endpoints can intelligently handle any of the following Content-Types.

JSON types of payloads are fairly well described above, and URL encoded form payloads are handled the exact same way, except of course the [.arguments] node is built from form values instead of JSON - However, internally this is transparent for you, and JSON, query parameters, and URL encoded forms can be interchanged 100% transparently from your code’s perspective. Hyperlambda content will be passed in as a [body] argument to your file as text.

All other types of payloads will be passed in as the raw stream, not trying to read from it in any ways, allowing you to intercept reading with things such as authentication, authorisation, logic of where to persist content, etc. To see how you can handle these streams, check out the “” project’s documentation.

Meta information

Due to the semantic structure of Hyperlambda, retrieving meta information from your HTTP endpoints using this module is very easy. The project has one slot called [endpoints.list] that returns meta information about all your endpoints. This slot again can be invoked using the following URL.


This endpoint/slot will semantically traverse your endpoints, recursively loading up all Hyperlambda files from disc, that are resolved from a valid URL, and return meta information about the file/endpoint back to the caller. This allows the system to easily figure out things such as the following about your endpoints.

This slot/endpoint is what allows you to see meta information about all your HTTP REST endpoints in the “Endpoints” menu item in the Magic Dashboard for instance. The return value from this slot/endpoint again, is what’s used as some sort of frontend is being generated using the Magic Dashboard.

Extending the meta data retrieval process

If you wish, you can extend the meta data retrieval process, by invoking ListEndpoints.AddMetaDataResolver, and pass in your own function. This class can be found in the namespace.

The AddMetaDataResolver method takes one function object, which will be invoked for every file the meta generator is trying to create meta data for, with the complete lambda, verb and args of your endpoint. This allows you to semantically traverse the lambda/args nodes, and append any amount of (additional) meta information you wish - Allowing you to extend the generating of meta data, if you have some sort of general custom Hyperlambda module, creating custom HTTP endpoints of some sort.

Notice - The function will be invoked for every single Hyperlambda file in your system, every time meta data is retrieved, so you might want to ensure it executes in a fairly short amount of time, not clogging the server or HTTP endpoint meta generating process in any ways.

Additional slots

In addition to the meta retrieval endpoint described above, the module contains the following slots.


Unless you explicitly change the Content-Type of your response object, by using the [response.headers.add] slot, a Content-Type of application/json will be assumed, and this header will be added to the resulting HTTP response object. If you wish to override this behavious and return plain text for instance, you could create an endpoint containing the following.

return:Hello from Magic Backend

Notice - If you intend to return anything but JSON, you must set the Content-Type header, because the resolver will by default try to serialize your content as JSON, and obviously fail unless it’s valid JSON.

You can also return stream objects using for instance the [return-value] slot, at which point ASP.NET Core will automatically stream your content back over the response object, and Dispose your stream automatically for you afterwards. This allows you to return large files back to the client, without loading them into memory first, etc. If you do this, you’ll have to change your Content-Type accordingly.


Since cookies have more parameters than just a simple key/value declaration, the [response.cookies.set] slot takes the following arguments.

Only the [value] from above is mandatory. To delete a cookie on the client, set the expiration date to a value in the past.

Project website

The source code for this repository can be found at, and you can provide feedback, provide bug reports, etc at the same place.

Quality gates


This project is the copyright(c) 2020-2021 of Thomas Hansen, and is licensed under the terms of the LGPL version 3, as published by the Free Software Foundation. See the enclosed LICENSE file for details.