You are viewing the documentation for Blueriq 14. Documentation for other versions is available in our documentation directory.

The Blueriq web application is equipped with a REST API to expose methods to allow clients to control the flowing of the application. This page gives a description about the available services. For all of the below endpoints, an Accept header of application/json must be present in the request.


Authentication

Login user

POST /api/v2/login

Description

Login the user with the provided credentials

Request body



{
	username: string,
	password: string
}
Example request
{
	"username": "testUser",
	"password": "secret"
}

Before release 12.10, Blueriq expected the username and password to be in the request parameters of the login request (e.g. http://.../api/v2/login?username=testUser&password=secret). Since release 12.10, the username and password are retrieved from the login request body. For backwards compatibility the login information can still be retrieved from the request parameters as well.

The material theme sends the login information in the request body by default from release 12.10. It is possible to configure the theme to still use the legacy request parameter method of logging in, by configuring the backend module in your theme:

app.module.ts
    V2BackendModule.forRoot({
      baseUrl: ....,
      legacyLoginWithQueryParams: true,
    }),

Response

204 No Content, if successful.

401 Unauthorized, if unsuccessful.



Logout user

POST /api/v2/logout


Parameters

Query ParameterExpected TypeDescriptionRequired
redirect_uristringURL to redirect to after logoutConditional (see Response)

Description

Logout the current user and close all Blueriq sessions

Response

204 No Content

302 Found

  • if redirect_uri parameter is present
  • the Location header contains the redirect_uri

400 Bad Request

  • if the Runtime is configured with OpenID Connect and SSO Logout, and no redirect_uri parameter was received
  • if a whitelist is defined for the redirect_uri parameter and the received redirect_uri is not whitelisted




Starting a Blueriq session

Start Shortcut

POST /api/v2/start/{shortcutName?}

Description


Starts a session by specifying the name of a shortcut.


Parameters

URL SegmentExpected TypeDescription
shortcutNamestring

The shortcut name, leave empty to start the default shortcut


Example response

{
    "sessionId": "2f177274-514d-4be9-aa3d-4a550ab9e724",
    "sessionTimeout": 1800
}



Start Project

POST /api/v2/start?project=export-kinderbijslag&flow=Main

Description

Starts a session with project parameters. This endpoint may be disabled in production for security reasons, so using shortcuts is preferred.


Parameters

Query parameterExpected TypeDescriptionRequired
projectstring

The project to start

Yes

flow

stringThe flow to startOnly required if more than one exposed flow is present in the project
versionstringThe branch versionNo
languageCodestringThe project languageNo
uistringThe UI variant to use, by default only mvcis supportedNo
themestringThe project themeNo
channelstringthe project channelNo

Example response

{
    "sessionId": "2f177274-514d-4be9-aa3d-4a550ab9e724",
    "sessionTimeout": 1800
}


Interacting with a session 

After having started a session using one of the /api/v2/start endpoints, its initial page contents may be obtained via a POST to /api/v2/session/{sessionId}/load. The result of this call is the full page model, necessary for initial rendering of the page. Subsequently, events may be submitted to the runtime via a POST to /api/v2/session/{sessionId}/event, resulting in a response containing all changes (add, update, delete). In Blueriq each session may be part of a hierarchy of sessions. For example, in a DCM application, the session of a flow widget is a child session of the main dashboard session. An event in one session may cause changes in other sessions if Portal Messages are thrown. Therefore, the response  of /api/v2/session{sessionId}/event endpoint will contain changes in all sessions in the heirarchy. An example response containing the changes:


Change Events
{"events":[
	{"sessionId":"27390ee2-4968-4f27-ae71-3d6516ba06ec",
	 "changes": {
		"changes":[
			{"type":"add",
		 	"key":"P521-C0-F1",
		 	 "model":{
				"key":"P521-C0-F1",
				"name":"e.a2",
				"properties":{},
				"questionText":"q2",
				"explainText":null,
				"dataType":"boolean",
				"rejectedValue":null,
				"readonly":false,
				"required":false,
				"hasDomain":false,
				"multiValued":false,
				"refresh":false,
				"displayLength":-1,
				"domain":[],
				"messages":[],
				"values":[],
				"type":"field",
				"styles":[]
				}
			}
		]
	}
]}

In this example a field is added to the page. The available properties per element are listed in the REST Page Models V1.

Serialization

The serialization of page element to datamodel is handled by the IApiRendererFactory, this renderer factory can be overridden to customize the serialization. In Java by use of the AquimaApiRendererFactory annotation.





Load session information

After a session has been created using /api/v2/start, the current state of the session can be obtained through:

POST /api/v2/session/{sessionId}/load


Description

Loads the information of the provided session.

Example response

 {
   "elements": [
     {
       "key": "P381-C1",
       "name": "Single",
       "properties": {
         
       },
       "children": [
         "P381-C1-F0",
         "P381-C1-F1",
         "P381-C1-F7"
       ],
       "displayName": "Single Items",
       "contentStyle": "container",
       "type": "container",
       "styles": [
         
       ]
     }
   ],
   "language": {
     "patterns": {
       "datetime": "yyyy-mm-dd hh:mm:ss",
       "date": "yyyy-mm-dd"
     },
     "languageCode": "en-GB"
   }
 }


Parameters

URL SegmentExpected TypeDescription
sessionIdstringThe id of the session.


Response body

Contains a description of the current page model and language settings. For more information about the page elements see REST Page Models V1.


{
	language {
    	languageCode: string,                  // Current language of the session
	    patterns: { [string]: string },        // Formatter patterns for dates
	},                                         // Language information of the session
	elements [{
    	type: string,
		key: string,
		name: string,
		styles: string[],
		properties: { [string]: string },
	}]                                         // All elements of the currently active Blueriq page. Further explained under 'REST Page Models'
}




Send user event

POST /api/v2/session/{sessionId}/event


Description

Handles a page event and returns the events that occurred in any of the sessions in heirarchy.

Headers

NameValue
Content-Typeapplication/json


Parameters

URL SegmentExpected TypeDescription
sessionIdstringThe session id.





Request body

At least the element that triggered the event and all editable fields on the page must be included in the request.

{
	elementKey: string,               // Key of the element the event originates from
	fields: [{
	    key: string,                  // Key of the field
    	values: string[],             // Values of the field, an array even if the field is not multivalued
	}],                               // Data of all fields on the page
	parameters: { [string]: string }  // Additional parameters that may be passed to the backend
}
Example request
{
	"elementKey": "P960-C2-B1",
	"fields": [
		{
       		"key": "P960-C1-F0",
			"values": [
				"testValue"
			]
		},   
		{
			"key": "P960-C1-F6",
			"values": [  
				"testValue2"      
			]
		}
	]
}


Response body

Returns an event response, for more info about an event response see: REST Events V1.

 

{
    events: { EventResponse }[]
}
Example response
{
   "events": [{
		"sessionId": "45992123-f893-4b22-a6a3-ff648b63267c",
		"changes": {
         "changes": [
           {
             "type": "add",
             "key": "P501-C1-B0",
             "model": {
               "key": "P501-C1-B0",
               "name": "Annuleer",
               "properties": {
                 
               },
               "disabled": false,
               "refresh": false,
               "caption": "Annuleer",
               "type": "button",
               "styles": [
                 
               ]
             }
           },   		 
		},
		"type": "page"
	}]
}




Start flow

POST /api/v2/session/{sessionId}/flow/{flowName}


Description

Starts a flow and returns the events that occurred in any of the sessions in the hierarchy. When a page is currently active, only flows which have already been visited can be started.

Example response

{
	"events": [{
		"sessionId": "7c2868f4-4fe9-48b6-841a-cf3e4831750a",
		"changes": {
			"changes": [{
				"type": "delete",
				"key": "P977-C1",
				"model": null
			}]
		},
		"type": "page"
	}]
}


Parameters

URL SegmentExpected TypeDescription
sessionIdstringThe session id.
flowNamestringThe name of the flow.




Response body

Returns an event response, for more info about an event response see: REST Events V1.


Close session


POST /api/v2/session/{sessionId}/close


Description

Closes a session and all its child session.

Parameters

URL Segment

Expected Type

Description

sessionId

string

The sessionId



Keep alive


POST /api/v2/session/{sessionId}/keepalive


Description

Assures that the session stays alive by refreshing its most recent access date.


Parameters

URL SegmentExpected TypeDescription
sessionIdstringThe session id.

Response

204 No Content

  


Create widget

POST /api/v2/session/{sessionId}/widget/{infoKey}

Description

provides a service that creates a child-session using the provided sessionId as its parent, to be used for widgets.

Parameters

URL SegmentExpected TypeDescription
sessionIdstring

The session id

infoKeystringThe info key of the widget to load, available in properties.info of a page mode of type dashboard_flowwidget

Reponse

The sessionId of the existing or newly created session. 

{"sessionId":"a487f65e-6804-4803-bf4b-c89e45f97e38"}



Handling files

Endpoints that go with AQ_File_Upload/AQ_File_Download containers.

Upload file

POST /api/v2/session/{sessionId}/file/{configurationId}/upload

Parameters

URL SegmentExpected TypeDescription
sessionIdstringThe session id.
configurationIdstringThe configuration id.

Response body

Returns an event response, for more info about an event response see: REST Events V1.


 


Download a file

GET /api/v2/session/{sessionId}/file/{configurationId}/download

Description

Gets the file from the specified connection based on its configuration

Parameters


URL SegmentExpected TypeDescription
sessionIdstring

The session id

configurationId

stringThe property configuration id, available


Query Parameters

Query ParameterExpected TypeDescription
error-redirectstringOptional. Specifies the URL to be redirected to if the file download fails. If not provided, the default JSON error output will be used instead.



Example response

The requested file, transferred using Content-Disposition: attachment.


Check authorization


GET /api/v2/session/{sessionId}/file/{configurationId}/checkauthorization

Description

Check if the user has the authority to download the file.

Parameters


URL SegmentExpected TypeDescription
sessionIdstring

The session id

configurationId
stringThe configuration id




Example response

200 OK, if the current user is authorized to download the file

401 Unauthorized, otherwise



Documents

Use to render a Blueriq document or page. A call to this service returns the binary data of the document or page. 

Render a document 

GET /api/v2/session/{sessionId}/document/{documentName}/{type}

Description

Renders a document and returns its binary value. 

 Parameters


URL SegmentExpected TypeDescription
sessionIdstringThe id of the session.
documentNamestringName of the document.
typestringType of document (e.g. PDF).

Query Parameters

 

Query ParameterExpected TypeDescription
error-redirectstringOptional. Specifies the URL to be redirected to if the document download fails. If not provided, the default JSON error output will be used instead.


Response body

Transfers the binary data of a document using Content-Disposition: attachment

 


Render a page

GET /api/v2/session/{sessionId}/document/page/{pageName}/{type}

Description

Renders a page and returns its binary value.

Parameters


URL SegmentExpected TypeDescription
sessionIdstringThe id of the session.
pageNamestringName of the page.
typestringType of page (e.g. PDF).

Query Parameters

Query ParameterExpected TypeDescription
error-redirectstringOptional. Specifies the URL to be redirected to if the document download fails. If not provided, the default JSON error output will be used instead.



Response body

Transfers the binary data of a page using Content-Disposition: attachment

 


Images

Retrieve an image


GET api/v2/session/{sessionId}/image/{imageName}

Description

Returns the binary data of a named Blueriq image.


Parameters


URL SegmentExpected TypeDescription
sessionIdstringThe id of the session.
imageNamestringThe name of the image.


Response body

Returns the binary data of an image.

 


 

Retrieve a QR Code image

GET api/v2/session/{sessionId}/image/{imageName}/key/{key}

Description

Returns the binary data of a named Blueriq QR Code image.

Parameters


URL SegmentExpected TypeDescription
sessionIdstringThe id of the session.
imageNamestringThe name of the image.
keystringThe element key of the image.



Response body

The binary data of an image.



Offline functionality

Prepare offline task

POST api/v2/session/{sessionId}/offline/prepare/{taskId}

Description

Prepares a task to be executed in offline mode 

Parameters

URL SegmentExpected TypeDescription
sessionIdstringThe session id.
taskIdstringThe id of the task to prepare offline mode for

Response body

A PageModel instance with the page contents started by the task. For more information about the page contents (elements) see: REST Page Models V1.



Inference details

The DMN service is part of the development plugin and can be used to get inference details for attribute instances

Get Decision Tree


GET /api/v2/session/{sessionId}/dmn/{entityName}/{instanceId}/{attributeName}


Description

Gets a decision tree model for the specified attribute instance


Parameters

URL SegmentExpected TypeDescription
sessionIdstring

The session id to create an event response for

entityNamestringEntity name for the attribute for which the decision tree is requested
instanceIdstringInstance id for the attribute for which the decision tree is requested
attributeNamestringName of the attribute for which the decision tree is requested





Example response

A decision tree for DMN starts with a rootNode and it is possible that there are 0 or more usedDecisions. A used decision describes an attribute that is used to derive the parent attribute.

{
  "rootNode": {
    "ruleName": "DMNEntity.DataRuleEndResult",
    "justification": null,
    "usedDecisions": [
      {
        "ruleName": "DataRuleForPage",
        "justification": null,
        "usedDecisions": [],
        "entityName": "DMNEntity",
        "attributeName": "DataRule",
        "attributeValues": [
          "44"
        ],
        "sourceType": "System",
        "defaultRuleType": null,
        "instanceId": "40c05cc5-8ddf-48a3-8d5d-53228ca7305c"
      }
    ],
    "entityName": "DMNEntity",
    "attributeName": "DataRuleEndResult",
    "attributeValues": [
      "1342"
    ],
    "sourceType": "Default",
    "defaultRuleType": "expression",
    "instanceId": "40c05cc5-8ddf-48a3-8d5d-53228ca7305c"
  }
}


Language

Get current languages

GET /api/v2/session/{sessionId}/language

Description

Returns a status code 200 if request was successful and a body containing a JSON Array with the available languages that are available in the current project.

Example response

[
  {
   "code": "nl-NL",
   "name": "Nederlands"
  },
  {
   "code": "en-US",
   "name": "English"
  }
]

Set language

POST /api/v2/session/{sessionId}/language/current?languageCode=nl-NL

Description

Sets the specified language in the languageCode parameter for the currently active project. If the specified language does not exist a Bad Request status code is returned.

Standard response codes

All services return a 200 response code on successful requests and a 500 response code if an error occurs. For more information about errors see REST Errors V2.

2 Comments

  1. for the currently active project?