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

3-shake Workflows API

The Workflows API from 3-shake — 8 operation(s) for workflows.

3-shake Workflows API is one of 6 APIs that 3-shake publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Workflows. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, and rate-limit docs.

This API exposes 8 operations across 8 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0.

Requests are made against a single base URL, https://cdp-server.reckoner-api.com/api/external/v1.

8 operations 8 paths 32 schemas 6 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.0
Base URL
https://cdp-server.reckoner-api.com/api/external/v1
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

3-shake Workflows API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (Access token) (BearerAccessAuth). It accepts HTTP bearer tokens (Refresh token) (BearerRefreshAuth). By default, every request must be authenticated.

  • BearerAccessAuth — アクセストークン(pat プレフィックス)
  • BearerRefreshAuth — リフレッシュトークン(prt プレフィックス)

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 6 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Workflows 8
POST
/workflows/{workflowId}/run
ワークフロー実行
runWorkflow 1 param body → 200400401402403404429500
GET
/workflows/{workflowId}/jobs/{jobId}
ワークフロージョブ実行結果取得
getWorkflowJob 2 params → 200400401403404429500
GET
/workflows/{workflowId}/jobs
ワークフロージョブ実行結果一覧取得
listWorkflowJobs 5 params → 200400401403404429500
PUT
/workflows/{workflowId}/jobs/{jobId}/cancel
ワークフロージョブキャンセル
cancelWorkflowJobs 2 params → 200400401402403404429500
GET
/workflows/{workflowId}
ワークフロー取得
getWorkflow 1 param → 200400401403404429500
GET
/workflows/projects/{projectId}
ワークフロー一覧取得
listWorkflows 7 params → 200400401403404429500
GET
/workflows/{workflowId}/export
ワークフローエクスポート
exportWorkflow 1 param → 200400401403404429500
GET
/workflows/usages
ワークフロー利用状況取得
listWorkflowUsages 4 params → 200400401403404429500

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are Workflow (10 properties), WorkflowSummary (7 properties), ExportWorkflow (6 properties), ExportTask (5 properties). Each schema is shown below with its type and property counts.

WorkflowUsages
object
2 properties 2 required
WorkflowJobSummary
object
5 properties 3 required
WorkflowJob
object
5 properties 2 required
Workflow
object
10 properties 7 required
JobId
object
1 property 1 required
WorkflowNotifications
object
ワークフローの通知設定
4 properties 4 required
WorkflowSchedule
object
ワークフローのスケジュール実行設定
3 properties 3 required
WorkflowNotificationWebhook
object
ワークフローに設定されているWebhook通知
2 properties 2 required
WorkflowRunParameter
object
1 property
WorkflowNotificationSlack
object
ワークフローに設定されているSlack通知
2 properties 2 required
ExportTask
object
エクスポートしたワークフロー内のタスク
5 properties 5 required
ExportWorkflowParameter
object
ワークフローに設定されているパラメーター変数。エクスポート元の変数がシークレット属性の場合、値をマスクした上で非シークレット属性として扱われる
2 properties 2 required
WorkflowUsageDetail
ExportWorkflow
object
6 properties 5 required
WorkflowNotificationEmail
object
ワークフローに設定されているメール通知
2 properties 2 required
ErrorResponse
object
2 properties 2 required
WorkflowRunParameterItem
object
2 properties 2 required
TaskDependency
object
ワークフロー内のタスクの依存関係
2 properties 2 required
WorkflowJobStatus
string
ワークフロージョブのステータス SUBMITTING - ジョブ送信中 RUNNABLE - 実行前 RUNNING - 実行中 COMPLETED - 正常完了 FAILED - 失敗 CANCELSTARTED - キャンセル処理開始 CANCELED - キャンセル完了 SERVERERROR - サーバーエラー
WorkflowJobError
object
4 properties 4 required
WorkflowSummary
object
7 properties 5 required
WorkflowUsageClassification
WorkflowNotificationMSTeams
object
ワークフローに設定されているMicrosoft Teams通知
3 properties 3 required
WorkflowJobTrigger
string
ワークフロージョブの実行方法 button - ブラウザ画面上の実行ボタンによる実行 scheduled - スケジューリング実行 webhook - Webhook実行 externalapi - Reckoner APIによる実行
WorkflowJobs
object
2 properties 2 required
Label
object
ワークフローに付与されたラベル
3 properties 3 required
Task
object
ワークフロー内のタスク
5 properties 4 required
WorkflowUsageTotal
object
2 properties 1 required
WorkflowUsage
object
3 properties 2 required
WorkflowParameter
object
ワークフローに設定されているパラメーター変数
3 properties 3 required
WorkflowNotificationStatus
string
通知対象となるワークフロージョブ完了ステータス
Workflows
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

3shake-workflows-api-openapi.yml Raw ↑

Other APIs 3-shake publishes across the network.

Securify Scan Public API
3-shake Accounts API
3-shake Auth API
3-shake Integrations API
3-shake Projects API
Where this information came from

This is an independent, third-party profile of 3-shake Workflows 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.