ToolYourToolYourAPI Docs

Office, Web & Archives

Office, web, eBook, and archive conversion — REST and TypeScript SDK.

TypeScript SDK

ModuleSDK namespace
Officety.office
Webty.web
eBookty.ebook
Archivety.archive
File extractty.extract

Slug xlsx-to-pdfty.office.xlsxToPdf({ file }). Full tables: SDK Tool Map.

import { ToolYour } from "@toolyour/sdk";
const ty = ToolYour({ apiKey: process.env.TOOLYOUR_API_KEY! });

await ty.office.xlsxToPdf({ file: xlsxBlob });
await ty.archive.zipToTar({ file: zipBlob });

Send multipart/form-data with a file field unless noted.

Base paths

CategoryBase path
Office (XLS, PPT, ODF)/api/v1/office/*
Web (HTML, XML, JSON, CSV)/api/v1/web/*
eBook/api/v1/ebook/*
Archive (ZIP, RAR, 7z, …)/api/v1/archive/*

Each module exposes GET …/supported-conversions without an API key to list available slugs.

File conversion routes in these modules return ToolFileResponse JSON with result.downloadUrl by default (same as Documents and Convertors). See Calling Tools.

File extract

POST /api/v1/extract accepts JSON:

{
  "filename": "report.pdf",
  "mimeType": "application/pdf",
  "contentBase64": "..."
}

Returns extracted text, segments, and metadata. Requires X-Api-Key.

AI models

These match the AI tools on toolyour.com (transcription, summarization, file analysis):

EndpointBody
POST /api/v1/ai-models/file-insightsmultipart file
POST /api/v1/ai-models/text-aiJSON
POST /api/v1/ai-models/youtube-insightJSON

All AI routes require X-Api-Key. The web UI also sends Turnstile headers; API-only clients should follow the same pattern if enforced by your deployment.

See the OpenAPI sidebar for every operation.

On this page