Dock Certs ACTION
Issue Credential
Issue a new credential. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Dock Certs account once, then configure and run Issue Credential from your backend or agent.
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: "dock_certs-issue-credential",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
dock_certs: { authProvisionId: "apn_xxxxxxx" },
issuerProfile: "Issuer Profile",
anchor: true,
},
})
console.log(result)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": "dock_certs-issue-credential",
"configured_props": {
"dock_certs": { "authProvisionId": "apn_xxxxxxx" },
"issuerProfile": "Issuer Profile",
"anchor": true
}
}'// 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": "dock_certs",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "dock_certs-issue-credential",
arguments: {
issuerProfile: "Issuer Profile",
anchor: true,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
issuerProfile Issuer Profile | string | Identifier of the profile issuing the credential Required Dynamic |
anchor Anchor | boolean | Whether to anchor the credential on the blockchain as soon as it is issued. Defaults to false. Optional |
persist Persist | boolean | Whether to store an encrypted version of this credential with Dock Certs. Defaults to false, if true you must supply password. Optional |
password Password | string | Password used to encrypt the credential if you choose to store it. The same password must be used to retrieve the credential contents. Dock does not store this password. Optional |
template Template Design | string | The ID of the intended template/design Optional Dynamic |
type Type | string | Credential type Required Dynamic |
subject Credential Subject | string | A unique identifier of the recipient. Example: DID, Email Address, National ID Number, Employee ID, Student ID, etc. Required |
status Registry | string | Identifier of the credential's revocation registry Optional Dynamic |
expirationDate Expiration Date | string | The date and time in GMT that the credential expired is specified in RFC 3339 format. The default value of the expirationDate will be empty if the user does not provide it. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- dock_certs-issue-credential
- Version
- 0.0.3
- App
- Dock Certs
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗