https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/index.html Recent content in API Reference Home on JP1 Cloud Service/Operations Integration API Reference Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/introduction/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/introduction/index.html This document describes how to use the API functions in JP1 Cloud Service/Operations Integration. ■ Target product JP1 Cloud Service/Operations Integration 02-90 ■ Export precautions When exporting this product, please check the regulations of the Foreign Exchange and Foreign Trade Law and the export control regulations of the U.S. and other foreign countries, and follow the necessary procedures. If you have any questions, please contact our sales representative. ■ Trademarks https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/history/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/history/index.html Changes in (JCSM72-0290-01(E)) JP1 Cloud Service/Operations Integration 02-90 Additions and changes Location By collaborating with your AI agent, tickets can be managed and Ops I definitions can be created and edited efficiently. 1.5 Added the query parameters "filterBy" and "sortBy" to "GET /api/v1/gitops-logs" in Standard API functions (v1). 2.1.1 Changed the upper limit of the "pageSize" query parameter for "GET /api/v1/practice-contexts" in Standard API functions (v1) to 10,000. Changed the upper limit of the "pageSize" query parameter for "GET /api/v1/users" in Standard API functions (v1) to 1,000. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/table-of-contents/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/table-of-contents/index.html 1. API reference overview 1.1 Prerequisite knowledge 1.1 (1) Obtaining Ops I tokens 1.1 (2) Providing and setting Ops I tokens 1.1 (3) Obtaining Ops I access tokens (not recommended) 1.2 Use cases and workflow for using API functions 1.3 Details of API function and execution examples 1.3.1 Changing the agent of an activity corresponding to a specific step in My Workflow 1.3.2 Assigning custom ACLs to roles and removing custom ACLs assigned to roles https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/apireference/index.html In Ops I, you can use API functions to create, obtain, and delete a variety of information. Note When using API functions, specify URL-encoded values in "UTF-8" for the path or query parameters. Chapter structure 1.1 Prerequisite knowledge 1.2 Use cases and workflow for using API functions 1.3 Details of API function and execution examples 1.4 Lists of API functions 1.5 MCP server 1.6 Error information https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/detail/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/detail/index.html This section describes each API function in detail. The API functions are described separately in the following lists. Standard API functions: These are used for user and group management, checking YAML file registration status, etc. You cannot customize these APIs. Custom API functions: These are used for ticket management. When customizing the Ticket screen, the API must also be customized. Note Fields marked "(Reserved Field)" in the request body and response description are reserved fields. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/appendix/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM72029001e/appendix/index.html Descriptions are provided for the following items. Chapter structure 3.1 Version changes