How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

CData Job API

The CData Cloud Job API monitors background jobs such as replication, caching, and scheduled operations, exposing job state and history.

CData Job API is one of 12 APIs that CData publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Background Jobs, Monitoring, and Replication. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 38 operations across 38 paths, organized into 9 resource areas, and defines 45 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://cloud.cdata.com/api.

38 operations 38 paths 45 schemas 4 DELETE17 GET15 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://cloud.cdata.com/api
Authentication
HTTP Bearer
Resource Areas
9

Authentication & Security 1

CData Job API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — JWT token authentication. Include the token in the Authorization header as Bearer {token}. See [Authentication](/en/API/Authentication-Embedded) for more infor…

Paths & Operations 38

Across 38 paths, the API surfaces 38 operations — 4 DELETE, 17 GET, 15 POST, 2 PUT. They span 9 resource areas: Log, Account, Connection, Data Explorer, Jobs, Cache, Job, Metadata, Query. Each is listed below with its method, path, parameters, and response codes.

Log 3
POST
/log/query/list
List Query Log
listQueryLog body → 200
GET
/log/query/get/{queryId}
Get Query Log
getQueryLog 1 param → 200
POST
/log/audit/list
List Audit Log
listAuditLog 2 params → 200
Account 5
GET
/poweredby/account/list
List Accounts
listAccounts → 200
GET
/poweredby/account/{accountIdOrExternalId}
Get Sub-Account
getAccount 1 param → 200
POST
/poweredby/account/create
Create Account
createAccount body → 200
PUT
/poweredby/account/update/{subAccountId}
Update Sub-Account
updateAccount 1 param body → 200
DELETE
/poweredby/account/delete/{id}
Delete Sub-Account
deleteAccount 1 param → 200
Connection 6
POST
/poweredby/connection/create
Create Connection
createConnection body → 200
GET
/poweredby/connection/list
List Connections
listConnections 2 params → 200
GET
/poweredby/sources/list
List Data Sources
listDataSources → 200
POST
/poweredby/connection/edit/{connectionId}
Edit Connection
editConnection 1 param body → 200
DELETE
/poweredby/connection/delete/{id}
Delete Connection
deleteConnection 1 param → 200
DELETE
/poweredby/{connectionId}/metadata
Clear Connection Metadata
clearConnectionMetadata 1 param → 200
Data Explorer 1
POST
/poweredby/dataExplorer
Generate Data Explorer URL
generateDataExplorerURL → 200
Jobs 1
POST
/poweredby/jobs
Generate Jobs URL
generateJobsURL → 200
Cache 2
POST
/job/cacheConnection
Update Cache Connection
updateCacheConnection body → 200
POST
/job/cacheConnection/formLink
Generate Cache Connection URL
generateCacheConnectionURL body → 200
Job 7
GET
/job/list
List Jobs
listJobs → 200
GET
/job/{jobId}
Get Job
getJob 1 param → 200
POST
/job/create
Create Job
createJob body → 200
PUT
/job/{jobId}/update
Update Job
updateJob 1 param body → 200
DELETE
/job/{jobId}/delete
Delete Job
deleteJob 1 param → 200
POST
/job/{jobId}/run
Run Job
runJob 1 param → 200
POST
/job/{jobId}/stop
Stop Job
stopJob 1 param → 200
Metadata 10
GET
/catalogs
List Catalogs
→ 200
GET
/schemas
List Schemas
2 params → 200
GET
/tables
List Tables
4 params → 200
GET
/columns
List Columns
4 params → 200
GET
/primaryKeys
List Primary Keys
3 params → 200
GET
/importedKeys
List Imported Keys
3 params → 200
GET
/exportedKeys
List Exported Keys
3 params → 200
GET
/indexes
List Indexes
5 params → 200
GET
/procedures
List Procedures
3 params → 200
GET
/procedureParameters
List Procedure Parameters
4 params → 200
Query 3
POST
/query
Execute Query
body → 200
POST
/batch
Execute Batch Query
body → 200
POST
/exec
Execute Procedure
body → 200

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are QueryRecord (13 properties), JobInfo (12 properties), ColumnInfo (12 properties), AuditEvent (11 properties). Each schema is shown below with its type and property counts.

AuditEvent
object
11 properties
AuditEventSearchCriteria
object
2 properties
AuditEventType
integer
BatchRequest
object
5 properties 1 required
BillingStatus
integer
ColumnInfo
object
12 properties
DataType
integer
The parameter's [data type](/en/API/REST-APIdata-types).
Direction
integer
ErrorCode
integer
ErrorDetail
object
2 properties
ExecParameter
object
3 properties
ExecRequest
object
5 properties 1 required
Parameter
object
2 properties
QueryRecord
object
13 properties
QueryRequest
object
6 properties 1 required
QueryResult
object
2 properties
QuerySearchCriteria
object
3 properties
QuerySearchResult
object
1 property
AuditSearchResult
object
1 property
QueryType
integer
| Value | Name | |-------|------| | 0 | Drivers | | 1 | DriverInfo | | 2 | TestConnection | | 3 | GetOAuthAuthorizationUrl | | 4 | GetOAuthAccessToken | | 5 |…
QueryUserInfo
object
5 properties
QueryUserUsageLimits
object
7 properties
ResultSet
object
3 properties
AccountListResult
object
1 property
AccountInfo
object
4 properties 3 required
CreateAccountRequest
object
2 properties
UpdateAccountRequest
object
2 properties
CreateAccountResult
object
3 properties 3 required
CreateConnectionRequest
object
5 properties 1 required
EditConnectionRequest
object
3 properties 1 required
RedirectURLResponse
object
1 property 1 required
ConnectionListItem
object
7 properties 6 required
ConnectionListResult
object
1 property
CacheConnectionRequest
object
1 property 1 required
DataSourceListItem
object
1 property 1 required
DataSourceListResult
object
1 property
JobListResult
object
1 property
JobInfo
object
12 properties 10 required
JobLastRun
object
The last run metrics for the job, including the date and time, duration, status, rows affected, and next run time.
5 properties
JobParams
object
An object containing job parameters. Caching jobs use the fields below; other job types may include additional properties.
8 properties
MergeKey
object
3 properties
CreateJobRequest
object
7 properties 5 required
UpdateJobRequest
object
7 properties 5 required
WorkspaceList
object
2 properties
WorkspaceListItem
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cdata-rest-api-embedded-openapi.yml Raw ↑

Other APIs CData publishes across the network.

CData SQL API
CData Metadata API
CData Log API
CData Connection API
CData Account API
CData Audit API
CData OData API
CData Connect AI MCP Server
CData Connect AI Management API
CData Connect AI Embed MCP Server
CData Connect AI OpenAPI API
Where this information came from

This is an independent, third-party profile of CData Job API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.