Table of Contents


Overview

Cohesity is a data protection and backup platform. It consolidates backup, recovery and long-term retention for virtual machines, databases, NAS shares and physical servers onto a scale-out cluster, replacing separate backup products and their media servers. Protection policies decide what gets backed up, how often and how long copies are kept, and the cluster reports on which jobs succeeded and which objects are protected at all.

The ReadyWorks connector talks to the Cohesity cluster’s v1 public REST API. It posts a username, password and authentication domain to the access tokens endpoint, reads the bearer token from the accessToken node in the response, and sends that token on every subsequent call. Data lands in whichever staging table each job names in the estate.

Backup coverage is one of the harder things to answer across an estate, and it is exactly the kind of question a migration or decommission wave has to answer. Pulled into the fabric and reconciled against the server and application records already there, Cohesity data shows which machines are protected, which are not, and which have a policy that no longer matches what the workload has become. That turns an assumption into a gate you can enforce before a wave moves.

The connector is declared bidirectional and both job forms are fully exposed, but no Cohesity endpoint ships. Both templates are generic REST skeletons with no endpoint set, so the endpoints have to be configured against your Cohesity API documentation.

NOTE: The authentication method is not marked as the default, even though it is the only one offered. Select it explicitly when creating the connection.

Connector Properties

PropertyValue
IdentifierCOHESITY
NameCohesity
DescriptionConnector for pulling and processing data from Cohesity storage systems
Job TypesBoth Inbound and Outbound
Order310
EnabledYes
LockedYes
Block UpdateNo
Single AuthenticationNo
Windows OnlyNo
Connector Version2026-08-10
HooksNone
Additional Job FieldsNone
Image

Authentication Methods

One authentication method is shipped, matching the Cohesity access tokens flow.

MethodIdentifierBase MethodScriptOrderEnabledConfig Fields
POST username / password / domain – return bearer tokenCOHESITY_452248034dJSON Rest API_cohesityjson_rest_api.php150Yes9

Method 1: POST username / password / domain – return bearer token (COHESITY_452248034d)

Authentication used for Cohesity (Storage Solution)

Posts the username, password and authentication domain as a JSON body to the access tokens endpoint, reads the bearer token from the accessToken node, and attaches it as Authorization: Bearer on the data calls. All five inputs (domain, username, password, token endpoint and token node) are required, and the endpoint and node ship with working defaults for the v1 public API. The Domain value is the Cohesity authentication domain the account belongs to, which is LOCAL for a cluster-local account and the Active Directory domain name for a directory account.

Connection Configuration Fields (9)

OrderLabelTypeRequiredDefaultMax LenTooltip
10API DomaintextYes255Enter API domain of the Connection
30Server Temporary Working PathtextYesstorage/etl5255Enter path where temporary files are stored during data processing (exclude starting and ending backslash)
40UsernametextYes1024Enter username of the Connection
50PasswordpasswordYes64000Enter password of the Connection
60DomainpasswordYes64000Enter domain of the Connection
190Bearer Token End PointtextYes/irisservices/api/v1/public/accessTokens500Enter API end point to request a bearer token
200Bearer Token JSON NodetextYesaccessToken255Enter JSON data node for bearer token
240Single AuthenticationradioYes0Choose if authentication is only to be done once and not on each enumeration or pagination loop
250Additional Job Fieldsfields_listNoEnter list of additional fields to add to staging data for all jobs

Authentication Configuration

Headers sent on the authentication call:

HeaderValueBase64
Content-Type:application/jsonOff

Headers sent on the data calls:

HeaderValueBase64
Content-Type:application/jsonOff
Authorization: Bearer%auth_data%Off

Authentication request body:

KeyValue
username%user_name%
password%user_pass%
domain%auth_value_1%

cURL options:

OptionAuthentication CallData Calls
USERAGENTMozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0Same
SSL_VERIFYHOSTfalseSame
SSL_VERIFYPEERfalseSame
RETURNTRANSFERtrueSame
FOLLOWLOCATIONtrueSame
FAILONERRORtrueSame
POSTtrueSame

NOTE: The Domain field uses a masked password input, so the value is hidden as you type and stored encrypted even though a domain name is not a secret. Type it carefully, because you cannot read it back to check it.

Inbound Job Fields Enabled (44)

The inbound job form carries the full generic REST field set, including pagination, the three enumeration levels and the raw JSON body.

OrderLabelTypeRequiredDefaultTooltip
10Job DescriptiontextYesEnter description of the Job
20Job SchedulelookupYesDailySelect frequency Job should run
30EnabledradioYesYesChoose if Job is enabled
40Use Unparsed DataradioNoNoChoose if you wish to parse the incoming data, or leave it in its raw format
50Log Raw API CallsradioYesNoChoose if raw API calls are logged
70Destination TabletextYesEnter name of the destination table
80Data IdentitytextNoEnter identity of the Job
120Append New Data to Existing TablesradioNoNoChoose if new data will append to the existing destination table, or will create a new destination table
130Fields to IndextextNoEnter fields to index
170Method TypeselectYesGETSelect method type of the Job
190API End PointtextNoEnter API end point of the Job
200API Data Parametersfields_listNoEnter API data parameters of the Job
210Body Data Sending MethodselectYesJSON Encoded DataSelect method for sending the body data
220Raw JSON Body DatatextareaNoEnter the raw JSON body to send. Do not use body selections in the API Parameters if this is used.
230API Return Data NodetextNoEnter API return data node of the Job
250Pagination TypeselectNoNoneSelect request paging type of the Job
270API Pagination NodetextNoEnter API pagination node of the Job
280Pagination Offset StarttextNoEnter request paging offset start of the Job
290Pagination LimittextNoEnter request pagination limit of the Job
300Pagination Termination NodetextNoEnter request paging termination node and value of the Job
310Maximum API CallstextNoEnter maximum number of API calls for the Job to make
320Enumeration 1 TypeselectNoNoneEnter enumeration level 1 type
330Enumeration 1 ETL JoblookupNoSelect ETL job for the enumeration values
340Enumeration 1 Data Typedata_typeNoSelect the data type and fields for enumeration 1 values
350Enumeration 1 Keys End PointtextNoEnter enumeration 1 keys end point of the Job
360Enumeration 1 NodetextNoEnter enumeration 1 node of the Job
370Enumeration 1 Fieldsfields_listNoEnter enumeration 1 fields of the Job
380Enumeration 2 TypeselectNoNoneEnter enumeration level 2 type
390Enumeration 2 ETL JoblookupNoSelect ETL job for the enumeration 2 values
400Enumeration 2 Data Typedata_typeNoSelect the data type and fields for enumeration 2 values
410Enumeration 2 Keys End PointtextNoEnter enumeration 2 keys end point of the Job
420Enumeration 2 NodetextNoEnter enumeration 2 node of the Job
430Enumeration 2 Fieldsfields_listNoEnter enumeration 2 fields of the Job
440Enumeration 3 TypeselectNoNoneEnter enumeration level 3 type
450Enumeration 3 ETL JoblookupNoSelect ETL job for the enumeration 3 values
460Enumeration 3 Data Typedata_typeNoSelect the data type and fields for enumeration 3 values
470Enumeration 3 Keys End PointtextNoEnter enumeration 3 keys end point of the Job
480Enumeration 3 NodetextNoEnter enumeration 3 node of the Job
490Enumeration 3 Fieldsfields_listNoEnter enumeration 3 fields of the Job
500Pause EnumerationtextNoEnter values for pausing enumeration every X calls for Y seconds
510Kill Enumeration on ErrorradioNoNoChoose to stop the enumeration loop on an error or continue processing the loop
520Additional Fieldsfields_listNoEnter list of additional fields to add to staging data
550Retry PausetextNoEnter values for retrying a failed API connection. Retry X times, waiting Y seconds between each try, with an API timeout of Z seconds.
560OrdertextYesEnter order of the Job

NOTE: Several labels and tooltips carry unedited text from the shared templates. Enumaration 1 Node is misspelled and the tooltip on Enumeration 1 Keys End Point refers to enumeration 2. The fields behave as their level numbers say.

Outbound Job Fields Enabled (13)

Thirteen outbound job fields are exposed, covering the endpoint, method type, data sending methods, the outbound and return field lists and a raw JSON template that overrides the generated body.

OrderLabelTypeRequiredDefaultTooltip
10Job DescriptiontextYesEnter description of the Job
30EnabledradioYesYesChoose if Job is enabled
50Log Raw API CallsradioYesNoChoose if raw API calls are logged
170Method TypeselectYesGETSelect method type of the Job
180Data Sending MethodselectYesJSON Encoded DataSelect method for sending the outbound data
190API End PointtextNoEnter API end point of the Job
200API Data Parametersfields_listNoEnter API data parameters of the Job
210Body Data Sending MethodselectYesJSON Encoded DataSelect method for sending the body data
260Return Data Fields Listfields_listYesEnter return data fields of the Job
530Outbound Fields Listfields_listYesEnter outbound fields of the Job
540Ignore Empty Outbound FieldsradioNoYesIgnore, and do not include, any outbound fields that are empty and have no data
550Raw JSON Outbound TemplatetextareaNoEnter the raw JSON outbound template to send. This will replace any automated structures defined in the outbound fields.
560OrdertextYesEnter order of the Job

Inbound Job Templates (1)

One inbound template ships, and it is a blank REST skeleton rather than a Cohesity job.

#Job DescriptionDestination TableAPI End PointEnabledWhat It Pulls
1Rest GET APIapi_dataNot setNoAn empty GET skeleton with no endpoint set, writing to a staging table called api_data. Copy it once per Cohesity collection you want, fill in the API End Point and Destination Table, and set API Return Data Node to the node holding the record array.

Job Template Configuration

Settings

SettingValue
Order10
EnabledNo
Job ScheduleDaily (15 1 * * *)
Destination Tableapi_data
Data Identityapi_data
Allow Empty TableYes
Append Files to Same Destination TableNo
Append New Data to Existing TablesNo
Use Unparsed DataNo
Convert UUID-Keyed Objects to RowsNo
Ignore XML AttributesNo
Log Raw API CallsNo
Method TypeGET
Body Data Sending MethodJSON Encoded Data

NOTE: The template ships disabled. Nothing is retrieved until you configure an endpoint and enable a job.

NOTE: The authentication endpoint default shows the v1 public API prefix, /irisservices/api/v1/public/. Job endpoints on the same API follow that prefix, which is a useful starting point when you build the first job.

Outbound Job Templates (1)

One outbound template ships as a generic shell.

#Job DescriptionMethodAPI End PointEnabledWhat It Does
1Rest POST APIPOSTNot setNoA disabled POST skeleton with no endpoint set. It sends a single Record Key field and expects status, message and data.record_key back. Configure the endpoint and field lists to match the Cohesity call you intend to make.

Job Template Configuration

Settings

SettingValue
Order10
EnabledNo
Log Raw API CallsNo
Method TypePOST
Body Data Sending MethodJSON Encoded Data
Data Sending MethodJSON Encoded Data
Ignore Empty Outbound FieldsYes

Job Parameters and Enumeration

Rest POST API

Outbound fields list:

LabelNameTypeRequiredPattern
Record Keyrecord_keyStringon

Return data fields:

LabelName
Return Statusstatus
Return Messagemessage
Record Keydata.record_key
Last updated on 11/4/2026

Attachments