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

Adobe Suite Flows API

Flows (or dataflows) represent the transfer of data between source and target. They include details on the transformations applied to your data, the current status of your flow, and details on the most recent run iteration of your flow. Flows also contain metadata, attributes inherited from the base, source, and target connections, as well as a unique flow ID. An instance of a flow is specific to an organization.

Adobe Suite Flows API is one of 482 APIs that Adobe Suite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Flows. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, release notes, and a getting-started guide.

This API exposes 7 operations across 4 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, //{environment}.adobe.io/data/foundation/flowservice.

7 operations 4 paths 20 schemas 1 DELETE2 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://image.adobe.io
Resource Areas
1

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Flows 7

Flows (or dataflows) represent the transfer of data between source and target. They include details on the transformations applied to your data, the current status of your flow, a…

GET
/flows
List flows
listFlows 9 params → 200400401500
POST
/flows
Create a flow
createFlow 4 params body → 201403503
GET
/flows/{FLOW_ID}
Retrieve a flow's details
retrieveFlow 5 params → 200403503
DELETE
/flows/{FLOW_ID}
Delete a flow
deleteByFlow 5 params → 204403503
PATCH
/flows/{FLOW_ID}
Update a flow
patchFlow 6 params body → 200403503
POST
/flows/search
Retrieves list of flows based on a given filtering criteria.
getFlowsByFilters 6 params body → 200401500
POST
/flows/{FLOW_ID}/action
Perform a state transition action given flow object.
postStateTransition 8 params body → 200401500

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are FlowItemDTO (24 properties), CreateFlowRequest (7 properties), FlowFilterRequest (5 properties), ScheduleSpecDTO (4 properties). Each schema is shown below with its type and property counts.

SourceConnectionMetaInfoDTOWrapper
object
3 properties
CreateFlowResponse
object
Location of the newly created flow instance
2 properties
FlowMetaInfoDTO
object
2 properties
ConnectionMetaInfoDTO
object
2 properties
PageLinksResponse
object
1 property
PageLink
object
1 property
FlowItemDTO
object
24 properties
FlowFilterRequest
object
5 properties
PatchInstruction
object
3 properties 3 required
StatusDTO
object
3 properties
StatusErrorDTO
object
3 properties
TransformationSpecDTO
object
2 properties
ScheduleSpecDTO
object
4 properties
FlowListResponse
object
3 properties
TargetConnectionMetaInfoDTOWrapper
object
2 properties
FlowRecordTypeDTO
object
2 properties 2 required
FlowTransformationDTO
object
2 properties 2 required
StateActionDTO
object
3 properties
SpecInfoDTO
object
2 properties 2 required
CreateFlowRequest
object
7 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adobe-suite-flows-api-openapi.yml Raw ↑

Other APIs Adobe Suite publishes across the network.

Adobe Sign API
Adobe Experience Manager API
Adobe Stock API
Adobe Premiere Pro API
Adobe After Effects API
Adobe Target API
Adobe Campaign API
Adobe User Management API
Adobe I/O Events API
Adobe MCP Servers
Adobe Suite Accelerated Queries API
Adobe Suite Access Control Policies API
Where this information came from

This is an independent, third-party profile of Adobe Suite Flows 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.