![]() Virima API |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Home Commons Constructs Error Codes Tester SERVICES CertificateManagementService AgentResourceMonitor AndroidService AnnouncementService AssetLicenseEntitlementService ConsumableService HardwareAssetService OtherAssetService SoftwareLicenseAssetService StockRoomService StockRoomTypeService UserLicenseEntitlementService AuditRecordService BSMService AvailabilityService CommitmentScheduleService OutagesService OutScopeService BusinessService ServiceCommitment ServiceOffering InScopeService ChangeAttributeService ChangeApprovalServices CherwellIntegrationService CmdbAuditService CMDBCIRelationship CMDBCIVersion CMDBCIService CommentService CommonService ConfigurationServices ContractService CorrelationService CostCenterService CredentialService CustomerService CustomizedColumnsService CyberArkService DemandService DesignationService DevOpsService DiscoveryService DiscoveryMonitoringProfileService DiscoveryClientService DiscoveryPattern DiscoveryScanService DiscoveryScanSplitService Document DuplicatesAndRemediation EMEmailService EventService ExternalAlertService FederationService FileService FinanceService GetRecordService GroupProbeService HelpDeskDashboardService HomePageService ImportCIService ImportITILService IncidentService PriorityService TimescaleService IncidentAttributeService InfoBloxService AssetsAuditService ITILMetricService ITSMChangeService ITSMTicketMgtService IvantiIntegrationService JiraIntegrationService KnowledgeAttributeService KnowledgeManagementService LocationService LoginService MajorSoftwareService MFAService MMCCertificateService OwnerService PreprocessorService PurchaseOrderService PurchaseOrderLineItemService ReceivingSlipService ReceivingSlipsLineService RequestItemService RequestProcurementService TransferOrderService ProbeService ProblemService ProblemAttributeService ProcessNetworkConnections ProcessjobsService ProgramService ProjectService PropertyGroupService ReleaseManagementService ReportDashBoardService ReportingService ReportingClauseService ReportingOrderService ReportPresentationService RequestService RequestAttributeService AssessmentMasterAndQuestionService RiskMangaementService RoleAccessService RuleService RunBookService SAMLService SampleService ScanService SDPService SearchService SensorService ServiceCatalog ServiceNowMappingService ServiceNowRecordService SLAService SoftwareMetricsService ImportSpiceWorkTicketsService SurveyMastersAndQuestions TagService TaskService TaskTimeTrackingService TimeTrackingExportService TimeTrackingService UCFADService UnfuddleService UserDepartmentService UserGroupService UserRoleService UserService VCenterHeirarchyService VCenterTagsService VendorService WorkflowService MenuService |
Virima API Specification - IncidentService ServicesThe requests documented in this section are directed to IncidentService resources, which represent . Contents
saveIncidentCategoryPic GET Interface
Method: GET Relative URL: incident/save-incident-category-pic/image-name/incident-category-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: addIncident POST InterfaceDescription: Service to create incidents. This service is a POST service which takes parameter of type EditValuesArray. It creates an incident and stores audit record for that incident. It also schedules the incident based on the timescale defined by the client and the current state to check for any Service Level Agreement(SLA) violations. Method: POST Relative URL: incident/add Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: editIncident POST InterfaceDescription: Service to edit incidents. This service is a POST service which takes parameter of type EditValuesArray. It updates an incident and stores audit record for that incident. It re-schedules the incident based on the timescale defined by the client, if any state change is done, to check for any Service Level Agreement(SLA) violations. Method: POST Relative URL: incident/edit Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: cloneIncident GET InterfaceDescription: Service to clone an existing incident. This service is a GET service which takes incident id as parameter. It clones the incident with given id by creating a new incident and storing audit record for the cloned incident. It also schedules the cloned incident based on the timescale defined by the client and the current state to check for any Service Level Agreement(SLA) violations. Method: GET Relative URL: incident/clone/incident-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: reOpenIncident POST InterfaceDescription: Service to re-open a closed or resolved incident. An incident can be re-opened if the reporter is not satisfied with the resolution or closure. It also schedules the re-opened incident based on the timescale defined by the client and the current state to check for any Service Level Agreement(SLA) violations. Method: POST Relative URL: incident/re-open/user-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getDefaultTemplate GET InterfaceDescription: Service to get default incident model to create an incident. Method: GET Relative URL: incident/get-default-model Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: getAllProperties POST InterfaceDescription: Service to get all properties of specified module. This is useful if we want to add new property to the specified module, which can be done while adding a model of the specified module. Method: POST Relative URL: incident/get-all-properties/module/model-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: addNewProperty POST InterfaceDescription: Service to add new property to the specified module. This can be done while adding a model. Method: POST Relative URL: incident/add-new-property Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getDefaultProperties GET InterfaceDescription: Service to get default properties of the specified module to create a model. Method: GET Relative URL: incident/get-default-properties/module Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: getIncident GET InterfaceDescription: Service to get the particular incident details. Method: GET Relative URL: incident/get-incident/incident-id/template-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: getIncidentProperties GET InterfaceDescription: Service to get the all incident properties. Method: GET Relative URL: incident/get-incident-properties Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: getLatestIncidents GET InterfaceDescription: Service to get latest incidents created. Method: GET Relative URL: incident/get-latest-incidents/search-key Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: getIncidentSearchRecords POST InterfaceDescription: Service to get latest incidents, problems and known errors created based on the conditions specified. Method: POST Relative URL: incident/get-search-inc-records Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getProcedureFromIncident GET InterfaceDescription: Service to get the procedure to handle incident. Method: GET Relative URL: incident/get-procedure/model-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: createProblem GET InterfaceDescription: Service to create problem from incident page. It creates a problem and stores audit record for that problem. It also schedules the problem based on the timescale defined by the client and the current state to check for any Service Level Agreement(SLA) violations. Method: GET Relative URL: incident/create-problem/incident-id/template-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: createKnowledge GET Interface
Method: GET Relative URL: incident/create-knowledge/id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: addIncidentForServiceCatalogItem POST InterfaceDescription: Service to create requests from service catalog item. It creates a request and stores audit record for that request. It also schedules the request based on the timescale defined by the client and the current state to check for any Service Level Agreement(SLA) violations. Method: POST Relative URL: incident/add-service-catalog-item-incident Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: cancelRequest GET InterfaceDescription: Service to cancel request if it is not fulfilled or closed. Method: GET Relative URL: incident/cancel-request/request-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: changeState POST Interface
Method: POST Relative URL: incident/change-state Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getStates GET InterfaceDescription: Service to get all possible state values Method: GET Relative URL: incident/get-states/model-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: saveCustomStates POST InterfaceDescription: Service to save custom state possible values for incident model. List of states in order and model id need to be passed as input Method: POST Relative URL: incident/save-custom-states Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getTaskStatus GET InterfaceDescription: Service to get the procedure to handle incident. Method: GET Relative URL: incident/get-task-status Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Response Structure:
Example Request: Example Response: incidentBulkUpdates POST Interface
Method: POST Relative URL: incident/incident-bulk-updates Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: editBulkIncidents POST Interface
Method: POST Relative URL: incident/edit-bulk Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getAssigneeAutoFillValues POST Interface
Method: POST Relative URL: incident/get-assignee-autofill-values Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: getExistingProperties POST InterfaceDescription: Service to get all properties of specified module. This is useful if we want to add new property to the specified module, which can be done while adding a model of the specified module. Method: POST Relative URL: incident/get-existing-properties/module/model-id Request Headers: Accept, Authorization Response Headers: Content-Length, Content-Type. Request Structure:
Response Structure:
Example Request: Example Response: |