Infraon API Guide
Product DocsSchemaAuthentication
  • Welcome
    • Base URL
    • Authorization
    • Responses
  • Modules
    • Schema
    • Authentication
    • Announcement
    • API Registration
    • Async Tasks
    • BusinessRule
    • BusinessServiceConfiguration
    • Service Catalogue
    • CMDBBlacklistWhitelist
    • CMDBCategory
    • CMDBConsumables
    • Ux
    • CMDBSoftwareLicense
    • Cmdb
    • CMDBRelation
    • CMDBSoftware
    • ContractManagement
    • Department
    • Events
    • Field Configuration
    • IMACD
    • Knowledge Base
    • Leaves
    • Chat
    • Marketplace
    • APIViewSet
    • BeepViewSet
    • SMSviewset
    • Suppressedviewset
    • Organization Location
    • Partner
    • Predicted Events
    • Requester
    • Service Feasibility Requests
    • Role Profile
    • Tag
    • Service_outage
    • Teams
    • Telecom Settings
    • Trap Configurations
    • User Profile
    • Vendor Managemment
    • Association Events
    • Device Template
    • Discovery Configuration
    • Jobs
    • MIB Explorer
    • Seasonal Events
    • IPAM
    • Log Grok Pattern Configuration
    • Log Pipeline Configuration
    • Log Integraion
    • Log Search
    • CLI Download Jobs
    • Configuration Profiles
    • Configuration Policies
    • Configuration Rules
    • Configuration Search
    • Configuration Template
    • Configuration Trigger
    • Jobs Account Audit
    • Manage Vulnerabilities
    • OS Image Download
    • Rule Group
    • Configuration Upload Jobs
    • Work Flow Jobs
    • Change
    • Checklist
    • Incident
    • Problem
    • Release
    • Request Process
    • Task
    • Models
Powered by GitBook
On this page
  1. Modules

Department

PreviousContractManagementNextEvents

Gets a department with the given id

get

This endpoint is used to fetch a department details in the current organization

Authorizations
Path parameters
idstringRequired
Responses
200Success
application/json
get
GET /ux/common/department/department/{id}/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
200Success
{
  "id": "text",
  "name": "text",
  "ci_display_name": "text",
  "ci_descr": "text",
  "dept_id": "text",
  "organization": "text",
  "dept_name": "text",
  "dept_head": "text",
  "prime_user": [],
  "description": "text",
  "created_by": 1,
  "modified_by": 1,
  "creation_time": "2025-06-07T11:51:33.822Z",
  "last_update_time": "2025-06-07T11:51:33.822Z",
  "is_deleted": true,
  "is_demo_data": true
}

Deletes the department with given id

delete

This endpoint is used to delete an existing department for the current organization

Authorizations
Path parameters
idstringRequired
Responses
204
No response body
delete
DELETE /ux/common/department/department/{id}/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
204

No response body

No content

get

API endpoint that allows users to be viewed or edited.

Authorizations
Responses
200Success
application/json
get
GET /ux/common/department/department/options/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
200Success
{
  "id": "text",
  "name": "text",
  "ci_display_name": "text",
  "ci_descr": "text",
  "dept_id": "text",
  "organization": "text",
  "dept_name": "text",
  "dept_head": "text",
  "prime_user": [],
  "description": "text",
  "created_by": 1,
  "modified_by": 1,
  "creation_time": "2025-06-07T11:51:33.822Z",
  "last_update_time": "2025-06-07T11:51:33.822Z",
  "is_deleted": true,
  "is_demo_data": true
}
  • GETGets a list of departments
  • POSTCreates a new department
  • GETGets a department with the given id
  • PUTEdits the department with given id
  • DELETEDeletes the department with given id
  • POST/ux/common/department/department/multidelete/
  • GET/ux/common/department/department/options/

Gets a list of departments

get

This endpoint is used to fetch all the department in the current organization

Authorizations
Query parameters
items_per_pageintegerRequired

Items Per Page

pageintegerRequired

Page Number

reversebooleanOptional

Sorting Order

sortstringOptional

Sorting Key

Responses
200Success
application/json
get
GET /ux/common/department/department/?items_per_page=1&page=1 HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Accept: */*
200Success
[
  {
    "id": "text",
    "name": "text",
    "ci_display_name": "text",
    "ci_descr": "text",
    "dept_id": "text",
    "organization": "text",
    "dept_name": "text",
    "dept_head": "text",
    "prime_user": [],
    "description": "text",
    "created_by": 1,
    "modified_by": 1,
    "creation_time": "2025-06-07T11:51:33.822Z",
    "last_update_time": "2025-06-07T11:51:33.822Z",
    "is_deleted": true,
    "is_demo_data": true
  }
]

Creates a new department

post

This endpoint is used to save a new department for the current organization

Authorizations
Body
Other propertiesanyOptional
Responses
201
No response body
post
POST /ux/common/department/department/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 107

{
  "dept_name": "Finance Department",
  "dept_head": [
    "Ramesh"
  ],
  "description": "Finance",
  "prime_user": [
    "Akshatha"
  ]
}
201

No response body

No content

Edits the department with given id

put

This endpoint is used to edit an existing department for the current organization

Authorizations
Path parameters
idstringRequired
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
namestringRequired
ci_display_namestringRequired
ci_descrstringRequired
dept_idstring · max: 25Required
organizationstring · max: 25Required
dept_namestringOptional
dept_headstringOptional
descriptionstringOptional
created_byintegerOptional
modified_byintegerOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
is_deletedbooleanOptional
is_demo_databooleanOptional
Responses
200Success
application/json
put
PUT /ux/common/department/department/{id}/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 330

{
  "name": "text",
  "ci_display_name": "text",
  "ci_descr": "text",
  "dept_id": "text",
  "organization": "text",
  "dept_name": "text",
  "dept_head": "text",
  "prime_user": [],
  "description": "text",
  "created_by": 1,
  "modified_by": 1,
  "creation_time": "2025-06-07T11:51:33.822Z",
  "last_update_time": "2025-06-07T11:51:33.822Z",
  "is_deleted": true,
  "is_demo_data": true
}
200Success
{
  "id": "text",
  "name": "text",
  "ci_display_name": "text",
  "ci_descr": "text",
  "dept_id": "text",
  "organization": "text",
  "dept_name": "text",
  "dept_head": "text",
  "prime_user": [],
  "description": "text",
  "created_by": 1,
  "modified_by": 1,
  "creation_time": "2025-06-07T11:51:33.822Z",
  "last_update_time": "2025-06-07T11:51:33.822Z",
  "is_deleted": true,
  "is_demo_data": true
}
post

API endpoint that allows users to be viewed or edited.

Authorizations
Body

Serializer for Documents.

Recognized primitve fields:

* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``

Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.

The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).

For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.

Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.

Not well supported or untested:

``FileField``
``ImageField``
``BinaryField``

All other fields are mapped to DocumentField and probably will work wrong.

idstringRead-onlyRequired
namestringRequired
ci_display_namestringRequired
ci_descrstringRequired
dept_idstring · max: 25Required
organizationstring · max: 25Required
dept_namestringOptional
dept_headstringOptional
descriptionstringOptional
created_byintegerOptional
modified_byintegerOptional
creation_timestring · date-timeOptional
last_update_timestring · date-timeOptional
is_deletedbooleanOptional
is_demo_databooleanOptional
Responses
200Success
application/json
post
POST /ux/common/department/department/multidelete/ HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 330

{
  "name": "text",
  "ci_display_name": "text",
  "ci_descr": "text",
  "dept_id": "text",
  "organization": "text",
  "dept_name": "text",
  "dept_head": "text",
  "prime_user": [],
  "description": "text",
  "created_by": 1,
  "modified_by": 1,
  "creation_time": "2025-06-07T11:51:33.822Z",
  "last_update_time": "2025-06-07T11:51:33.822Z",
  "is_deleted": true,
  "is_demo_data": true
}
200Success
{
  "id": "text",
  "name": "text",
  "ci_display_name": "text",
  "ci_descr": "text",
  "dept_id": "text",
  "organization": "text",
  "dept_name": "text",
  "dept_head": "text",
  "prime_user": [],
  "description": "text",
  "created_by": 1,
  "modified_by": 1,
  "creation_time": "2025-06-07T11:51:33.822Z",
  "last_update_time": "2025-06-07T11:51:33.822Z",
  "is_deleted": true,
  "is_demo_data": true
}