Migrating from ComplyOne API v6

The intent of this Migration Guide document is to help existing businesses seamlessly port their integrations with Comply One API v6 to Comply One API v7.

Comply One API v7 contain some breaking changes. Existing Add Action and Hazard permission is now split into two separate permissions, Add Action and Add Hazard. Please refer below for updated endpoints and request/response data.

1. Breaking Changes

Please check changes described below and update your integration accordingly.

Endpoint Breaking Change Version Introduced
GET /security/searchpermissions The following parameters are added/removed:
  • 'hasAddActionPermission' is added.
  • 'hasAddHazardPermission' is added
  • 'hasAddActionHazardPermission' is removed. Please use the newly added hasAddActionPermission and hasAddHazardPermission parameters instead.

The following response data are added/removed:
  • 'addAction' property is added.
  • 'addHazard' property is added.
  • 'addActionhazard' property is removed.
 7.0
GET /security/mypermission The following response data are added/removed:
  • 'addAction' property is added.
  • 'addHazard' property is added.
  • 'addActionhazard' property is removed.
 7.0
POST /security/permission The following request data are added/removed:
  • 'addAction' property is added.
  • 'addHazard' property is added.
  • 'addActionhazard' property is removed.
 7.0
POST /security/permission/savetomultiuser The following request data are added/removed:
  • 'addAction' property is added.
  • 'addHazard' property is added.
  • 'addActionhazard' property is removed.
 7.0