Your adama script is a webserver! Each Adama document is an opinionated webserver supporting GET, PUT, OPTIONS, and DELETE methods. These methods can return HTML, JSON, or XML.

Documents are addressable within a region via a URL of the form:

https://$region.adama-platform.com/$space/$key/$path

Where $region is the region to request the data from, $space is the adama's script name, $key is the document key, and the $path is then handed over to the specified document.

@web get / {
  return {
    html: "Oh, Hello there! this is the root document"
  };
}

@web options / {
  return {
    cors: true
  };
}

Adama normalizes url-encoded bodies into JSON objects, and converts POST into PUT.

message TwilioSMS {
  string From;
  string Body;
}

@web put /webhook (TwilioSMS sm) {
  return {
    xml: "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Response><Message>Thank you for the data. NOM. NOM.</Message></Response>"
  };
}

@web delete / {
  return {
    json: {}
  };
}

The @web handler has @parameters (a special constant) for accessing the query parameters as a dynamic.

The @web handler has @headers (a special constant) for accessing the headers parameters as a map<string,string>.

The return value on a @web is a message that is compile-time interpreted with rules. This message controls the behavior of the web server

The returned message within a @web may contain at most one body field.

The returned message within a @web may set a 'cors' field to true. This will allow the request to be visible to a browser.

@web get / {
  return {json:{}, cors: true}
}

Adama supports caching using both internal and browser caching. This is achieved via the 'cache_ttl_seconds' field.

@web get / {
  return {json:{}, cache_ttl_seconds:60}
}