Manuscript Python API Docs | dltHub

Build a Manuscript-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Manuscript API supports creating, listing, and editing cases via POST requests with JSON payloads. The base URL is https://api.manuscript.com/. Token authentication is required for all requests. The REST API base URL is https://api.manuscript.com/ and All requests require an API token (Manuscript) or HTTP Digest with username and API key (ScholarOne)..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Manuscript data in under 10 minutes.


What data can I load from Manuscript?

Here are some of the endpoints you can load from Manuscript:

ResourceEndpointMethodData selectorDescription
submissions_full_metadata_documentidsapi/s1m/v1/submissions/full/metadata/documentids?ids={ids}&site_name={site}&locale_id={id}GETresultGet full metadata for submissions by document IDs or submission IDs
submissions_basicapi/s1m/v1/submissions/basic/contributors/authors/submissionids?ids={ids}&site_name={site}GETresultGet basic submission contributor/author info by submission IDs
get_submission_info_basicapi/s1m/v1/getSubmissionInfoBasic?ids={ids}&site_name={site}GETresultRetrieve basic submission information (supports list input)
authors_full_by_documentidapi/s1m/v1/getAuthorFullByDocumentId?ids={ids}&site_name={site}GETresultGet full author details by document IDs
submissions_searchapi/searchPOSTdataSearch/submission queries (Manuscript API uses token in request body)

How do I authenticate with the Manuscript API?

Manuscript calls include a "token" field in the request body or query string; ScholarOne uses HTTP Digest authentication with a UserName and API Key in the Authorization header.

1. Get your credentials

  1. Log in to your Manuscript or ScholarOne admin console. 2) For Manuscript, generate an API token in the user/account settings (users with 2FA must generate tokens via the UI). 3) For ScholarOne, request an API Key from your ScholarOne Relationship Manager; they will provide a username and API Key. 4) Store the API token / API Key securely and include it in each request according to the API's authentication method.

2. Add them to .dlt/secrets.toml

[sources.manuscript_source] api_key = "your_api_key_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Manuscript API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python manuscript_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline manuscript_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset manuscript_data The duckdb destination used duckdb:/manuscript.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline manuscript_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads submissions_full_metadata_documentids and get_submission_info_basic from the Manuscript API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def manuscript_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.manuscript.com/", "auth": { "type": "http_basic", "api_key": api_key, }, }, "resources": [ {"name": "submissions_full_metadata_documentids", "endpoint": {"path": "api/s1m/v1/submissions/full/metadata/documentids", "data_selector": "result"}}, {"name": "get_submission_info_basic", "endpoint": {"path": "api/s1m/v1/getSubmissionInfoBasic", "data_selector": "result"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="manuscript_pipeline", destination="duckdb", dataset_name="manuscript_data", ) load_info = pipeline.run(manuscript_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("manuscript_pipeline").dataset() sessions_df = data.submissions_full_metadata_documentids.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM manuscript_data.submissions_full_metadata_documentids LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("manuscript_pipeline").dataset() data.submissions_full_metadata_documentids.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Manuscript data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Manuscript?

Request dlt skills, commands, AGENT.md files, and AI-native context.