AWS Data Exchange

Name: AWS Data Exchange API
Brand: AWS Data Exchange
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataAWS Signature v4 (HMAC)29 EndpointsREST

For Agents

Subscribe to and operate on third-party data sets in AWS - manage data sets, revisions, assets, jobs, and event-driven exports.

Connect the AWS Data Exchange to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Data Exchange, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS Data Exchange API.

Browse and subscribe to entitled data sets in AWS Data Exchange

List, describe, and update data sets, revisions, and individual assets the account is entitled to

Create import jobs that copy assets from S3, signed URLs, or APIs into Data Exchange

Create export jobs that copy revision assets to a subscriber's S3 bucket

GET STARTED

Start building with AWS Data Exchange API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Data Exchange, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Data Exchange, keeping it validated and agent-ready. AWS Data Exchange is a marketplace and management plane for finding, subscribing to, and using third-party data in AWS. The API manages data sets, revisions, assets, and jobs that import data from S3 or APIs and export it to S3 buckets the subscriber controls. Data sets cover financial, healthcare, geospatial, weather, demographic, and many other domains, with contractual access enforced through entitlements.

Use Cases

Patterns agents use AWS Data Exchange API for, with concrete tasks.

★ Daily Export of a Subscribed Data Set

Analytics teams subscribe to third-party data such as financial prices, weather, or demographics and need fresh data delivered to S3 daily. AWS Data Exchange's CreateJob with type EXPORT_REVISIONS_TO_S3 copies a revision to a target bucket, and an event action can trigger this automatically when a new revision is published.

Call CreateJob with Type=EXPORT_REVISIONS_TO_S3, Details specifying DataSetId, RevisionIds, and AssetDestinations, then StartJob.

Event-Driven Data Pipelines

Engineering teams want pipelines that fire as soon as new data arrives, not on a schedule. AWS Data Exchange's CreateEventAction with REVISION_PUBLISHED triggers an automatic export to S3 each time the data provider publishes a revision, removing the need for polling.

Call CreateEventAction with Event {RevisionPublished: {DataSetId}} and Action {ExportRevisionToS3: {RevisionDestinations}} to auto-export future revisions.

Cataloguing Entitlements Across Accounts

Data teams need to know which data sets the account is entitled to and what revisions are available. ListDataSets and ListDataSetRevisions paginate through the catalogue, and ListRevisionAssets enumerates the files inside each revision.

Call ListDataSets with Origin=ENTITLED, then for each data set ListDataSetRevisions and return the latest 5 revisions with their CreatedAt timestamps.

API Asset Invocation

Some Data Exchange data sets expose API assets - live endpoints rather than file dumps. SendApiAsset proxies requests to those endpoints with the entitlement scoped to the subscription, so the consumer never holds the provider's API keys directly.

Call SendApiAsset with AssetId, DataSetId, RevisionId, Method=GET, and Path='/quote' to fetch live data from a subscribed API asset.

Agent-Driven Data Onboarding

An AI agent helping a data team onboard new providers can list entitlements, set up event actions, and trigger initial exports without operating the AWS console. Through Jentic, the agent issues each operation as one structured call with vault-isolated credentials.

For each entitled DataSetId, create an event action exporting future revisions to s3://central-data-lake/<dataset>/, then trigger an immediate export of the latest revision.

Key Endpoints

29 endpoints — jentic publishes the only available openapi specification for aws data exchange, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/jobs

Create an import or export job

GET

/v1/data-sets

List data sets and entitlements

GET

/v1/data-sets/{DataSetId}/revisions

List revisions for a data set

GET

/v1/data-sets/{DataSetId}/revisions/{RevisionId}/assets/{AssetId}

Get an asset from a revision

POST

/v1/event-actions

Create an event action

GET

/v1/jobs/{JobId}

Get the status of a job

POST

/v1/jobs

Create an import or export job

GET

/v1/data-sets

List data sets and entitlements

GET

/v1/data-sets/{DataSetId}/revisions

List revisions for a data set

GET

/v1/data-sets/{DataSetId}/revisions/{RevisionId}/assets/{AssetId}

Get an asset from a revision

POST

/v1/event-actions

Create an event action

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS SigV4 (HMAC) credentials for the AWS Data Exchange are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access via Jentic's MAXsystem rather than holding the raw AWS access key ID and secret access key in their context.

Intent-based discovery

Agents search Jentic with intents like 'export the latest Data Exchange revision to S3' and Jentic returns the matching AWS Data Exchange operation with its input schema, so the agent can call the correct endpoint without browsing the AWS service reference.

Time to first call

Direct integration: 2-4 days for SigV4 request signing, IAM policy setup, and error handling across AWS Data Exchange operations. Through Jentic: under 1 hour - search by intent, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Marketplace Catalog

Manage Marketplace listings that include Data Exchange products.

Use Marketplace Catalog for listing-side operations; use Data Exchange for subscriber data operations.

Alternative

Snowflake Data Marketplace

Snowflake's marketplace for live shared data sets.

Choose Snowflake Marketplace for warehouse-native sharing; choose Data Exchange for AWS S3-native delivery.

Complementary

Amazon Athena

Serverless SQL over data in S3, including DataBrew outputs and Data Exchange exports.

Pair Athena with the source API to query the prepared or delivered data.

FAQs

Specific to using AWS Data Exchange API through Jentic.

Why is there no official OpenAPI spec for AWS Data Exchange?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Data Exchange via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Data Exchange API use?

AWS Signature v4 (HMAC) with IAM permissions on dataexchange:* and pass-through permissions on the S3 buckets used as job destinations. Jentic stores the AWS credentials in its vault and signs each request.

Can I auto-export new data set revisions through the API?

Yes. Use CreateEventAction with Event {RevisionPublished: {DataSetId}} and Action {ExportRevisionToS3: {RevisionDestinations}}. Each new revision a provider publishes is then exported automatically to the configured S3 location.

What are the rate limits for the AWS Data Exchange API?

Per-account, per-region TPS limits apply per operation; ListJobs, GetJob, and ListDataSets are higher TPS than CreateJob. Long-running export jobs are throttled per account by concurrent job count rather than TPS.

How do I export the latest revision of a data set to S3 through Jentic?

Search Jentic for 'export the latest revision of a Data Exchange data set to S3', load the CreateJob schema, and execute it with Type=EXPORT_REVISIONS_TO_S3 and the destination bucket. Then call StartJob and poll GetJob until State is COMPLETED.

Is the AWS Data Exchange API free?

The API is free to call. Data set subscriptions are billed per the provider's published price, and S3 storage and transfer of exported data are billed separately.