Hexloom Labs

Hexloom File API

Merge PDF files. Read or remove EXIF and GPS metadata in photos. Files are not stored.

Developer tools#documents--productivity

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Merge PDF files. Read or remove EXIF and GPS metadata in photos. Files are not stored.

Endpoints 4

  • POSTMerge 2 to 20 PDFs in the order sent/pdf/mergeSend the PDFs as multipart form fields (file1, file2, ... up to 20). Output is limited to 500 pages. Files are held in memory for the request and not stored.
  • POSTRemove EXIF, GPS and other metadata from a JPEG, PNG or WebP without re-encoding pixels/exif/stripJPEG output keeps a minimal EXIF block holding only the orientation number, plus the colour profile, so the photo still displays upright; a tool such as…
  • POSTList the EXIF and other metadata found in an image, as JSON/exif/inspectLong text values are shortened (EXIF text to 256 characters, comments and PNG text to 120) and about 200 rows are listed.
  • GETHealth check/status

API details

Base URL
https://hexloomlabs.com/api/v1
Authentication
None declared in the description
Operations
4 operations on 4 pathsPOST 3GET 1
Response formats
application/json application/pdf image/jpeg image/png
Description format
OpenAPI 3.0.3, API version 0.1.0

How to test the Hexloom File API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Hexloom File API collection, without the publisher's secrets.
  3. Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
  4. Send a requestPick an endpoint, for example “Merge 2 to 20 PDFs in the order sent” (POST /pdf/merge), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Hexloom File API?

Merge PDF files. Read or remove EXIF and GPS metadata in photos. Files are not stored. It is listed under Developer tools and has 4 endpoints.

Who publishes the Hexloom File API?

It is listed from Hexloom Labs's public API description (an OpenAPI document), not published by Hexloom Labs on Swastik Codes. Anyone who controls hexloomlabs.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Hexloom File API?

Requests go to https://hexloomlabs.com/api/v1. Endpoint paths are added to this base URL.

How do I authenticate with the Hexloom File API?

Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.

How many endpoints does the Hexloom File API have?

4 operations on 4 paths (3 POST, 1 GET).

Is forking the Hexloom File API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.