DocuSign: Creates a BCC email archive configuration
DocuSign esignature.esignatureBccemailArchivePostBccemailArchive: arguments, response, policy and SDK examples.
← Esignature operations · Get started
Operation docusign.esignature_bccemailarchive_postbccemailarchive
Provider route: POST /restapi/v2.1/accounts/{accountId}/settings/bcc_email_archives. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/docusign with npm, or alter-sdk-docusign with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { DocuSignIntegration } from "@alter-ai/docusign";
async function execute(input: Parameters<DocuSignIntegration["esignature"]["esignatureBccemailArchivePostBccemailArchive"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new DocuSignIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.esignature.esignatureBccemailArchivePostBccemailArchive(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_docusign import DocuSignIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = DocuSignIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.esignature.esignature_bccemail_archive_post_bccemail_archive(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.accountId | string | Required within parent | |
body | Model | Optional | Expand Creates a BCC email archive configuration — response body |
Referenced models: Creates a BCC email archive configuration — response body
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand Creates a BCC email archive configuration — response body |
Referenced models: Creates a BCC email archive configuration — response body
Schemas
Section titled “Schemas”Creates a BCC email archive configuration — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | This object contains information abut a BCC email archive configuration (a BCC email address used to archive Docusign-generated emails). |
accountId | string | Optional | The ID of the account that owns the BCC email archive configuration. |
bccEmailArchiveId | string | Optional | The ID of the BCC email archive configuration. |
created | string | Optional | The UTC DateTime when the BCC email archive configuration was created. |
createdBy | Model | Optional | Expand Gets a specific template associated with a specified account — response body — owner Details about the user who created the BCC email archive configuration. |
email | string | Optional | The BCC email address to use for archiving Docusign messages. Example: customer_bcc@example.com |
emailNotificationId | string | Optional | The GUID of the activation email message sent to the BCC email address. |
modified | string | Optional | The UTC DateTime when the BCC email archive configuration was last modified. |
modifiedBy | Model | Optional | Expand Gets a specific template associated with a specified account — response body — owner Details about the user who last modified the BCC email archive configuration. |
status | string | Optional | The status of the BCC email address. Possible values are: - `activation_sent`: An activation link has been sent to the BCC email address. - `active`: The BCC email address is actively used for archiving. - `closed`: The BCC email address is no longer used for archiving. |
uri | string | Optional | The helper URI for retrieving the BCC email archive. |
Referenced models: Gets a specific template associated with a specified account — response body — owner
Gets a specific template associated with a specified account — response body — owner
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
accountId | string | Optional | The account ID associated with the envelope. |
accountName | string | Optional | The name on the account. |
activationAccessCode | string | Optional | Access code provided to the user to activate the account. |
email | string | Optional | The user's email address. |
errorDetails | Model | Optional | Expand Locks a template — response body — error Details This object describes errors that occur. It is only valid for responses and ignored in requests. |
ipAddress | string | Optional | |
loginStatus | string | Optional | When **true,** indicates that the user is logged in. This is a read-only property. |
membershipId | string | Optional | The user's membership ID. |
sendActivationEmail | string | Optional | This field is no longer supported for most accounts. To create an eSignature user without sending an activation email, use the Admin API by following [these steps](/docs/admin-api/how-to/create-active-user/). |
uri | string | Optional | A URI containing the user ID. |
userId | string | Optional | The ID of the user to access. |
userName | string | Optional | The name of the user. |
userStatus | string | Optional | Status of the user's account. One of: - `ActivationRequired` - `ActivationSent` - `Active` - `Closed` - `Disabled` |
userType | string | Optional | The type of user, for example `CompanyUser`. |
Referenced models: Locks a template — response body — error Details
Locks a template — response body — error Details
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | This object describes errors that occur. It is only valid for responses and ignored in requests. |
errorCode | string | Optional | The code associated with the error condition. |
message | string | Optional | A brief message describing the error condition. |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: docusign.esignature_bccemailarchive_postbccemailarchive. Catalog operation: esignature:BCCEmailArchive_PostBCCEmailArchive. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.