What are DataDoe Files?

Files are temporary utility files stored in your Organization's DataDoe storage. They let you upload binary content (such as images) and reference it later from Actions, automations, or AI agents through a stable file ID.

Each file belongs to:

• your Organization
• a specific Seller or Vendor connection
• a file group that defines allowed formats, default lifetime, and intended use

Files are not Amazon assets. They are staging objects inside DataDoe that other features (for example, Actions - Manage Images) use at execution time.

How to access Files

In the DataDoe app

Open Files from the side menu. The page lists files for the active group tab and shows status, seller or vendor, size, and expiry.

Via MCP or REST API

Files are available through DataDoe MCP tools and the REST API. This is the recommended path for AI agents and custom integrations.

File groups

A file group defines what a file can be used for. Each group has its own allowed file types, default TTL, and validation rules.

More groups may be added over time. Always pass the correct group when creating a file.

File lifecycle

Every file moves through these statuses:

1. WAITING_FOR_UPLOAD: the file record exists, but the content has not been uploaded yet.
2. UPLOADED: the file content is stored and the file can be referenced by other features.
3. EXPIRED: the TTL has elapsed and the file can no longer be used.

TTL (time to live)

When you create a file, you set how long it remains valid (ttlHours). If omitted, the group default is used (12 hours for LISTING_IMAGES). Allowed range: 1 to 720 hours.

Start any Action that references a file before it expires. Validation rejects expired files.

Scoping

A file is always tied to the Seller or Vendor you pass at creation time (sellerOrVendorId). When you reference a file from an Action, the Action's seller or vendor and connection must match the file.

How to upload a file

The upload flow has two steps:

1. Create a file record and receive an upload target.
2. Upload the binary content.

Using MCP

MCP combines both steps in one call. Pass the file bytes as base64 in contentBase64:

1{
2    "name": "main-product-photo.png",
3    "group": "LISTING_IMAGES",
4    "type": "PNG",
5    "sellerOrVendorId": "YOUR_SELLER_OR_VENDOR_ID",
6    "ttlHours": 12,
7    "contentBase64": "BASE64_ENCODED_IMAGE_BYTES"
8}

Call the files_create tool. On success, the response includes file.id (UUID) and file.status = UPLOADED.

Other MCP tools:

Using the REST API

1. POST /api/v1/files to create the file and receive file and uploadUrl.
2. PUT the image bytes to uploadUrl (presigned upload URL, valid for 30 minutes).
3. GET /api/v1/files/{fileId} to confirm status is UPLOADED.

Other API endpoints:

See the DataDoe API docs (opens in a new tab) for request and response schemas.

Common use cases

Listing image updates

Upload product images to the LISTING_IMAGES group, then reference file UUIDs from an AMAZON_LISTINGS_UPDATE Action.

For the full workflow (slots, replace vs remove, seller vs vendor rules, and examples), see Actions - Manage Images.

Limits and validation

• Maximum file size: 32 MB.
• File type must be allowed for the selected group (for LISTING_IMAGES: PNG, JPG, or TIFF).
• The seller or vendor must exist in your Organization and have a valid connection.
• Only UPLOADED, non-expired files can be referenced by Actions.

Related documentation

• Actions for DataDoe Actions overview.
• Actions - Manage Images for changing listing images with AMAZON_LISTINGS_UPDATE.
• How to connect to the API for REST API setup.
• DataDoe MCP overview for connecting an AI agent to DataDoe.