CONNECT APP
Build with Docparser
Developer Tools
- API key
MCP
Give your agent Docparser tools
Every Docparser action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Docparser account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "docparser",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Fetch Document by URL:
const result = await mcp.callTool({
name: "docparser-fetch-document-url",
arguments: {
parserId: "Parser ID",
url: "Document URL",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "docparser",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Fetch Document by URL:
result = await session.call_tool("docparser-fetch-document-url", {
"parserId": "Parser ID",
"url": "Document URL",
})API PROXY
Call the Docparser API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Docparser API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.docparser.com/v1/ping",
})
// Any allowed Docparser endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.docparser.com/v1/ping
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZG9jcGFyc2VyLmNvbS92MS9waW5n?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Docparser actions from your backend
Connect a user's Docparser account once, then run Fetch Document by URL on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "docparser-fetch-document-url",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
docparser: { authProvisionId: "apn_xxxxxxx" },
parserId: "Parser ID",
url: "Document URL",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="docparser-fetch-document-url",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"docparser": {"authProvisionId": "apn_xxxxxxx"},
"parserId": "Parser ID",
"url": "Document URL",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "docparser-fetch-document-url",
"configured_props": {
"docparser": { "authProvisionId": "apn_xxxxxxx" },
"parserId": "Parser ID",
"url": "Document URL"
}
}'TOOLS
Docparser actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Fetch Document by URL
actionFetches a document from a provided URL and imports it to Docparser for parsing. See the documentationWritev0.0.2 -
List Parser ID Options
actionRetrieves available options for the Parser ID field.Read-onlyv0.0.1 -
Upload Document
actionUploads a document to docparser that initiates parsing immediately after reception. See the documentationWritev1.0.3
EVENTS
Docparser triggers
Event sources your backend can deploy for users and receive through a webhook.
- App slug
- docparser
- Authentication
- API key
- Categories
- Developer Tools
- Actions
- 3
- Triggers
- 1
- API proxy
- Available