API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
API endpoint that allows users to be viewed or edited.
API endpoint that allows users to be viewed or edited.
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
This endpoint is used to fetch all the Services profiles in the current organization (works based on token used to authorize)
Items Per Page
Page Number
Sorting Order
Sorting Key
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
Adaptation of DRF ModelViewSet
No response body
No content
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
API endpoint that allows users to be viewed or edited.
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
This endpoint is used to fetch all the customer ci configurations in the current organization
Items Per Page
Page Number
Sorting Order
Sorting Key
This endpoint is used to edit an existing ci classification for the current organization
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.
API endpoint that allows users to be viewed or edited.
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.
API endpoint that allows users to be viewed or edited.
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.
API endpoint that allows users to be viewed or edited.
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.
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.
true