DDownload API

Name: DDownload API API
Brand: DDownload API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject StorageapiKey16 EndpointsREST

For Agents

List, rename, move, and delete files and folders on DDownload, plus discover the right upload server and read account stats. Suited for agents managing hosted-file libraries.

Quickstart

Get started with DDownload API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list DDownload files in a folder"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with DDownload API API.

Read account profile and storage statistics from /account/info and /account/stats

Discover the correct upload server URL via /upload/server before pushing a file

Inspect a single file's metadata or batch-check up to many file codes at once

Rename files, move them between folders, and toggle public or private status

GET STARTED

Start building with DDownload API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for DDownload API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for DDownload API, keeping it validated and agent-ready. DDownload is a file-hosting platform whose v2 API covers account information, upload server discovery, file and folder lifecycle, and batch existence checks. Authentication is a single API key passed as a query parameter. The 16 endpoints follow a flat, action-style convention (e.g. /file/rename, /folder/create) rather than RESTful CRUD, so workflows tend to chain GETs with action verbs in the path.

Use Cases

Patterns agents use DDownload API API for, with concrete tasks.

★ Programmatic file library management

Teams using DDownload as a hosted file backend often need to keep file names, folder structures, and visibility settings in sync with an external system. The API exposes /file/rename, /file/set_folder, and /file/set_property to drive these mutations, plus /folder/list and /file/list for reconciliation. Because every endpoint is a GET with the API key as a query parameter, the workflow fits cleanly inside a scheduled batch job.

Call /folder/list to enumerate folders, then for each mismatched file call /file/set_folder with the file_code and target fld_id.

Upload pipeline with server discovery

DDownload requires clients to call /upload/server first and post the binary to the returned host rather than to a fixed endpoint. After upload, /file/info confirms the file_code and size are correct. This pattern keeps uploads close to the user geographically but means an agent must always run the discovery step before sending bytes.

GET /upload/server, POST the file to the returned URL, then GET /file/info?file_code={code} to verify the upload succeeded.

Batch existence and integrity checks

Distribution platforms that publish DDownload links at scale need to verify that referenced files still exist before serving them to end users. The /file/check endpoint accepts a list of file codes and returns existence status per code, and /files/deleted lists files removed in the recent window so a downstream catalogue can flag broken links and trigger re-uploads.

GET /file/check?file_code=code1,code2,code3 and flag any entry where status is not 'available' for re-upload.

AI agent managing a hosted file library through Jentic

An agent assigned to keep a DDownload library tidy can search Jentic for 'rename a DDownload file' or 'list DDownload folders' and execute the matching operation without ever seeing the API key. Jentic injects the key as a query parameter and returns clean JSON, so the agent can stay focused on the file-organisation task rather than transport details.

Search Jentic for 'rename a DDownload file', load the /file/rename schema, supply file_code and the new name, and execute.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for ddownload api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/account/info

Get account info

GET

/account/stats

Get account statistics

GET

/upload/server

Discover the upload server URL

GET

/file/list

List files in the account

GET

/file/check

Batch-check file existence

GET

/file/rename

Rename a file by file_code

GET

/folder/create

Create a new folder

GET

/folder/delete

Delete a folder

GET

/account/info

Get account info

GET

/account/stats

Get account statistics

GET

/upload/server

Discover the upload server URL

GET

/file/list

List files in the account

GET

/file/check

Batch-check file existence

GET

Why though Jentic?

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

Credential isolation

The DDownload API key is stored encrypted in the Jentic vault (MAXsystem). Agents execute operations through Jentic and the key is appended as the 'key' query parameter at call time — it never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'rename a DDownload file' or 'list DDownload folders') and Jentic returns the matching action endpoint with its input schema, sidestepping the need to learn DDownload's flat path conventions.

Time to first call

Direct DDownload integration: about a day to wire up server discovery, key handling, and the action-style endpoints. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Dropbox API

Mature file-storage and sync platform with collaboration features and shared links.

Choose Dropbox when you need shared collaboration, granular permissioning, or mobile sync rather than simple hosted-file delivery.

Alternative

Box API

Enterprise content platform with governance, classification, and admin controls.

Choose Box when compliance, retention policies, or enterprise SSO matter more than raw file hosting.

Complementary

Filestack API

File-upload pipeline with transformations and CDN delivery.

Pair with DDownload when you need image transforms or document conversion before storing the result.

FAQs

Specific to using DDownload API API through Jentic.

Why is there no official OpenAPI spec for DDownload API?

DDownload does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DDownload API 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 DDownload API use?

DDownload uses a single API key passed as the query parameter named key on every request. Through Jentic the key is held in the encrypted vault and injected at execution time, so the raw key never enters the agent's prompt or response.

Can I upload files directly with the DDownload API?

Not at the api-v2 base URL. The flow is two-step: GET /upload/server to discover the upload host, then POST your file to the returned URL. Confirm the result by calling /file/info with the returned file_code.

What are the rate limits for the DDownload API?

The OpenAPI spec does not document explicit rate limits. Treat /file/check as the preferred way to verify many files in one call rather than calling /file/info per code, which keeps request volume predictable.

How do I list all files in a DDownload folder through Jentic?

Run pip install jentic, search for 'list DDownload files in a folder', and Jentic returns the /file/list operation with its input schema. Load the operation, supply the fld_id of the folder, and execute. Jentic attaches the API key automatically.

Can the DDownload API recover deleted files?

It can list them. /files/deleted returns recently removed files so you can identify candidates for re-upload, but the API itself does not undelete in place — you re-upload via /upload/server and then move the new file_code into the right folder with /file/set_folder.