Adobe Suite Flow specs API
Flow specs retain information that define a flow. They include information on how a flow can be scheduled, whether a flow supports options like partial ingestion and error diagnostics, as well as the parameters required for different mappings from source to target. Flow specs also include information on how a flow run can be created and a list of connection spec IDs and target connection IDs that a given flow can support. Flow specs are organization agnostic.
Adobe Suite Flow specs 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 Flow specs. 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 5 operations across 3 paths, and defines 12 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.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 5
Across 3 paths, the API surfaces 5 operations — 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Flow specs retain information that define a flow. They include information on how a flow can be scheduled, whether a flow supports options like partial ingestion and error diagnos…
Schemas 12
The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are UpdateFlowSpecRequest (14 properties), CreateFlowSpecRequest (14 properties), FlowSpecItemDTO (11 properties), FlowSpecFilterRequest (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Adobe Suite 12
Other APIs Adobe Suite publishes across the network.
This is an independent, third-party profile of Adobe Suite Flow specs 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.