Signature contents

GET/v1/docs/{docId}/versions/signatures/{sha}/{fieldKey}/contentsv3.0.0-next.15

The DER /Contents of a signed field in one base version (immutable).

`fieldKey` is the field's fully qualified name, token-text encoded (the same encoding attachment keys use).

Authentication#

Any one of these credentials is accepted.

API token

The deployment's static root credential (CLOUDPDF_API_AUTH_TOKENS), valid on every surface.

Document token

Doc-scoped JWT, valid only on the /v1/docs/{docId} subtree it names, gated by the capability scopes it carries (each operation's x-required-capability).

Document capabilitydoc.forms.read

Parameters#

docIdpathstringrequired

shapathstringrequired

fieldKeypathstringrequired

X-Document-Passwordheaderstring

Base64-encoded password for an encrypted document. Valid only with the API token (403 anywhere else). An encrypted document answers 422 DocPasswordRequired when the header is absent. Viewer doc JWTs use the SDK password-session flow instead.

SDK examples#

The selected SDK is remembered across the API reference. Values are examples; replace them with identifiers and input from your application.

import { CloudPDFClient } from "@cloudpdf/sdk";

const client = new CloudPDFClient({
  baseUrl: "https://yourhost.com/path/to/api",
  token: "<token>",
});

await client.doc.versions.signatureContents({
  docId: "docId",
  sha: "sha",
  fieldKey: "fieldKey"
});

Responses#

200OK

application/pkcs7-signaturestring<binary>

404Not found

application/jsonDocVersionsSignatureContentsResponse

defaultError

application/jsonEngineErrorPayload

name"EngineError"

messagestring

detailsobjectoptional