Overview

String Web Access is a plain HTTP API, so anything that can send a POST can use it. That includes the automation platforms most teams already run, with no SDK and no custom code. Zapier also has a String Web Access app, invite-only for now.

Each page below gives the exact configuration for one platform: which node or action to add, what to put in every field, and what comes back.

What you need

Calling the API from any platform takes the same two things:

• Your API key, from the String dashboard. It goes in an Authorization: Bearer header — see Authentication.
• An endpoint. These pages use /v1/fetch because it is the most common starting point, but /v1/search and /v1/sitemap work the same way. Only the URL and the body change.

Choosing where the work happens

String returns clean Markdown or structured JSON, so most of the parsing an automation would otherwise do can happen inside the request instead of in the platform:

• "format": "markdown" returns LLM-ready text, so the next step can be a model call with no HTML handling in between. See Response formats.
• A jsonSchema in the request returns only the fields you asked for, so no downstream parsing step is needed at all. See Structured extraction.

That matters more on these platforms than in code, because every extra step costs a task or an execution.

Using MCP instead

If your automation is driven by an AI agent rather than a fixed workflow, the MCP server is usually the better fit: the agent discovers the tools itself instead of you wiring one request at a time.