Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsDocuSign ToolsDocusign Get Bccemail Archive History
DocuSign Tools

Docusign Get Bccemail Archive History

Retrieves the history of changes made to a specific BCC email archive configuration for a DocuSign account. This endpoint allows users to track modifications, including creation, updates, and closure of email addresses used for archiving DocuSign-generated emails. It provides de…

Write actionRisk level 2 of 5OAuth connection
Use Docusign Get Bccemail Archive History

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • countstring
    An optional query parameter that specifies the maximum number of results to return in the response. Use this parameter in conjunction with "start_position" to implement pagination and control the size of the result set. If not specified, the API will return all available results…
  • accountIdstring
    The external account number (integer) or account ID GUID that uniquely identifies the DocuSign account. This parameter is required and must be provided in the path of the API request. It is used to specify which account"s BCC email archive configuration history should be retriev…
  • start_positionstring
    An optional query parameter that specifies the zero-based index of the first result to return. Use this parameter in conjunction with "count" to implement pagination and retrieve specific subsets of the result set. The default value is 0, which returns results from the beginning…
  • bccEmailArchiveIdstring
    Required
    The unique identifier of the specific BCC email archive configuration whose history is being requested. This parameter is required and must be provided in the path of the API request. It is used to pinpoint the exact configuration for which the history should be retrieved.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.