DocuSign eSignature API

Faster paperwork.A clearer first day.

CarLife uses DocuSign to let photographers and video editors review and sign required onboarding agreements securely from inside their onboarding workflow.

Primary use case

Contractor agreements during photographer and editor onboarding.

Signers do not need a DocuSign account. Documents open in a secure embedded signing session.

How it works

From authorization to signature

The integration is intentionally narrow: connect an authorized sender, select templates, send the right paperwork, and confirm completion.

01

An administrator connects DocuSign

A CarLife administrator authorizes one organization-owned DocuSign account using DocuSign’s OAuth 2.0 Authorization Code Grant flow.

02

Templates are assigned

The administrator selects existing DocuSign templates and assigns them to the photographer or editor onboarding packet.

03

An envelope is created

When a contractor reaches the paperwork step, CarLife creates an envelope from the selected template using the contractor’s name and email address.

04

The contractor signs

The contractor opens a short-lived embedded signing session, completes the document in DocuSign, and returns directly to CarLife.

05

CarLife verifies completion

CarLife reads the envelope’s authoritative status from DocuSign and unlocks the next onboarding step after all required documents are complete.

Authorization

OAuth 2.0 Authorization Code Grant

Only an authenticated CarLife administrator can initiate authorization. DocuSign redirects back to CarLife at the registered callback URL, where the authorization code is exchanged server-side.

Scope

signature

Send envelopes and manage the signing workflow.

Scope

extended

Maintain access through secure refresh tokens.

eSignature API activity

What CarLife does

  • Read templates available in the connected organization account
  • Create envelopes from administrator-selected templates
  • Create embedded recipient views for authenticated contractors
  • Read envelope status after the signer returns to CarLife

Data & security

Designed around least access.

CarLife requests only the scopes needed to run the onboarding signature workflow. Access can be revoked by the connected DocuSign account owner at any time.

Encrypted credentials

OAuth access and refresh tokens are encrypted at rest and are never exposed to browser clients.

Verified callbacks

OAuth state is signed and time-limited. Envelope status is re-read from DocuSign instead of trusting a browser return parameter.

User-specific signing

Embedded signing sessions are created only for the authenticated contractor and use short-lived recipient URLs.

DocuSign is the record

CarLife stores envelope identifiers and status. Executed document PDFs remain in DocuSign and are not copied into CarLife storage.

Questions about this integration?

Contact CarLife or review our policies for more information.