Create Authentication
create_authentication Creates the current signing authentication transition for an agreement.
Conventions
Authentication
All endpoints require a Bearer token. Pass it in the Authorization header as Bearer <token>. Tokens are issued from the API settings page in your workspace.
Base URL
All paths are relative to https://mcp.allsign.app. The spec includes full paths; strip the base when constructing requests.
Versioning
The current version is 0.1.0. Breaking changes are documented in the Changelog and announced before taking effect.
Specification
The server follows the MCP specification and communicates via JSON-RPC 2.0. All documentation on this page is generated directly from the spec.
Example
curl "https://mcp.allsign.app" \-X POST \-H "Authorization: Bearer {token}" \-H "Content-Type: application/json" \--data-raw '{"jsonrpc": "2.0","id": 1,"method": "tools/call","params": {"name": "create_authentication","arguments": {"agreement_ref": "00000000-0000-4000-8000-000000000000"}}}'
Request
Request Body
{
"agreement_ref": "00000000-0000-4000-8000-000000000000",
"password": ""
}agreement_refPublic stable resource reference.
passwordCurrent account password when password-based reauthentication is required.
Responses
200 OK
{
"session": {},
"verification": {
"channel": "",
"expires_at": "",
"ref": "00000000-0000-4000-8000-000000000000"
}
}sessionAuthenticated session continuation payload.
verificationSignature or signing authentication verification challenge.
verification.channel
verification.expires_at
verification.refPublic stable resource reference.
Errors
Standard JSON-RPC 2.0 error codes apply.
-32600Invalid Request
-32601Method not found
-32602Invalid params
-32603Internal error
401Bearer token missing or invalid
403Actor does not have the required capacity for this operation