HTTP Request Structure

HTTP requests are made up of four parts. Take this example client request to a FHIR API:

The method indicates the action to be performed on a resource within the API.

With Iguana’s net.http.* library, you can invoke different HTTP methods:

net.http.get{} - query or retrieve resources.
net.http.post{} - to add or create a resource.
net.http.put{} - update an existing resource.
net.http.delete{} - remove a resource.

The URL defines where the client can access the desired resources - for example the Patient resource.

url='http://hapi.fhir.org/baseR4/Patient'

Query String:

For GET requests, the URL may also contain any necessary query parameters like the id of the patient you are searching for. The ? indicates the end of the url and beginning of the parameters. Key-value pairs are separated by &.

http://hapi.fhir.org/baseR4/Patient?id=12324&name=Bruce

These URLs can be hardcoded if necessary, or built using various URL Encoding strategies.

The header includes metadata requirements defined by the API to provide information about the request.

headers= {
  ['Content-Type'] = 'application/fhir+json',
  ['Authorization'] = 'Bearer '..token
}

This can contain information such as:

Connection and content types
Authentication information like credentials, cookies, or an access token
MIME types
Entity tags (ETAGS)

Some requests require a body where we add the resource content or additional information to be sent to the server. The HTTP formats will typically be specified by the API you’re working with and often requires the appropriate Content-Type header. Common formats include:

JSON

See Parsing and Serializing JSON.

XML

See Working with XML

Form Data

Form data for data sent from a web form. Typically handled in Lua using string or table functions, storing data as name-value pairs.