@bijection/connectors/docusign entrypoint to declare DocuSign resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Envelopes
pull: Status changes every 30 minutes, Connect hints read at most once per envelope per 15 minutes
The following example matches configurationconnect.
Inferred record types
Inferred record types
Configuration: standard
Case:docusign/envelopes/pull/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: docusign. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Configuration: connect
Case:docusign/envelopes/pull/connect.
Connection and resource configuration are declared by this exact case.
Credential kind: docusign. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Compiled declaration examples and configuration details are published in the connector reference. The connection’s setup is the account’sbaseUri (https://<server>.docusign.net,
from the OAuth userinfo answer) and accountId; the docusign credential is an
OAuth access token written as a bearer, replaced by hand when it expires. Identity is
the account’s accountIdGuid.
DocuSign permits a GET of one URL, including one envelope, at most once every 15
minutes, and reads prompted by Connect are not exempt. envelopes.pull therefore
reads the status-change listing (envelopes?from_date=, ordered status_changed
ascending, 100 a page) every 30 minutes by default and refuses an interval under 15
minutes. A pass carries the latest statusChangedDateTime and the next begins five
minutes before it. lastModifiedDateTime is the record version. Nothing is
withdrawn: DocuSign states no envelope deletion a read could observe.
With updates: "connect", a Connect delivery (JSON SIM) asks for a point read of
data.envelopeId. The envelope’s point read declares DocuSign’s rule as its
per-record read interval, so the platform’s refresh owner reads one envelope at most
once per 15 minutes whatever arrives: a delivery for an envelope read within the
last 15 minutes is retained and read by the first pass after the rest ends, and the
point read runs no scheduled sweep of its own. A Connect-prompted read never reads
the listing. Connect signs the exact body with HMAC-SHA256 under each active key,
one base64 digest per key in X-DocuSign-Signature-1 to -4; install the key as the
listener’s signing credential. There is no signed time and no delivery id: the
identity is derived from data.envelopeId, event and generatedDateTime, leaving
out retryCount, which changes on every retry. A delivery proves a refresh hint.
The ordering and paging come from DocuSign’s published OpenAPI description; no
request or delivery has reached DocuSign, and nothing here has been qualified.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.