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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Adobe Workfront

Adobe Workfront Records API

Record Controller

Documentation Provider Profile APIs.io OpenAPI GitHub

Adobe Workfront Records API is one of 9 APIs that Adobe Workfront publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Records. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 22 operations across 10 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{customer-domain}/maestro/api.

22 operations 10 paths 42 schemas 4 DELETE6 GET2 PATCH7 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{customer-domain}.my.workfront.adobe.com/attask/api/v22.0
Resource Areas
1

Paths & Operations 22

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

Records 22

Record Controller

GET
/v1/records/{id}
Get Record
getRecord 3 params → 200
PUT
/v1/records/{id}
Update Record
updateRecord 1 param body → 200
DELETE
/v1/records/{id}
Delete Record by ID
deleteRecord 1 param → 200
POST
/v1/records
Create Record
createRecord body → 200
GET
/v1/records/search
Search Records by field values
searchRecordsGet 9 params → 200
POST
/v1/records/search
Search Records by field values
searchRecordsPost 3 params body → 200
GET
/v2/records/{id}
Get Record
getRecord 1 param → 200401403404500
PUT
/v2/records/{id}
Update Record
updateRecord 1 param body → 200400401403404409422500
DELETE
/v2/records/{id}
Delete Record
deleteRecord 1 param → 204401403404500
PATCH
/v2/records/{id}
Patch Record
patchRecord 1 param body → 200400401403404409422500
PUT
/v2/record-types/{recordTypeId}/records/bulk
Bulk Update Records
bulkUpdateRecords 2 params body → 200207400401403404409500
POST
/v2/record-types/{recordTypeId}/records/bulk
Bulk Create Records
bulkCreateRecords 2 params body → 201207400401403404500
DELETE
/v2/record-types/{recordTypeId}/records/bulk
Bulk Delete Records
bulkDeleteRecords 1 param body → 200207400401403404500
PATCH
/v2/record-types/{recordTypeId}/records/bulk
Bulk Patch Records
bulkPatchRecords 2 params body → 200207400401403404409500
POST
/v2/records/{id}/thumbnail
Upload thumbnail on record
uploadThumbnail 1 param body → 201400401403404413500
DELETE
/v2/records/{id}/thumbnail
Delete thumbnail on record
deleteThumbnail 1 param → 204401403404500
GET
/v2/record-types/{recordTypeId}/records
Get Records by Record Type
getRecordsByRecordType 4 params → 200401403404500
POST
/v2/record-types/{recordTypeId}/records
Create Record
createRecord 1 param body → 201400401403404422500
GET
/v2/record-types/{recordTypeId}/records/search
Search Records (GET)
searchRecordsGet 12 params → 200400401403404500
POST
/v2/record-types/{recordTypeId}/records/search
Search Records (POST)
searchRecordsPost 7 params body → 200400401403404500
POST
/v2/record-types/{recordTypeId}/records/move
Move Records
moveRecords 1 param body → 200207400401403404500
GET
/v2/records/{id}/history
Get Record Field Change History
getHistory 3 params → 200400401403404500

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are RecordDto (12 properties), PageRecordDto (11 properties), RecordDto_2 (10 properties), RecordBaseDto (9 properties). Each schema is shown below with its type and property counts.

RecordSearchDto
object
8 properties
GroupedRecordsDto
object
3 properties
RecordExternalOptions
object
5 properties
RecordDto
object
12 properties
RecordGroupDto
object
3 properties
CoverImage
object
2 properties
RecordSorting
object
2 properties
JsonNode
object
RecordBulkResponseDto
object
Response envelope for V2 bulk record operations.
7 properties
MoveRecordsRequestDto
object
Move request specifying which records to move and where
3 properties 1 required
PageableObject
object
6 properties
RecordBulkRequestErrorDto
object
Request-level error affecting multiple items in a bulk operation.
3 properties
RecordGroupDto_2
object
Group of records with common field values
4 properties
HistoryEntryDto
object
A single record field change event
7 properties
GroupDto
object
Grouping specification
2 properties 1 required
V2ProblemDetail
object
RFC 7807 Problem Details error response for V2 endpoints.
7 properties 5 required
FieldOptionDto
object
Field option for single-select and multi-select fields
4 properties
FilterCondition
string
Supported filter conditions for record search
V2FieldError
object
Field-level error detail used in validation errors and per-item batch failures.
3 properties
CoverImageDto
object
Cover image information for a record
2 properties
FieldNumberOptionsDto
object
Number field options for number, percentage, and currency fields
4 properties
FilterGroupDto
A group of filter conditions combined with a logical operator (AND/OR). Supports recursive nesting for complex filter logic.
2 required
PageRecordDto
object
11 properties
CursorInfo
object
Cursor pagination metadata
2 properties
CursorResponseHistoryEntryDto
object
Cursor-paginated list of history entries
2 properties
CellValueDto
object
A snapshot of a field value at a point in time
2 properties
RecordBulkResultItemDtoObject
object
Result for one input item in a bulk record operation.
5 properties
RecordBaseDto
object
Partial record data to update. Only provided fields will be updated.
9 properties
FieldDateOptionsDto
object
Date field options
2 properties
RecordBulkItemErrorDto
object
Per-item error detail in a bulk record operation response.
3 properties
SortObject
object
3 properties
RecordDto_2
object
Complete record data including all record properties
10 properties
FieldUserOptionsDto
object
User field options
1 property
FieldSnapshotDto
object
Snapshot of field metadata captured at the time of the change
9 properties
UserReferenceDto
object
Reference to a user with identifier and display name
2 properties
FilterConditionDto
A leaf filter condition applied to a single field
2 required
RecordSearchPageDto
object
Paginated search response containing records and groups
2 properties
BulkDeleteRequestDto
object
List of record IDs to delete
1 property 1 required
RecordSearchRequestDto
object
Search criteria including filters, sorting, and grouping
7 properties
FilterOperator
string
Logical operator for combining filter conditions
SortDto
object
Sort specification
2 properties 1 required
FilterNodeDto
A node in the filter tree: either a leaf condition or a nested group

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

workfront-records-api-openapi.yml Raw ↑

Other APIs Adobe Workfront publishes across the network.

Adobe Workfront API
AE Profile APIs.io
Adobe Workfront Event Subscription API
AE Profile APIs.io
Adobe Workfront MCP Server
AE Profile APIs.io
Adobe Workfront Fields API
AE Profile APIs.io
Adobe Workfront Permissions API
AE Profile APIs.io
Adobe Workfront Record Types API
AE Profile APIs.io
Adobe Workfront Views API
AE Profile APIs.io
Adobe Workfront Workspaces API
AE Profile APIs.io
#Records
← Back to A APIs
API Details
ID
workfront:workfront-records-api
Base URL
https://{customer-domain}.my.workfront.adobe.com/attask/api/v22.0
Docs
https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/api-general-information/api-basics
Provider
Adobe Workfront
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=workfront-records-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/workfront-records-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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