Explorer

The API Explorer enables users to discover APEX REST APIs, quickly build and execute requests, and view responses directly within the platform.

We can dynamically create any Incidents/Requests/CIs using API.

User Persona: Super Admin

Configure Explorer

To configure the Explorer, perform the following steps:

1. Clickicon from the top panel.

2. Navigate to Platform Studio > API Hub > Explorer.

For more information on the below, navigate to the following links

Note

API can be accessed and configured based on the Roles and Role Templates configured. For example, the create or retrieve access will be subject to the accesses available in the Role Template.

Authentication (POST) - We can ensure secure access to APIs.

Retrieve Records (GET) - We can use the API to fetch a list of records. For example, the incident list.

Create a Record (POST - This API is used to create new records. For example, create a new incident

Update a Record (PUT) - We can use this API to update a record. For example, update a specific incident.

Retrieve a Record (GET) - This API can be used to retrieve a specific record. For example, Incident ID XX

Upload Attachment (PATCH) - This API is used to upload and update an attachment using the PATCH method in various systems.

Get Attachment (GET) - This API is used to retrieve the properties and relationship of an attachment.

Link Records (PATCH) - This API is used to modify specific fields without altering the rest of the resource.

Authentication (POST)

This method ensures secure access to APIs for users other than the logged in user. It can be configured within the explorer's interface. This facility allows the restricted use of API explorer based on user persona and credentials.

The following image displays the configuration screen for Authentication. For more information on the configuration, refer to the table below.

Figure: Authentication

Field	Description
Authentication (POST)
Url	The URL to authenticate is prefilled in the field. The URL can be copied using the copy icon .
Request Body
User Name	Provide the username for authentication.
Password	Specify the password for authentication.
Box	The payload for authentication is detailed. Use the copy icon to copy the request.
Request Headers
Request Format	The request format of the REST API is provided.
Response Format	The response format of the REST API is provided.

Click Send and the following are the details displayed. For more information, refer to the table below.

Figure: API Response

Click Use Token button to use the token for Authentication across APIs.

The following section provide details on the API configuration. For more information refer to each of the sections below.

Note

The general section configuration is common to all API.

/Platform/User/Authenticate

{
    "username": "abc@summitaicoe.co",
    "password": "**********",
    "authenticationType": "passwordlogin"
}

{
    "id": 213,
    "title": null,
    "firstName": "System",
    "lastName": "Administrator",
    "email": "abc@summitaicoe.co",
    "created": "0001-01-01T00:00:00",
    "updated": null,
    "isVerified": false,
    "jwtToken": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJJZCI6IjIxMyIsIlVuaXF1ZV9JZCI6IjAyNWQxMmY2LTQzZjktNDllNi1hNzc2LTRhMDQxNjY1MDJiNiIsIkZpcnN0TmFtZSI6IlN5c3RlbSIsIkxhc3ROYW1lIjoiQWRtaW5pc3RyYXRvciIsIkVtYWlsIjoic3lzYWRtaW5Ac3VtbWl0YWljb2UuY28iLCJVc2VybmFtZSI6IlN5c3RlbSAgQWRtaW5pc3RyYXRvciIsIkltcGVyc29uYXRlSWQiOiIiLCJJc1N3aXRjaE9yRGVsZWdhdGUiOiIiLCJVc2VyQWdlbnQiOiJ7XCJfZFwiOlwiTW96aWxsYS81LjAgKFdpbmRvd3MgTlQgMTAuMDsgV2luNjQ7IHg2NCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzEzMS4wLjAuMCBTYWZhcmkvNTM3LjM2IEVkZy8xMzEuMC4wLjBcIixcIl9yXCI6XCJodHRwczovL3FhYXBleHYxMDJidWlsZDIuc3ltcGhvbnlzdW1taXQuY29tL1wifSIsIm5iZiI6MTczNTUzODM3MiwiZXhwIjoxNzM1NTQxOTcyLCJpYXQiOjE3MzU1MzgzNzJ9.YoFHbj2EDZLJEBHy55QsToHjkzBm5Ul8IJZRps_d6gsSDPxEkPt77VQ2BRyxzhQcbfTE_y8qGQsoZE99rSCCnGZZB0We0_FO8qE8_UeSw8O0xK8L3ME4kIDUjO38Cu4CIlVE3ETuqvNpkVTPkeg9bNaLAv27EoCWqSaWfE4oelPYhQZrswQgC2t0i7tCjpJzJjIarijZwzDRdEmAMgZUjbSJETAL99_LC8EYuaEFZGJFsUPICYcvjaS2IiIw2_ALgC3xwlXDxD9d1JsVP-5e7eV2lfWe-SfUcre7yAsPGswYltZK-PTS8F8mEuyHudD2FChUTQhnzrnZ7TGKmgbgtg",
    "unique_Id": "025d12f6-43f9-49e6-a776-4a04166502b6",
    "message": "Success",
    "userAccount": null,
    "twoFactorEnabled": false,
    "provider": null,
    "isAuthenticated": true,
    "phoneNumber": "1234567890",
    "authenticatorKey": null,
    "authenticatorUri": null,
    "isAuthenticatorKeyPresent": false,
    "domainUniqueId": "b61687df-5b4d-4447-bf30-89d59d59c654",
    "subDomainUniqueId": "c542ea45-a701-47fa-a387-7a3afa92f33b",
    "userPrefernce": [
        {
            "UserPrefernce": "{\"theme\":{\"id\":7,\"unique_Id\":\"38c35750-647c-4548-9438-9922f14e270e\",\"domain_unique_id\":null,\"subdomain_unique_id\":null,\"theme_designer_name\":\"Blue Theme - Default Theme\",\"description\":null,\"theme_designer_json\":null,\"is_exclude\":false,\"publish_by\":null,\"logoFile\":null,\"logoFileType\":null,\"logoFileName\":null,\"favIconFile\":null,\"favIconFileType\":null,\"favIconFileName\":null,\"compressLogoFile\":null,\"compressFaviconFile\":null,\"compressFooterLogoFile\":null,\"footerLogoFile\":null,\"footerLogoFileType\":null,\"footerLogoFileName\":null,\"created_by\":null,\"created_on\":null,\"updated_by\":null,\"updated_on\":null,\"is_active\":true,\"is_default\":true,\"status\":null,\"publish_json\":null,\"publish\":\"{\\u0022Status\\u0022:\\u0022ED04D26A-B282-4BA4-B418-028327B74660\\u0022,\\u0022Publish_by\\u0022:\\u0022global\\u0022,\\u0022Exclude_subdomain\\u0022:false,\\u0022Excluded_domain_list\\u0022:[],\\u0022Excluded_subdomain_list\\u0022:[],\\u0022Published_domain_list\\u0022:[\\u0022b61687df-5b4d-4447-bf30-89d59d59c654\\u0022],\\u0022Published_subdomain_list\\u0022:[]}\",\"is_systemtheme\":false,\"is_GlobalTheme\":false,\"glob_Theme_accessible\":false,\"saved_stepper\":0},\"language_name\":\"en_us\",\"timezone\":\"Asia/Kolkata\",\"custom_data_format\":\"mm-dd-y hh:mm:ss\",\"date_format\":\"mm-dd-y\",\"time_format\":\"hh:mm:ss\"}"
        }
    ],
    "userRolesResponse": null,
    "loginUniqueID": "8337d7ef-c2f8-4afe-9518-1e68e2f04f07",
    "errorMessage": null,
    "impersonateId": "",
    "isDelegated": false,
    "deviceType": "web",
    "securityToken": "vault:v1:hCWj9O5Jct4K1RrUnLVCDQ54pXAbWXb8hGF15a4CbWQYQWSavDONuoYdtafG+ivo3uu43ThhFUvbzp3GDiAuljTYgCGnzFuCclOci8EgBo4s1eUC07+t"
}

Retrieve Records (GET)

This method is most common API function used to retrieve data from a server. It is a read-only option and does not modify the state of information on the server.

The following image displays the configuration screen for Retrieve Records. For more information on the configuration refer to the table below.

Field	Description
Authentication	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application *	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example: Incident, Service Request
Tenant*	Select the appropriate Tenant from which the records are to be retrieved.
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Retrieve Records (GET)	The table details will auto-populate based on the form name selected. Note The URL to GET records will be based on the form name selected and will be auto populated.
Table	The associated table selected in the Form name Note When the Form Type is selected as Designer, all the relevant Admin Forms are displayed.
URL	The URL will auto-populate
Query Parameters
Default Filter	The Tenant selected in General details will be populated in this field. It can be altered based on requirement.
Add Filters	An additional filters can be applied here. Click Add Filter and the following screen is displayed. Here we can set the conditions based on which the Filters will apply. Fields - Choose the specific fields for the request body Value - Choose the Value from the drop-down menu. Expose Display Name - Enable/Disable the option to expose the display name. Enabling the Expose Display Name will display the name as shown in the image below. Disabling the Expose Display Name will display the name with the ID as shown below. Only two attributes can be grouped as part of the AND/OR functionality.
Limit	The number of items displayed on the list. The minimum is set as 10 by default and maximum is 1000.
Page Number	We can limit the page numbers or set it as per requirement.
Response Fields	We can select the response fields based on the filter option. Click the Edit icon and the following page is displayed. Select the column to move the available fields to the selected fields. Use the single arrows to move the fields individually forward and backward . Use the double arrows to move the columns together forward or backward
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.
Authorization	Specifies the authorization and send the request as the current user.

An asterisk(*) represents a mandatory field.

Click Send to update the API. The following response is generated.

Figure: Sample Request Body and Response

The following metadata is available at the end of the response body. For more information on the data, refer to the table below.

Field	Description
HTTP Method/URI	The URI of the request body is displayed.
Headers
Accept	The format in which the request is being sent.
Status Codes	The standard HTTP status codes are displayed to indicate whether the API request has been executed successfully or not. The following are the standard response codes: Successful Responses (200-299) Client Errors (400-499) Server Errors (500 - 599)
Execution Time	The amount of time required for the API request to be processed is called execution time. Execution time logs can help identify performance bottlenecks, optimize code and meet API performance standards.
Current Page	Displays the page number of the listed data.
Page Limit	Displays the number of records being displayed per page.
Is Last	The query returns true or false based on whether the displayed page is the last page.
Total Pages	Displays a record of the total pages with records queried by the API.
Has Previous	Displays false if there are no previous pages to the displayed record. If there are previous pages to display, it shows true.
Has Next	Displays false if there are no further pages to the displayed record. If there are further pages to display, it shows true.
Total Records	Displays the total records returned for the API.
Previous page URL	Displays the previous page URL.
Next page URL	Displays the next page URL.

https://abc.novatech.com/explorer/api/Form/906F1F8E-01C5-4BF6-BDF4-E3E890626763

https://abc.novatech.com/explorer/api/Form/906F1F8E-01C5-4BF6-BDF4-E3E890626763?ResFields=All&ReqFilters=d_tenantOPT_EQ(Information%20Technology)&PageLimit=3&PageNumber=1

{
    "message": "Record(s) found.",
    "data": [
        {
            "created_on": "2024-12-31T03:43:59.603",
            "updated_on": "2024-12-31T11:24:32.14",
            "id": 648,
            "auto_id": "INC00649",
            "d_requestor": "System  Administrator",
            "d_requestor_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "created_by": "System  Administrator",
            "created_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "d_description": "How to troubleshoot Browser Issues?",
            "d_allocated_asset": null,
            "d_allocated_asset_key": null,
            "d_tenant": "Information Technology",
            "d_tenant_key": "0c80b689-8884-4294-939e-1b4ab13aed65",
            "updated_by": "API Key",
            "updated_by_key": "c6ad2f67-d4d2-4459-9c38-9e5f468f16a9"
        },
        {
            "created_on": "2024-12-20T03:34:44.993",
            "updated_on": "2024-12-31T11:24:31.267",
            "id": 642,
            "auto_id": "INC00643",
            "d_requestor": "System  Administrator",
            "d_requestor_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "created_by": "System  Administrator",
            "created_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "d_description": "How to troubleshoot Browser Issues?",
            "d_allocated_asset": null,
            "d_allocated_asset_key": null,
            "d_tenant": "Information Technology",
            "d_tenant_key": "0c80b689-8884-4294-939e-1b4ab13aed65",
            "updated_by": "API Key",
            "updated_by_key": "c6ad2f67-d4d2-4459-9c38-9e5f468f16a9"
        },
        {
            "created_on": "2024-12-20T03:24:34.467",
            "updated_on": "2024-12-31T11:24:30.377",
            "id": 641,
            "auto_id": "INC00642",
            "d_requestor": "System  Administrator",
            "d_requestor_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "created_by": "System  Administrator",
            "created_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "d_description": "How to troubleshoot Browser Issues?",
            "d_allocated_asset": null,
            "d_allocated_asset_key": null,
            "d_tenant": "Information Technology",
            "d_tenant_key": "0c80b689-8884-4294-939e-1b4ab13aed65",
            "updated_by": "API Key",
            "updated_by_key": "c6ad2f67-d4d2-4459-9c38-9e5f468f16a9"
        }
    ],
    "executionTime": 0.1538716,
    "metadata": {
        "currentPage": 1,
        "pageLimit": 3,
        "isLast": false,
        "totalPages": 7,
        "hasPrevious": false,
        "hasNext": true,
        "totalRecords": 19,
        "previousPageURL": "",
        "nextPageURL": "https://qaapexprelude.symphonysummit.com/explorer/api/Form/906F1F8E-01C5-4BF6-BDF4-E3E890626763?ResFields=All&ReqFilters=d_tenantOPT_EQ(Information Technology)&PageLimit=3&PageNumber=2"
    }
}

Create a Record (POST)

The POST method in API is one of the HTTP methods used to send data to a server to create or update a resource. It is commonly used REST APIs where the server needs to accept and process data enclosed in the body of the request.

The following image displays the configuration screen for Create a Record. For more information on the configuration refer to the table below.

Field	Description
Authentication	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application*	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example: Incident, Service Request
Tenant*	Select the appropriate Tenant from which the records are to be retrieved.
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Create a Record (POST)
Table*	The associated table selected in the Form name is selected.
URL	The URL will auto-populate based on the table selected in Form Name. Note The URL to POST records will be based on the form name selected and will be auto-populated.
Request Body	The Request body is displayed when we Add a Field with the specific values. For more information refer to Add a Field.
Add Field	Expose Display Name - Enable/Disable the option to expose the display name. Note Enabling the Expose Display Name will display the name as shown in the image below. Disabling the Expose Display Name will display the name with the ID as shown below. Fields - Choose the specific fields for the request body Value - Choose the Value from the drop-down menu.
Query Parameters
Response Fields	Choose the Value from the table selected for available fields. Click the Edit icon and the following page is displayed. Select the column to move the available fields to the selected fields. Use the single arrows to move the fields individually forward and backward . Use the double arrows to move the columns together forward or backward .
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.
Authorization	Specifies the authorization and send the request as the current user.

An asterisk(*) represents a mandatory field.

Click Send to update the API

https://abc.novatech.com/explorer/api/Form/906F1F8E-01C5-4BF6-BDF4-E3E890626763

{
    "data": {
        "d_description": "sample records, test records",
        "d_tenant": "Information Technology",
        "d_requestor": "Admin"
    }
}

{
    "message": "Record created successfully.",
    "data": [
        {
            "created_on": "2025-01-02T04:54:50.263",
            "updated_on": null,
            "id": 650,
            "auto_id": "INC00651",
            "d_requestor": "Admin",
            "d_requestor_key": "1c4ab999-fb0e-4a8d-b929-c59e64d6e0e0",
            "created_by": "System  Administrator",
            "created_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "d_description": "sample records, test records",
            "d_allocated_asset": null,
            "d_allocated_asset_key": null,
            "d_tenant": "Information Technology",
            "d_tenant_key": "0c80b689-8884-4294-939e-1b4ab13aed65",
            "updated_by": null,
            "updated_by_key": null
        }
    ],
    "executionTime": 0.6031261
}

Update a Record (PUT)

One of the HTTP methods used in RESTful APIs is the PUT method. It is mostly utilized for developing new resources or updating ones that don't currently exist.

The following image displays the configuration screen for Update a Record. For more information on the configuration refer to the table below.

Field	Description
Authentication*	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application*	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example: Incident, Service Request
Tenant	Select the appropriate Tenant from which the records are to be retrieved.
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Update a Record (PUT)
Table*	The associated table selected in the Form name is selected.
URL	The URL will auto-populate based on the table selected in Form Name. Note The URL to PUT records will be based on the form name selected and will be auto-populated.
Request Body	The Request body is displayed when we Add a Field with the specific values. For more information refer to Add a Field.
Add Field	Expose Display Name - Enable/Disable the option to expose the display name. Note Enabling the Expose Display Name will display the name as shown in the image below. Disabling the Expose Display Name will display the name with the ID as shown below. Fields - Choose the specific fields for the request body Value - Choose the Value from the drop-down menu.
Query Parameters
Response Fields	Choose the Value from the table selected for available fields. Click the Edit icon and the following page is displayed. Select the column to move the available fields to the selected fields. Use the single arrows to move the fields individually forward and backward . Use the double arrows to move the columns together forward or backward
Auto Id *	Enter the ID for updating the records. Note The ID depends on the selected form and will change for each module.
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.
Authorization	Specifies the authorization and send the request as the current user.

An asterisk(*) represents a mandatory field.

Click Send to update the API.

https://abc.novatech.com/explorer/api/Form/755f38fc-1bf7-452d-a209-dee5534dfdd6/INC00650

{
    "data": {
        "d_category": [
            "Applications"
        ],
        "d_classifications": [
            "Software"
        ],
        "d_symptom": "Software corrupted "
    }
}

{
    "message": "Record updated successfully.",
    "data": [
        {
            "created_on": "2025-01-02T04:10:38.847",
            "updated_on": "2025-01-02T04:59:18.78",
            "d_category": "Applications",
            "d_category_key": "204e8cdf-db5f-6a14-8186-3b2a2865e0b9",
            "d_classifications": "Software",
            "d_classifications_key": "84eb9a51-53ef-b1b8-1947-b9bf15287cd7",
            "d_closure_category": null,
            "d_closure_category_key": null,
            "d_start_date": null,
            "d_resolution_deadline": null,
            "d_end_date": null,
            "id": 649,
            "auto_id": "INC00650",
            "d_status": "New",
            "d_requestor": "Admin",
            "d_requestor_key": "1c4ab999-fb0e-4a8d-b929-c59e64d6e0e0",
            "d_approvaltimeline_1": null,
            "created_by": "System  Administrator",
            "created_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "d_symptom": "Software corrupted ",
            "d_description": "Sample test tickets, sample records ",
            "updated_by": "System  Administrator",
            "updated_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
            "d_tenant": "Information Technology",
            "d_tenant_key": "0c80b689-8884-4294-939e-1b4ab13aed65",
            "d_medium": "Web",
            "d_tags_1": null,
            "d_tags_1_key": null,
            "d_closure_code": null,
            "d_closure_code_key": null,
            "d_source": "User",
            "d_customer": null,
            "d_customer_key": null,
            "d_cancellation_remarks": null,
            "d_major_incident": null,
            "d_internal_flag": null,
            "d_impact": "Low",
            "d_impact_key": "4",
            "d_pending_reason_old": "Incomplete Info – Details Awaited from User",
            "d_pending_reason_old_key": "18",
            "d_priority": "P4",
            "d_priority_key": "4",
            "d_urgency_": "Low",
            "d_urgency__key": "4",
            "d_is_suggestion_applied": null,
            "d_resolution_code": "Resolved – Custom Solution Applied",
            "d_resolution_code_key": "13",
            "d_solution": null,
            "d_i_found_in_a_knowledge_article": null,
            "d_please_link_the_article_that_helped": null,
            "d_please_link_the_article_that_helped_key": null,
            "d_contact_person": null,
            "d_contact_person_key": null,
            "d_backed_up_dfs_namespace_configuration": null,
            "d_checked_windows_updates_and_suggested_any_critic": null,
            "d_are_antivirus_logs_checked___updated_": null,
            "d_incident_id": null,
            "d_message": "sample records, test records",
            "d_notes_for_self": null,
            "d_vendor_name": null,
            "d_vendor_name_key": null,
            "d_location": null,
            "d_location_key": null,
            "d_inc_urgency": "Low",
            "d_inc_urgency_key": "4",
            "d_inc_impact": "Low",
            "d_inc_impact_key": "4",
            "d_inc__priority": "P4",
            "d_inc__priority_key": "4",
            "d_solution_old": null,
            "d_workgroup": "Level 1 Helpdesk",
            "d_workgroup_key": "4e39f8c9-bdd0-4363-a03d-b0a703d78dcb",
            "d_analyst": null,
            "d_analyst_key": null,
            "d_service_window": "24/7",
            "d_service_window_key": "bdc4b84a-6ba0-41ff-b49a-3c3218e58a38",
            "d_response_sla_violation_reason": "Working on other incidents",
            "d_response_sla_violation_reason_key": "3",
            "d_effort_1": null,
            "d_resolution_sla_violation_reason": null,
            "d_resolution_sla_violation_reason_key": null,
            "d_response_sla_violation_remarks": null,
            "d_resolution_sla_violation_remarks": null
        }
    ],
    "executionTime": 0.5029585
}

Retrieve a Record (GET)

The GET method is essential for retrieving records in an API. This method is most common API function used to retrieve data from a server. It is a read-only option and does not modify the state of information on the server.

The following image displays the configuration screen for Retrieve a Record. For more information on the configuration refer to the table below.

Field	Description
Authentication*	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application*	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example, Incident, Service Request
Tenant*	Select the appropriate Tenant from which the records are to be retrieved.
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Retrieve a Record (GET)
Table*	The associated table selected in the Form name is selected.
URL	The URL will auto-populate based on the table selected in Form Name. Note The URL to GET records will be based on the form name selected and will be auto-populated.
Query Parameters
Response Fields	Choose the Value from the table selected for available fields. Click the Edit icon and the following page is displayed. Select the column to move the available fields to the selected fields. Use the single arrows to move the fields individually forward and backward . Use the double arrows to move the columns together forward or backward .
Auto Id*	Enter the ID for retrieving the records. Note The ID depends on the selected form and will change for each module.
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.
Authorization	Specifies the authorization and send the request as the current user.

An asterisk(*) represents a mandatory field.

Click Send to update the API.

https://abc.novatech.com/explorer/api/Form/755f38fc-1bf7-452d-a209-dee5534dfdd6/INC00650

https://abc.novatech.com/explorer/api/Form/755f38fc-1bf7-452d-a209-dee5534dfdd6/INC00650?ResFields=All&childViews=false

{
    "message": "Success",
    "data": {
        "created_on": "2025-01-02T04:10:38.847",
        "updated_on": "2025-01-02T04:59:18.78",
        "d_category": "Applications",
        "d_category_key": "204e8cdf-db5f-6a14-8186-3b2a2865e0b9",
        "d_classifications": "Software",
        "d_classifications_key": "84eb9a51-53ef-b1b8-1947-b9bf15287cd7",
        "d_closure_category": null,
        "d_closure_category_key": null,
        "d_start_date": null,
        "d_resolution_deadline": null,
        "d_end_date": null,
        "id": 649,
        "auto_id": "INC00650",
        "d_status": "New",
        "d_requestor": "Admin",
        "d_requestor_key": "1c4ab999-fb0e-4a8d-b929-c59e64d6e0e0",
        "d_approvaltimeline_1": null,
        "created_by": "System  Administrator",
        "created_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
        "d_symptom": "Software corrupted ",
        "d_description": "Sample test tickets, sample records ",
        "updated_by": "System  Administrator",
        "updated_by_key": "025d12f6-43f9-49e6-a776-4a04166502b6",
        "d_tenant": "Information Technology",
        "d_tenant_key": "0c80b689-8884-4294-939e-1b4ab13aed65",
        "d_medium": "Web",
        "d_tags_1": null,
        "d_tags_1_key": null,
        "d_closure_code": null,
        "d_closure_code_key": null,
        "d_source": "User",
        "d_customer": null,
        "d_customer_key": null,
        "d_cancellation_remarks": null,
        "d_major_incident": null,
        "d_internal_flag": null,
        "d_impact": "Low",
        "d_impact_key": "4",
        "d_pending_reason_old": "Incomplete Info – Details Awaited from User",
        "d_pending_reason_old_key": "18",
        "d_priority": "P4",
        "d_priority_key": "4",
        "d_urgency_": "Low",
        "d_urgency__key": "4",
        "d_is_suggestion_applied": null,
        "d_resolution_code": "Resolved – Custom Solution Applied",
        "d_resolution_code_key": "13",
        "d_solution": null,
        "d_i_found_in_a_knowledge_article": null,
        "d_please_link_the_article_that_helped": null,
        "d_please_link_the_article_that_helped_key": null,
        "d_contact_person": null,
        "d_contact_person_key": null,
        "d_backed_up_dfs_namespace_configuration": null,
        "d_checked_windows_updates_and_suggested_any_critic": null,
        "d_are_antivirus_logs_checked___updated_": null,
        "d_incident_id": null,
        "d_message": "sample records, test records",
        "d_notes_for_self": null,
        "d_vendor_name": null,
        "d_vendor_name_key": null,
        "d_location": null,
        "d_location_key": null,
        "d_inc_urgency": "Low",
        "d_inc_urgency_key": "4",
        "d_inc_impact": "Low",
        "d_inc_impact_key": "4",
        "d_inc__priority": "P4",
        "d_inc__priority_key": "4",
        "d_solution_old": null,
        "d_workgroup": "Level 1 Helpdesk",
        "d_workgroup_key": "4e39f8c9-bdd0-4363-a03d-b0a703d78dcb",
        "d_analyst": null,
        "d_analyst_key": null,
        "d_service_window": "24/7",
        "d_service_window_key": "bdc4b84a-6ba0-41ff-b49a-3c3218e58a38",
        "d_response_sla_violation_reason": "Working on other incidents",
        "d_response_sla_violation_reason_key": "3",
        "d_effort_1": null,
        "d_resolution_sla_violation_reason": null,
        "d_resolution_sla_violation_reason_key": null,
        "d_response_sla_violation_remarks": null,
        "d_resolution_sla_violation_remarks": null,
        "Tags": [
            {
                "tags": []
            }
        ]
    },
    "executionTime": 0.6088779
}

Upload Attachment (PATCH)

The PATCH method is essential for file upload as an attachment. This method involves, setting up the server to handle file uploads, defining the appropriate PATCH route, and ensuring that files are sent properly.

The following image displays the configuration screen for Upload Attachment. For more information on the configuration refer to the table below.

Figure: Upload Attachment

Field	Description
Authentication	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application*	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example: Incident, Service Request
Tenant*	Select the appropriate Tenant from which the records are to be retrieved.
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Upload Attachment (PATCH)
Table*	The associated table selected in the Form name is selected.
URL	The URL will auto-populate based on the table selected in Form Name. Note The URL to PATCH records will be based on the form name selected and will be auto-populated.
Query Parameters
Auto Id (Ticket Id)*	Enter the Record ID for updating the records.
Field Name*	Specify the column name for which the attachment has to be uploaded.
File Name*	Enter the file name for the attachment.
Request Body
Attachment*	Browse and upload the attachment. The uploaded attachment is displayed as shown below. Note The response is in Base 64 format. Note The attachment gets uploaded and displayed in the box below. There is an option to preview and delete the uploaded attachment. There is also an option to copy the contents displayed in the text box.
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.
Authorization	Specifies the authorization and send the request as the current user.

An asterisk(*) represents a mandatory field.

Click Send to update the API.

https://abc.novatech:44323/API/Form/Attachment/755f38fc-1bf7-452d-a209-dee5534dfdd6/INC00648/d_attachment/test1.txt

"dGVzdGluZyB0aWNrZXQuLi4uLi4uLi4uLi4uLi4u"

{
    "message": "Success",
    "data": {
        "fileName": "test1.txt",
        "fileType": "text/plain",
        "fileSize": 30,
        "columnName": "d_attachment",
        "createdBy": "System  Administrator",
        "createdOn": "2025-02-05T19:14:30.3177221Z",
        "content": ""
    },
    "executionTime": 22.2700667
}

Get Attachment (GET)

The GET method is essential for retrieving an attachment in an API. This method is most common API function used to get attachment properties such as ID, name, and content from a server by providing the necessary parameters.

The following image displays the configuration screen for Upload Attachment. For more information on the configuration refer to the table below.

Figure: Get Attachment

Field	Description
Authentication	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application*	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example, Incident, Service Request
Tenant*	Select the appropriate Tenant from which the records are to be retrieved.
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Get Attachment (GET)
Table*	The associated table selected in the Form name is selected.
URL	The URL will auto-populate based on the table selected in Form Name. Note The URL to GET records will be based on the form name selected and will be auto-populated.
Query Parameters
Auto Id (Incident ID)*	Enter the Incident ID for updating the records.
Field Name*	Specify the column name for which the attachment has to be uploaded.
File Name*	Enter the file name for the attachment.
Attachment Type	Choose the attachment type in the response.
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.
Authorization	Specifies the authorization and send the request as the current user.

An asterisk(*) represents a mandatory field.

Click Send to update the API.

https://abc.novatech:44323/API/Form/Attachment/755f38fc-1bf7-452d-a209-dee5534dfdd6/INC00648/d_attachment/test1.txt

{
    "message": "Success",
    "data": {
        "fileName": "test1.txt",
        "fileType": "text/plain",
        "fileSize": 30,
        "columnName": "d_attachment",
        "createdBy": "System  Administrator",
        "createdOn": "2025-02-05T19:14:30.3177221Z",
        "content": ""
    },
    "executionTime": 22.2700667
}

Link Record (PATCH)

In an API, updating or changing relationships between records by linking or unlinking resources without changing the records' actual data is known as the Link Records (PATCH) action. In an API, updating or changing relationships between records by linking or unlinking resources without changing the records' actual data is known as the Link Records (PATCH) action.

The following image displays the configuration screen for Link Record. For more information on the configuration refer to the table below.

Figure: Link Record (PATCH)

Field	Description
Authentication*	The authentication will be based on the following types. Logged in User - Based on the login credentials used. Generated Token - Based on the credentials used in Authentication.
General
Form Type*	Choose the Form Type from the drop-down menu. For example, Transaction Form or Admin Form.
Domain*	Select the appropriate Domain as per requirement.
Sub Domain*	Select the appropriate Sub Domain as per requirement.
Application*	Select the Application from which the records need to be retrieved.
Module*	Select the appropriate Module as per the Application selected. For example: Incident, Service Request
Form Name*	Select the Form Name from which the records are to be retrieved. The forms that are created and accessible for the specific Tenant will be available. Note The forms will load based on the accesses and role template.
Source Id*	Select the source module to link records. For example Incident Id.
Target Module*	To link records, select the target module. The target module can be chosen within the application or from another application.
Link Type*	Choose the option to Link or Delink records. When the Delink option is chosen, the following is displayed. Here the Target Id will appear as a dropdown based on previously configured links.
Target Id*	Select the target id to link records. For example incident to service request.
Relationship Type*	Select the relationship type. For example Parent child or Peer. Note This field is available for only the Link option.
Link Record (PATCH)
URL	The URL will auto-populate based on the table selected in Form Name. Note The URL to PATCH records will be based on the form name selected and will be auto-populated.
Request Body	The Request body is displayed based on the configuration done at the General level. Note The copy icon can be used to copy the contents.
Request Headers
Request Format	Specifies the format for the REST request body.
Response Format	Specifies the format for the REST response body.

An asterisk(*) represents a mandatory field.

Click Send to update the API and the following is the response received.

Request

Figure: Request Body

Response

Figure: Response

https://abc.novatech:44323/API/relationship/LinkRecord

{
    "relationshipType": "Parent-Child",
    "sourceAutoId": "INC00648",
    "sourceModuleViewId": "755f38fc-1bf7-452d-a209-dee5534dfdd6",
    "targetModuleViewId": "755f38fc-1bf7-452d-a209-dee5534dfdd6",
    "targetAutoId": "INC00647"
}

{
    "message": "Success",
    "data": {
        "id": null,
        "name": null,
        "message": "success",
        "displayName": null,
        "actionType": null,
        "autoId": null,
        "entityDetails": null
    },
    "executionTime": 8.8594651
}