https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/index.html Recent content in 1. API reference overview on JP1 Cloud Service/Operations Integration API Reference Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/api_pre/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/api_pre/index.html API authentication must be performed in advance to execute API requests. (1) Obtaining Ops I tokens A system administrator who has been granted the Pre-Installed role “System Security Administrator” can issue an Ops I token to any user. Ops I tokens do not expire. To obtain an Ops I token, select a user subject to user management in the navigation area of the System Configuration window. After clicking a username in the configuration area, you will see the User Details screen. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/api_usecase/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/api_usecase/index.html This section explains how you can use the Ops I API functions through specific use cases and the corresponding workflow. (1) Changing the agent of an activity corresponding to a specific step in My Workflow The workflow is shown as follows. (Table) Workflow for “Changing the agent of an activity corresponding to a specific step in My Workflow” # Item 1 The API obtains the workflow context ID. 2 The API obtains detailed My Workflow information. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/example/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/example/index.html The following is a detailed description of the API to be used for each use case flow described in “Use cases and workflow for using API functions”. If a request body is required when executing the API, the execution example is formatted to reference a json file. For more information on request bodies, see “Detailed API reference information”. Section structure 1.3.1 Changing the agent of an activity corresponding to a specific step in My Workflow https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/api_list/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/api_list/index.html The following lists describe the API functions available in Ops I. List of Standard API functions (v1) List of Standard API functions (v2) List of Standard API functions (oauth2) List of Custom API functions For details on API functions, see “Detailed API reference information”. (Table) List of Standard API functions (v1) Category Method URL Function users GET /api/v1/users The API obtains a list of users. GET /api/v1/users/{id} The API obtains detailed information about the user with the specified ID. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/mcpserver/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/mcpserver/index.html Ops I provides an MCP server. By connecting to the MCP server, AI agents can perform Ops I operations on behalf of users. AI agents can connect to the MCP server via endpoints (URLs) categorized by purpose and execute the tools associated with those endpoints. Additionally, authentication is required to connect to and use the MCP server. Grant the user the appropriate permissions, issue a Ops I token, and then configure the connection settings. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/errorinfo/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/errorinfo/index.html If an API is executed and results in an error, it returns a response described in “(Table) Status codes returned by the API”. Depending on the error that occurs, it might return a response in response format (e.g., HTML) or with response content not listed here. If a response not listed is returned, review your request, referring to the status code and message content. (Table) Status codes returned by the API