The catalog.
258 services · 20 categories · One key, one billApply Headers and Footers on DOCX API
Add headers, footers, images, or a table of contents to DOCX files. Returns a modified DOCX download or a hosted URL.
Convert WAV to MP3
WAV to MP3 Converter turns a WAV audio file into an MP3 file. Send a binary WAV upload or a public WAV file URL, and get back either the converted audio as a binary download or a signed link to the MP3 output. Use the multipart endpoints when you already have the file in hand, or the URL endpoints when the source audio is already hosted elsewhere. The upload limit is 100 MB for the file-based routes, and the URL-based routes expect a publicly accessible WAV file. The response is simple and predictable: one path streams the MP3 file back, and the other returns a data field containing a signed URI. That makes it easy to plug this service into upload workflows, media pipelines, or back-office tools that need to normalize audio into a widely supported format. If you’re building a media library, podcast workflow, or voice app, this is the kind of conversion step you can insert before storage, playback, or distribution.
Convert PNG to WebP API
Convert PNG files or image URLs to WebP. Get binary output or a signed URL for browser-friendly image delivery and storage.
Extract Web Text
Extract visible text from a webpage as lines or a single string. Useful for scraping, indexing, and content monitoring without HTML noise.
Webpage Screenshot
Webpage Screenshot captures a live webpage as a PNG image. Send a url, optionally set delay to wait before capture, and choose quality from 1 to 5. You can either get a signed cloud data link back with /link or stream the image directly from /download. Use Webpage Screenshot when you need a visual record of a page for audits, bug reports, QA checks, social previews, or archived evidence. It is a straightforward way to turn a URL into a screenshot without managing browser automation in your own infrastructure. The /link endpoint returns a signed upload URL for the PNG screenshot, which is useful when you want to store the image in cloud storage or pass it to another service. The /download endpoint returns the screenshot as binary PNG data and also accepts an output filename. Both endpoints use the same capture inputs, so you can pick the delivery format that fits your workflow. If you are building monitoring, content review, or page documentation features, this service gives you a simple URL-to-image capture flow with predictable output.
WebP to JPEG Converter
WebP to JPEG Converter turns a WebP image into a JPEG and gives you either a signed download link or the converted file itself. Send a publicly accessible WebP URL to the /url/link or /url/download endpoints, or upload a WebP file with multipart form data to /multi-part/link or /multi-part/download. The URL-based endpoints accept a url in the request body. The multipart endpoints accept a binary file in the request body, and the download variants also accept an optional output query parameter. The link variants return a JSON object with a data field containing the output URI. The download variants return the converted image as binary data. Use this when you need JPEG output for older browsers, CMS uploads, email workflows, or downstream systems that do not handle WebP reliably. Keep your source image in WebP, convert on demand, and choose the response format that fits your pipeline: a stored file link or a streamed download.
Convert JPEG to WebP API
JPEG to WebP Converter turns a JPEG or JPG image into a WebP file. Send either a binary image upload or a publicly accessible image URL, and get back the converted result as a file download or a signed URL, depending on the endpoint you use. Use the multipart endpoints when you already have the source image in your app or form upload flow. Use the URL endpoints when the image already lives somewhere public and you want to convert it without downloading it first. In both cases, the request only needs the source image input plus the optional output query parameter. The response is simple and matches the delivery mode: download endpoints return the converted WebP as binary data, while signed-URL endpoints return a JSON object with a data field containing a URI. That makes it easy to plug JPEG to WebP Converter into image pipelines, content delivery workflows, or storage backends that prefer WebP for smaller file sizes and browser support.
WebP to PNG Converter
WebP to PNG Converter turns WebP images into PNG files from either a public URL or a multipart file upload. Send a publicly accessible url and choose whether you want the converted image streamed back as binary output or returned as a signed link in data. If you already have the image file, upload it as file and use the same two output options. The service is built for simple image format conversion, with no extra transformation steps or metadata fields to manage. Use WebP to PNG Converter when you need a PNG for browser compatibility, downstream image processing, or workflows that do not accept WebP. It fits cleanly into asset pipelines, content moderation tools, or back-office systems that accept uploads from different sources and normalize them into a standard image format. The response is intentionally minimal: either the converted PNG arrives as binary data, or you receive a URI pointing to the generated file.
Working Day Calculator
Working Day Calculator counts business days between two dates for a given country. Send a country, start, and end, and get back a breakdown of the date range in calendar terms and working-day terms. The response includes totaldays for the full inclusive range, weekends for Saturday and Sunday days, holidays for public holidays that fall on weekdays, and workingdays for the resulting Mon–Fri count after those holidays are removed. That makes it easy to calculate lead times, SLA windows, payroll periods, project timelines, and delivery estimates without hard-coding your own calendar logic. Use Working Day Calculator when your app needs country-aware date math. For example, you can verify whether a support deadline lands on a working day, estimate how many business days remain in a procurement cycle, or compute working-time reports for internal tooling. Because the country is part of the request, the result can reflect local public holidays rather than just weekdays. That helps keep schedule calculations consistent across regions and avoids off-by-one errors in date ranges.
Generate Archives API
ZIP Archiver creates ZIP files from either remote file URLs or uploaded files. Send it a list of urls or a list of binary files, and get back either a streamed ZIP download or a signed link to the archive. Use the /url/download and /file/download endpoints when you want the archive returned directly as binary data. Use the /url/link and /file/link endpoints when you prefer a generated URI you can store, share, or fetch later. The only input it needs is the list of files you want to bundle; the archive filename can be passed as output on the download and file-link variants. ZIP Archiver is a good fit for packaging reports, assets, invoices, image sets, or any batch of documents into a single download. It also works well in backend workflows where you need to collect remote resources into one archive before handing them off to another service or user.
Unarchiver Extractor
Archive Extractor unpacks ZIP, RAR, and 7Z archives and returns signed URLs for each extracted file. Send it either a remote archive URL or a local archive upload, and you get back an array of file URLs you can download or pass to downstream workflows. Use POST /url/link when the archive is already hosted somewhere accessible by URL. Use POST /file/link when you have the archive file in hand and want to upload it directly. In both cases, the response is a data array of signed cloud storage URLs, one for each file extracted from the archive. This is a good fit for ingestion pipelines, document processing, and support tooling where users submit bundled assets. For example, you can accept a ZIP of invoices, extract each file, and forward the returned URLs to OCR, storage, or review steps without doing archive handling in your own code. Archive Extractor keeps the interface simple: one input for the archive, one structured list of file links out. That makes it easy to drop into file intake jobs, batch processors, or any backend that needs to open compressed uploads and work with the extracted contents individually.
Protected Unarchiver Extractor
Protected Archive Extractor lets you send a password-protected archive and get signed URLs for each extracted file back. It supports uploaded archives through file and remote archives through url, and both endpoints require a password to decrypt the contents. Use it when you need to unlock .zip, .rar, or .7z files without handling the extraction yourself. The response is a data array of URI strings, each pointing to an extracted file in signed cloud storage. That makes it straightforward to hand off decompressed documents, images, or other assets to the next step in your workflow. Protecting access to uploaded archives is a common need in document pipelines, support tooling, and internal file processing systems. You can accept an archive from a user, decrypt it with the provided password, and store or forward the resulting files using the returned links. Because the API returns URLs instead of raw binary payloads, it fits cleanly into systems that already work with object storage or downstream fetch jobs.