Skip to content

Project Drives

20 endpoints served by the ProjectDriveController controller under the Unified Contact Center family. Every path here is resolved from the controller’s mapping annotations at the commit named in the front matter; the table lists what the backend serves and nothing else.

Access endpoints present: backoffice-ep, etl-ep. The segment decides how the caller authenticates — see Authentication and the Data API reference for the credential each one takes, the request headers, and the response envelope. Paths without an access segment take the signed-in user’s token.

Endpoints

MethodPathHandlerRequest bodySource
GET/core2/tnt/dm/alg/cc/project-drive-linksgetAllProjectDrive—ProjectDriveController.java:163
POST/core2/tnt/dm/alg/cc/project-drive-linkscreateProjectDriveProjectDriveContainerProjectDriveController.java:80
PUT/core2/tnt/dm/alg/cc/project-drive-linksupdateProjectDriveProjectDriveContainerProjectDriveController.java:107
GET/core2/tnt/dm/alg/cc/project-drive-links/backoffice-epgetAllProjectDriveBackoffice—ProjectDriveController.java:375
POST/core2/tnt/dm/alg/cc/project-drive-links/backoffice-epcreateProjectDriveBackofficeEPProjectDriveContainerProjectDriveController.java:235
PUT/core2/tnt/dm/alg/cc/project-drive-links/backoffice-epupdateProjectDriveBackOfficeEpProjectDriveContainerProjectDriveController.java:283
GET/core2/tnt/dm/alg/cc/project-drive-links/backoffice-ep/export/csvgetExportCsvBackoffice—ProjectDriveController.java:495
GET/core2/tnt/dm/alg/cc/project-drive-links/backoffice-ep/querygetProjectDriveByCriteriaBackoffice—ProjectDriveController.java:452
GET/core2/tnt/dm/alg/cc/project-drive-links/backoffice-ep/{guid}getProjectDriveByGuidBackoffice—ProjectDriveController.java:414
DELETE/core2/tnt/dm/alg/cc/project-drive-links/backoffice-ep/{guid}deleteProjectDriveBackoffice—ProjectDriveController.java:329
GET/core2/tnt/dm/alg/cc/project-drive-links/etl-epgetAllProjectDriveEtl—ProjectDriveController.java:384
POST/core2/tnt/dm/alg/cc/project-drive-links/etl-epcreateProjectDriveEtlProjectDriveContainerProjectDriveController.java:246
PUT/core2/tnt/dm/alg/cc/project-drive-links/etl-epupdateProjectDriveEtlEpProjectDriveContainerProjectDriveController.java:293
GET/core2/tnt/dm/alg/cc/project-drive-links/etl-ep/export/csvgetExportCsvEtl—ProjectDriveController.java:504
GET/core2/tnt/dm/alg/cc/project-drive-links/etl-ep/querygetProjectDriveByCriteriaEtl—ProjectDriveController.java:462
GET/core2/tnt/dm/alg/cc/project-drive-links/etl-ep/{guid}getProjectDriveByGuidEtl—ProjectDriveController.java:424
DELETE/core2/tnt/dm/alg/cc/project-drive-links/etl-ep/{guid}deleteProjectDriveEtl—ProjectDriveController.java:339
GET/core2/tnt/dm/alg/cc/project-drive-links/querygetProjectDriveByCriteria—ProjectDriveController.java:207
GET/core2/tnt/dm/alg/cc/project-drive-links/{guid}getProjectDriveByGuid—ProjectDriveController.java:185
DELETE/core2/tnt/dm/alg/cc/project-drive-links/{guid}deleteProjectDrive—ProjectDriveController.java:136

Path variables are shown as {name}. Request body is the declared @RequestBody type; the JSON shape of a container is the record it wraps, and the reliable way to learn it is to read one back with a GET before you POST one (the Data API reference explains the technique). Query endpoints (…/query) take the paging parameters described there.

Related

Last updated on