Get Connect Jobs Logs
Use this to get all of the logs for a Connect job.
Note: The Responsys Advanced API is generally available for all Responsys customers.
Service URL:
/rest/api/v1.3/connectJobs/{jobId}/jobRuns/{jobRunID}/logs
Required Path Parameters:
-
jobId- Job ID of the existing Connect job that you want to get the logs for. See Trigger a Connect Job for information about how to look up the Job ID in Oracle Responsys. -
jobRunID- Job Run ID of the existing Connect job that you want to get the logs for. Use the Get Connect Jobs Runs endpoint to retrieve a job'sjobRunID.
Request Method:
GET
Request Header:
Authorization=<AUTH_TOKEN>
Content-Type=application/json
Request Body - Required Properties:
Not applicable
Sample Request Body
Not applicable
Sample Response Body - Success
[
{
"logLevel": "<logLevel1>",
"logMessage": "<logMessage1>",
"logTime": <logTime1>
},
{
"logLevel": "<logLevel2>",
"logMessage": "<logMessage2>",
"logTime": <logTime2>
}
]
Sample Response Body - Failure
400 Bad Request
Invalid request parameters. Error when the job ID in the request URL is non-numeric (if, for instance, the job name was provided instead):
{
"type":"",
"title":"Invalid request parameters",
"errorCode":"INVALID_PARAMETER",
"detail":"Job Id should be a numeric value.",
"errorDetails":[]
}
401 Unauthorized
API disabled for user. Error when the user does not have access to advanced APIs:
{
"type": "",
"title": "API disabled for user",
"errorCode": "API_DISABLED_FOR_USER",
"detail": "API is disabled for user",
"errorDetails": []
}
404 Not Found
Running connect job not found. Error when the job ID in the request URL is invalid:
{
"type": "",
"title": "Connect job not found",
"errorCode": "CONNECT_JOB_NOT_FOUND",
"detail": "Connect Job not found for jobId : 1", // value of job ID sent
"errorDetails": []
}