API saved queries

This page outlines how to use saved queries with APIs.


Cinchy queries are automatically available as REST APIs to allow for external application integration.

See Saved Queries on how to create a saved query. The URL of the REST API can be found on the Execute Query screen (Image 1).

How to Use the Access Token to Call Cinchy APIs

GET https://<Cinchy Web URL>/API/MyDomain/MyQuery

{% swagger-response status="400" description="The request couldn't be understood, the client is sending a request with incomplete data, poorly constructed data or invalid data.

Optional Validation Logic: To validate query business / control conditional logic failure can be added at the beginning of the API which can intentionally generate a 400 error code (using RAISERROR) and stopping (using RETURN) the API. If there is no RETURN the errors will accumulate and will be provided at the end of running the API.

An attribute (X-Cinchy Error) will be returned in the HTTP header with the custom RAISERROR message indicated (see example below).


--given the following CQL used within a saved query:

IF (ISNULL(@Int,0) = 0)
  RAISERROR('Invalid parameter: @Int cannot be NULL or zero',18,0)
IF (ISNULL(@String,'') = '' OR ISNULL(@String,'') = 'X')
  RAISERROR('Invalid parameter: @String cannot be NULL or empty or X',18,0)

--note "X-Cinchy-Error" in the sample response:

< HTTP/1.1 400 Bad Request
< Cache-Control: private
< Content-Type: text/html; charset=utf-8
< Server: Microsoft-IIS/10.0
< X-AspNetMvc-Version: 5.2
< Access-Control-Allow-Origin: *
< X-Cinchy-Error: Invalid parameter: @Int cannot be NULL or zero
< X-AspNet-Version: 4.0.30319
< X-Powered-By: ASP.NET
< Date: Wed, 1 Aug 2020 17:43:04 GMT
< Content-Length: 4517


The following example shows how to use API Saved Queries (Image 2.)

In the above image, "%40" is the URL encoded version of "@".If you are passing them in as parameters you will need to include the %40 in front of your parameter name.

Use Basic Authentication to Call Cinchy APIs

https://<Cinchy Web URL>/BasicAuthAPI/MyDomain/MyQuery

Anonymous access

The following instructions detail how to allow anonymous access to your saved query API endpoint.

  1. Navigate to the table your query will be referencing. In this example, it's the Accessibility Assessments table (Image 1).

  2. Navigate to Data Controls > Entitlements.

  3. On a new row, add in the Anonymous user and ensure that either "View All Columns" (to expose all the data) or "View Selected Columns" (to select individual columns) is checked off (Image 3).

Clicking on inline images in GitBook will open a larger version.

  1. Design your query (Image 4). For more information on creating new saved queries, click here.

  1. Once you have written your query, navigate to Design Query > Info, on the left navigation bar.

  2. Change your API Result Format to JSON (Image 5).

  1. Navigate to Design Controls from the left navigation bar.

  2. To ensure that anonymous users have the correct permission needed to execute the query that generates the API response, add the "Anonymous" user to the users permission group UI under "Who can execute this query?" (Image 6).

  1. Navigate to "Execute Query" from the left navigation bar.

  2. Copy your REST API endpoint URL (Image 7).

  1. To confirm that anonymous access has been successfully set up, paste the URL into an incognito/private browser (Image 8).

3.1 Troubleshooting

  • 401 errors likely mean you haven't added the Anonymous user to the list of users (not "Groups") that can execute the query.

  • 400 errors likely mean that you haven't added the Anonymous user to the list of users that (not "Groups") that can view column data from the tables that your query uses.

Last updated