Guide
API for people and integrations
Learn what the API is for, which endpoints are available, and how to use them with scripts, n8n, or LLM integrations.
What Is This API
This API exposes JSON with salamyx.com tool listings and page metadata so integrations, automation, and assistants do not need to scrape HTML.
Why It Is Useful
- Automations can read tool metadata without parsing HTML pages.
- You can build n8n flows, scripts, and MCP wrappers on top of stable JSON.
- As new tools are added, they appear in the catalog automatically.
How To Start
https://salamyx.com/api/v1
Try These Endpoints
GET /api/v1/healthGET /api/v1/toolsGET /api/v1/tools?id=sha256GET /api/v1/pages/sha256
Need Full API Docs?
Open the developer API documentation with endpoint details and response examples.
Privacy And Limitations
API v1 returns metadata and does not replace local in-browser processing on tool pages.
- The first API version is metadata-first and does not execute every tool server-side.
- For per-tool server execution, dedicated endpoints should be added where truly needed.
- Always verify automation behavior against current API docs before production workflows.
FAQ
Why does this API exist?
It gives a stable JSON interface for tool catalogs and page metadata so automations do not need to parse HTML.
Who is this API for?
It is for developers, no-code workflows like n8n, and agent integrations through MCP wrappers or custom scripts.
Can I run tools server-side through API v1?
Not by default. API v1 focuses on metadata and listing tool URLs—not executing tools for you.
Where should I start?
Start with /api/v1/health and /api/v1/tools, then request specific pages by id with /api/v1/pages/{pageId}.
Will this API evolve?
Yes. Future versions can add validation and execution endpoints when needed.