Unqork’s Internal API: Read APIs
Overview
Unqork's internal Read API call is one of the available create, read, update, and delete (CRUD CRUD refers to the four critical operations for creating and managing data elements in your applications. It stands for create, read, update, and delete.) operations. Unlike other CRUD operations, the read operation does not modify the data it retrieves. Instead, read operations act like a operating system's copy and paste function, copying data from one location on the internet and pasting it to a different location. In Unqork, read operations are also known as GET The HTTP GET method is used to request data from a server, typically retrieving information without modifying any resources. calls. For example, the following endpoint is a read operation: Get Module Submissions.
In this
Get Module Submissions API
The Get Module SubmissionsAPI APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. is the simplest of Unqork's internal API calls. It retrieves multiple module submissions. In combination with the List Submissions for Dashboard API, you can then populate those submissions in a dashboard.
To learn more about the Get Module Submissions API, view our Get Module Submissions documentation.
Review the Get Module Submissions API Configuration
To help explain how the Get Module Submissions API APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. works, we've configured a module and Plug-In component that uses this API call. The following sections explore the configuration and lets you test the API. We will take a closer look at the List Submissions for Dashboard API later in this article.
Feel free to use the configuration created here for your own builds. But, please do not reconfigure the modules. If you want to use the configuration, make a copy of the module and paste it in your application.
Review the initNewSubmission Initializer Component
First, let's open the preconfigured module and look at the Initializer component configuration.
1. | Open the preconfigured module in the Module Builder by clicking the following link: https://training.unqork.io/#/form/64cbebaf9ee30a59c4322f0d/edit. |
2. | Hover over the initNewSubmission ![]() |
A 4-button toolbar displays above the component on hover-over.
3. | Using the toolbar, click the (Settings) button. |
4. | Review the following settings: |
You can see the Trigger Type is set to New Submission, firing the Initializer on page load. In the Outputs table, the component outputs values from a schema module and stores them in the moduleId Hidden component.
Review the pluginGetSubmissions Plug-In Component
Let's take a closer look at the necessary Plug-In component configuration and settings to make the API work.
1. | Hover over the pluginGetSubmissions Plug-In component. |
A 4-button toolbar displays above the component on hover-over.
2. | Using the toolbar, click the (Settings) button. |
3. | Review the following settings: |
Internal Services
From the Internal Services drop-down, you'll see that the Get Module Submissions API is selected. Once selected, the Data Source URL auto-populates with /fbu/uapi/modules/{moduleId}/submissions. As you can see, the {moduleId} placeholder text in the URL was modified to {{data.moduleId}}. That way, you can retrieve the specific data stored in the moduleId Hidden component.
To learn more about the Get Module Submissions API, click the Learn More button in the Plug-In component's configuration window.
Request Type
The Request Type is also set to GET. The GET The HTTP GET method is used to request data from a server, typically retrieving information without modifying any resources. type is used to retrieve data.
Inputs
Lastly, the Inputs table sorts by the created data field of the submission and specifies a descending sort order based on the date and time created.
To learn more about conditional filtering, see the api-query-params library documentation: github.com/loris/api-query-params.
Test the Get Module Submissions API
Now, let's preview the module and test the configuration.
2. | Right-click anywhere on the page. |
3. | Click Inspect. The Inspect tab of the DevTools Console The DevTools Console helps you securely store, build, test, and deploy your software. opens to the right of the page. |
5. | Click Get Submissions. This button triggers the pluginGetSubmissions Plug-In component. |
Unqork data is managed in a MongoDB database, which is stored in Amazon Web Services (AWS) and Azure. By pulling in these submissions, you’re seeing what’s saved to MongoDB.
6. | In the Name column, you'll see submissions?sortBy=created&sortOrder=-1. You’ll also see the HTTP status in the Status column. If you see a 200 response, the call was successful. |
You will also see additional filters after the word submissions. These are the sortBy and sortOrder filters set up in the pluginGetSubmissions Plug-In component.
7. | If you click on the API APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. call, you’ll see the specific information about that call: |
Inspector Tabs | Description |
---|---|
Headers |
Displays the call's general information. This information includes the request URL A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address., request method, response headers, and request information (if any was sent). Use this tab to double-check the information that you’re sending in your request. |
Payload |
Displays the actual response payload received from the call, formatted using readable JSON JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data.. |
Preview |
Displays the additional information about the call, formatted using readable JSON JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data.. |
Use the Angular Command
You can also view API call data and responses in the Console tab. In a new line of the Console tab, enter the Angular Command The Angular command, or data command, is a tool that displays submission data in a browser's developer console. In Express View, enter the following command in the devtool console: angular.element('.unqorkio-form').scope().submission: angular.element('.unqorkio-form').scope().submission. This command lets you see the module’s data in a neat JSON JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data. format.
2. | Click Inspect. The Inspect panel opens to the right of the page. |
3. | Click the Console tab. |
4. | Click Get Submissions. This button triggers the pluginGetSubmissions Plug-In component. |
5. | Returning to the Console tab, enter the angular.element('.unqorkio-form').scope().submission command. |
You’ll notice a new nested array displays in the DevTools Console. An array is a collection of ordered data sets. Arrays have a numbered index that starts at [0]. Because this is a nested array, you must expand the data sets to view the submission details.
1. | Expand the ![]() |
2. | Expand the ![]() |
3. | Click the Property ID A Property ID is the unique field ID used by Unqork to track and link components in your module. of the API’s Plug-In component. In this example, its pluginGetSubmissions. |
4. | Select a submission. They're numbered starting at [0]. |
5. | Expand the ![]() |
6. | Expand the ![]() |
Resources