Open API on Gateway v3.28.0

What's new

  • User management
    • [Update] POST /api/open/v1/users
      • Supported for creating users with encrypted passwords
    • [Update] PATCH /api/open/v1/users/{id}
      • Supported for changing user password via this API, user password must be encrypted for security reasons
    • [New] POST /api/open/v1/users/delete
      • Deleting the specified users
    • [New] POST /api/open/v1/users/group
      • Assigning the specified users to a single group
  • Computer management
    • [New] GET /api/open/v1/computers/{id}
      • Getting the information for a single computer
    • [New] PATCH /api/open/v1/computers/{id}
      • Managing the information for a single computer
    • [New] POST /api/open/v1/computers/delete
      • Deleting the specified computers
    • [New] POST /api/open/v1/computers/group
      • Assigning the specified computers to a single group

  • Group management
    • [New] POST /api/open/v1/groups
      • Creating a new group
    •  [New] POST /api/open/v1/groups/delete
      • Deleting the specified groups
    • [New] PATCH /api/open/v1/groups/{id}
      • Managing the information for a single group
    • [New] GET /api/open/v1/groups/{id}/managers
      • Getting the group managers for a single group
    • [New] PATCH /api/open/v1/groups/{id}/managers
      • Managing the group managers for a single group
  • Access permission
    • [New] GET /api/open/v1/users/access_permission/result
      • Getting the access permission result for all users
    • [New] GET /api/open/v1/groups/access_permission/result
      • Getting the access permission result for all groups
  • Security management 
    • [New] POST /api/open/v1/dynamic_key
      • Creating a Dynamic Key
    • [New] PUT /api/open/v1/encryption_key
      • Negotiating encryption_key based on POST /api/open/v1/dynamic_key. The encryption_key will be used to encrypt sensitive information
    •  [New] POST /api/open/v1/encryption_key/verify
      • After setting the encryption key, verify that the AES key matches the key in the backend
  • PSA (You need to enable Attened Support in Gateway to use PSA-related API)
    • [New] POST /api/open/v1/psa/support_ticket/external_ids/token
      • Creating a support ticket token based on an external ticket_id
    • [New] PUT /api/open/v1/psa/support_ticket/external_ids/token
      • Managing the specified support token
    • [New] GET /api/open/v1/psa/support_ticket/external_ids/logs
      • Getting the logs for a single support ticket based on the external ticket_id
    • [New] POST /api/open/v1/psa/support_ticket/internal_ids/tickets
      • Creating an internal ticket_id
    • [New] POST /api/open/v1/psa/support_ticket/internal_ids/token
      • Creating a support ticket token based on an internal ticket_id
    • [New] PUT /api/open/v1/psa/support_ticket/internal_ids/token
      • Managing the specified support token
    • [New] GET /api/open/v1/psa/support_ticket/internal_ids/logs
      • Getting the logs for a single support ticket based on the internal ticket_id
    • [New] DELETE /api/open/v1/psa/support_ticket/internal_ids/tickets/{id}
      • Deleting an internal ticket_id

API Documentation

 
0 out of 0 found this helpful