Overview
API Type Model solely focuses on integrating with external web applications by using REST APIs, allowing seamless data retrieval and management from various web sources.
These models handle data exchange and can be bound various components, enabling efficient data display and interaction across various layouts.
...
Before heading to this section, we need to have some basic understanding about API connections. Let us go through that first.
Pre-requisites
Panel | ||
---|---|---|
| ||
|
This will give an idea about Auth Provider and its configuration, Named Credentials and its configuration as well as Connected App for OAuth settings. Also, if you want to completely go through this you can refer:
Info |
---|
ReferenceReferences:
|
...
Let’s explore the screens that follow, after clicking on Model Creation +
button and Type
as API
.
Details
In this sectiontab, you can see various option while creation model for API types let’s understand each:
...
Details
...
user can specify the REST API Connection for integration and its details, on whose basis model is to be created.
...
Details Config | Description | |
---|---|---|
Type | Specify Allows to specify the type of model, such as:
| |
Connection | Allows you to choose the desired REST connection to fetch records from. | |
Label | Assign a unique name to the model. Info | Note: By default, |
Authentication Type | Allows to specify flexible and secure access to integrated applications through following options:
| |
Connection | Provides the ability to specify the source (i.e., from various web applications to be integrated with REST APIs) to select records . Note: This field is only visible when | |
Label | Allows to specify the name of the model. Note: In case of . | |
Name | Provide Allows to provide unique API name for the model. Info | Note: In case of replicating the connection label in camel case. |
Execute on Load | Enables records to be fetched automatically upon loading the component. |
Request
...
In this tab, user can specify the REST API request that is sent to a server to access resource data.
...
Request Config Group | Config Name | Description | ||
---|---|---|---|---|
Request Parameters | Method | Different Allows to specify HTTP method among different HTTP methods such as GET, POST, PATCH, etc. are used to perform specific operations on resources. You can explore more about methods by clicking here. Note: By default, | ||
URLAdd |
| Headers | It is used to provide additional information about the request, such as the format of the request body, the client's preferred language, authentication credentials, and more
| |
Record Count | Set the record count to either Multirecord or Single, depending on whether you are dealing with multiple records or a single record in the data operation. | |||
Query Params | It is way to pass information to an API in a flexible and simple manner. They are added to the end of the API endpoint URL as a series of key-value pairs. It can be used for filtering, sorting, pagination, formatting or searching the data. | |||
| ||||
Is Array? | Allows to specify whether the data requested from resource should be treated as a single record or multiple records (an array). Notes:
| |||
Type | Allows to specify type of request query argument which will passed to URL, which is basically of two types:
Note: When | |||
Request Body | Generate Schema | It can define fields using JSON formatAllows to define object JSON schema which will be passed on to request.
| ||
Create New Field | It can create fields using the create field Model.Allows users to create fields that can be utilized to build an object JSON schema. Note: When a new field is created, it will be automatically mapped in JSON structure of
|
Response
...
In this tab, user can specify the REST API response that is sent by a server with resource data.
...
Response Config Group | Config Name | Description | ||
---|---|---|---|---|
Response Parameters | Status Code | It indicates whether a specific HTTP request has been successfully completed. | ||
New Button | It allows to specify new Status Code as per one's business need. | |||
Record Count | Set the record count to either Multirecord or Single, depending on whether you are dealing with multiple records or a single record in the data operationIs Array? | Allows to specify whether the data retrieved from resource should be treated as a single record or multiple records (an array). Notes:
| ||
Type | Allows to specify type of response which will retrieved through REST request, which is basically of two types:
Notes:
| |||
Response Body | Generate Schema | It can define fields using JSON formatAllows to define object JSON schema which will be retrieved from response.
| ||
Create New Field | It can create fields using the create field Model.Allows users to create fields that can be utilized to build an object JSON schema that will be received from response. Note: When a new field is created, it will be automatically mapped in JSON structure of
|
Merge Text
Include Page | ||||
---|---|---|---|---|
|
Schema Designer
...
Generate Schema
A "generate
Generate schema
" typically refers to the process of defining or creating a structured format that outlines how data is organized, validated, and transmitted, especially in contexts like APIs or databases.In noKodr, users can define fields using JSON format.
...
Button | Description | ||
---|---|---|---|
Cancel | It allows the user to exit the "Generate Schema" process. If any changes were made in the modal, they will be discarded, and no new schema will be generated. | ||
Recreate | It is used to reset the schema creation form within the modal. All fields will be cleared or set to their default values, enabling the user to begin the process of defining a new schema from scratch. | ||
Merge | It allows the user to merge the newly generated schema with an existing schema. This is useful when the user wants to integrate new schema elements into a pre-existing schema without completely overwriting it.
|
Create New Field
In cases where a user does not have data in XML format but has it in JSON format, the application allows the user to create a schema by adding new fields directly.
This feature is particularly useful for users who need to generate or modify schemas based on their JSON data structure.
...
Field Config | Description | ||
---|---|---|---|
Name | The identifier for the field within the schema. This is the name that will be used to reference the field in the data structure. | ||
Type | It specifies the data type of the field. Note: By default, field type is text.
| ||
Required | It indicates whether the field is mandatory. | ||
Minimum Length | It defines the minimum number of characters or elements that the field must contain. | ||
Maximum Length | It defines the maximum number of characters or elements that the field must contain. | ||
Pattern | It is a regular expression that the field’s value must match. This is typically used for validating formats like email addresses, phone numbers, etc. | ||
Help Text | It provides additional information or guidance on what the field represents and how it should be used. This is often displayed in the UI to assist users. | ||
Default Value | It is a predefined value that the field will take if no other value is provided. This helps in setting initial values. |
...
Field Type | Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Array |
| |||||||||||||
Checkbox |
| |||||||||||||
Date |
| |||||||||||||
Date and Time |
| |||||||||||||
Double |
| |||||||||||||
Integer |
| |||||||||||||
Object |
| |||||||||||||
Text |
|
...
Info |
---|
|