API Changes

API Changes in OvalEdge Release6.0.2

As part of this release, new APIs are introduced along with modifications to existing APIs, which enhance current functionality and improve usability.

New APIs

  1. Business Glossary API
    GET /api/businessglossary/domain/getBusinessTermsDomainWise
    In the Business Glossary APIs, a new GET request (/api/businessglossary/domain/getBusinessTermsDomainWise) is introduced to fetch the details of the terms based on domain types. 
  2. Custom Fields API
    POST /api/addCustomFields
    In the Custom Fields APIs, a new POST (/api/addCustomFields) is introduced to add a custom field for an object by providing the object name and object type.
  3. Security API
    GET /api/fetchUserPrivilegesOnObject
    In the Security APIs, a new GET request (/api/fetchUserPrivilegesOnObject) is introduced to fetch a user's permissions on a particular object.

Modified APIs

The term ‘Connection’, which refers to the connectivity to a source data system for crawling and profiling metadata has been changed to ‘Connector’. This change has been reflected in all the APIs that use connector as a parameter. 

Column API

  1. GET /api/column/getTableColumnsByName
    Change: GET parameter connectionname -> connectorname
  2. POST /api/column
    Change: Request body parameter connectionid -> connectorid
    Change: Request body parameter connection name -> connectorname
  3. POST /api/column/fields/add
    Change: Response body parameter connectionname -> connectorname
  4. POST /api/column/description/add
    Change: Response body parameter connectionname -> connectorname

Custom Fields API

  1. GET /api/getdefinedcustomfields
    Change: GET parameter connection/domainId -> connectorOrDomainId

File API

  1. GET /api/file
    Change: Request Body parameter connectionid -> connectorid
    Change: Request Body parameter connectionname -> connectorname
  2. GET /api/file/catalogandprofilefile
    Change: Request Body parameter connectionid -> connectorid

File Column API

  1. POST /api/filecolumn
    Change: POST parameter connectionid -> connectorid

File Folder API

  1. POST /api/filefolder
    Change: POST parameter connectionid -> connectorid
  2. GET /api/connector/{connectorid}/filefolders
    Change: GET parameter connectionId -> connectorId
  3. GET /api/connector/{connectorid}/filefolder
    Change: API name from /connection/{connectionid}/filefolder to /connector/{connectorid}/filefolder
    Change: GET parameter connectionId -> connectorId

Governance Roles API

  1. POST /api/updategovernanceroles
    Change: Response Body parameter connectionname -> connectorname

Impact Analysis API

  1. POST /api/job/submitcustombatchforimpactanalysis
    Change: Response Body parameter connectionname -> connectorname

Lineage API

  1. POST /api/insertLineage
    Change: Response Body parameter refconnectionid -> refconnectorid
  2. POST /api/insertLineageWithNames
    Change: Response Body parameters refconnectionname -> refconnectorname, sourceconnectioname -> sourceconnectorname, targetconnection -> targetconnectorname
  3. GET /api/lineagegraphwithnames
    Change: GET Paramater connectionname -> connectorname
  4. GET /api/lineageColumnGraphWithNames
    Change: GET Paramater connectionname -> connectorname

Query API

  1. POST /api/query/update
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  2. POST /api/query/getqueryresults
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  3. POST /api/query/add
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid

Report API

  1. POST /api/report
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid

Connector API

  1. GET /api/connectors/all
    Change: The API name connections/all is changed to connectors/all.
  2. POST /api/connector/updatepassword
    Change: The API name /connection/updatepassword is changed to /connector/updatepassword.
    Change: The response body parameter connectionid is changed to connectorid.
  3. POST /api/connector/saveconnector
    Change: The API name /connection/saveconnection is changed to /connector/saveconnector.
    Change: The response body parameter connectionparamlist is changed to connectorparamlist.
  4. POST /api/connector/crawlerandprofilerules
    Change: The API name is changed from /connection/crawlerandprofilerules to /connector/crawlerandprofilerules.
    Change: The response body parameters connectionid and connectionname are changed to connectorid and connectorname, respectively.
  5. GET /api/connector/{connectorid}
    Change: The API name connection/{connectionid} is changed to connector/{connectorid}.
  6. GET /api/connector/getconnectorparam
    Change: The API name connection/getconnectionparam is changed to connector/getconnectorparam.

Report Column API

  1. POST /api/reportcolumn
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid

Report Group API

  1. GET /api/reportgroup
    Change: GET Paramater connectionid -> connectorid
  2. POST /api/reportgroup
    Change: Request body parameters connectionname -> connectorname, connectionid -> connectorid

Schema API

  1. GET /api/schema
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  2. POST /api/schema/description/add
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  3. POST /api/jobs/crawl/schema/new
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  4. POST /api/jobs/crawl/schema/existing
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  5. GET /api/connector/{connectorid}/schemas
    Change: GET Parameter connectionname -> connectorname

Security API

  1. POST /api/security/roles/users/updateuserrolemappings
    Change: Parameter connectionname -> connectorname
  2. PUT /api/security/role/update{roleid}
    Change: Parameter connectionname -> connectorname
  3. POST /api/security/role/add
    Change: Response Body parameter connectionname -> connectorname

Table API

  1. POST /api/table
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  2. POST /api/table/schemacompare
    Change: Response Body parameters connectionname -> connectorname, connectionid -> connectorid
  3. POST /api/table/saveprofileinfo
    Change: Response Body parameters connectionname ->
    connectorname, connectionid -> connectorid
  4. POST /api/table/fields/add
    Change: Request body parameter connectionname -> connectorname
  5. POST /api/table/description/add
    Change: Request body parameter connectionname -> connectorname
  6. POST /api/table/tablewithname
    Change: GET parameter connectionname -> connectorname

Business Glossary API

  1. POST /api/term/addterm
    Change: Request body parameters connectionname -> connectorname, connectionid -> connectorid

Please note that the provided information includes the changes made in the API endpoints, request body parameters, and response body parameters in Release6.0.2. 


Copyright © 2023, OvalEdge LLC, Peachtree Corners, GA USA