Add Datasets and Uploads APIs, deprecate Tables API

[va3093]

Context

The Dune API has introduced new /v1/datasets and /v1/uploads endpoints to replace the legacy /v1/table endpoints. This update aligns the TypeScript client with the latest API specification and provides users with access to new functionality while maintaining backward compatibility.

Currently, the client only supports the legacy /v1/table endpoints which are being phased out in favor of the more comprehensive and better-organized /v1/uploads endpoints. Additionally, there was no support for the new /v1/datasets endpoints which provide read access to dataset information.

What Changed

New APIs Added

DatasetAPI (client.dataset):

• list(args?) - List datasets with filtering by owner and type
• getBySlug(slug) - Get detailed dataset information by slug

UploadsAPI (client.uploads):

• list(args?) - List all uploaded tables for the account
• create(args) - Create an empty table with defined schema
• uploadCsv(args) - Upload CSV data as a new table
• insert(args) - Insert data into an existing table (CSV/JSON)
• delete(args) - Delete an uploaded table
• clear(args) - New! Clear all data from a table while preserving schema

Deprecation Changes

All four methods in TableAPI are now deprecated with console warnings:

• table.uploadCsv() → Use uploads.uploadCsv()
• table.create() → Use uploads.create()
• table.insert() → Use uploads.insert()
• table.delete() → Use uploads.delete()

The deprecated methods continue to work exactly as before, ensuring full backward compatibility. Users will see helpful deprecation warnings guiding them to the new API.

Type Definitions

Added comprehensive type definitions matching the OpenAPI specification:

• Request types: ListDatasetsArgs, ListUploadsArgs, ClearTableArgs
• Response types: DatasetResponse, ListDatasetsResponse, TableListResponse, TableClearResponse
• Supporting types for dataset columns, owners, and metadata

Implementation Details

Both new API classes follow established patterns:

• Extend Router base class for consistent HTTP handling
• Use camelCase method names for JavaScript conventions
• Implement proper error handling and logging
• Include JSDoc comments for IDE support
• Export through central index.ts for clean public API

Migration Example:

// Old (still works, shows deprecation warning)
await client.table.uploadCsv({ table_name: "data", data: csv });

// New (recommended)
await client.uploads.uploadCsv({ table_name: "data", data: csv });
await client.dataset.list({ owner_handle: "dune", limit: 50 });

[bh2smith]

Seems great, just some failing tests

[bh2smith]

May need to add an env var here.

[va3093]

@bh2smith do you know what the team handle that owns the API_KEY we use here?

[bh2smith]

Its probably my account bh2smith. I can try locally and see.

[bh2smith]

So locally (using a different API KEY) the error actually said the associated namespaces I could use with that key:

    Response Error: HTTP - Status: 401, Message: {"error":"You are not authorized to create a table under the 'your_username' namespace. Your accessible namespaces: 'bh2smith'"}

This leads me to believe that the API key used in the test here is so old that it may not have a name to link it to?

[bh2smith]

I discovered that I am unable to call the usage endpoint:

https://api.dune.com/api/v1/usage

{"error":"An internal error occurred"}

[va3093]

Ok. I will create a new team and generate a new API key.

[va3093]

I discovered that I am unable to call the usage endpoint:

https://api.dune.com/api/v1/usage

{"error":"An internal error occurred"}

does it still not work for you @bh2smith . I just tried it and it worked for me.