# ExpressConsent docs

ExpressConsent records what a person saw and agreed to on your website, so you can prove it later.

Add a script to your site, call one function when a consumer submits a consent form, and you have a durable, third-party record of the agreement. Everything else here is about doing that accurately and about moving the evidence to whoever needs it.

## Start here

- [How ExpressConsent works](https://app.expressconsent.com/docs/how-it-works): What a Certified Digital Record is, and why capture timing decides whether it holds up.
- [Lead generators and lead buyers](https://app.expressconsent.com/docs/roles): Who captures consent evidence, who receives it, and why one company is often on both sides.
- [Capture your first CDR](https://app.expressconsent.com/docs/quickstart): Add the script, tag your form, capture on submit, and confirm the evidence landed.
- [Go live](https://app.expressconsent.com/docs/go-live): The checks worth making before real consumers reach the page.

## Common tasks

- [Tagging a form](https://app.expressconsent.com/docs/tags): Mark the disclosure, the checkbox, and the submit control so a record carries structured consent facts.
- [How to share CDRs](https://app.expressconsent.com/docs/share): Share CDRs with another organization, such as a lead buyer.
- [Receive a shared record](https://app.expressconsent.com/docs/receive): You were handed a share URL with a lead. What to do with it, and what to check before you take it.
- [Set up webhooks](https://app.expressconsent.com/docs/webhooks): Have every completed record pushed to your endpoint, and know what happens when your endpoint is down.

## Understand the model

- [Sessions and Package CDRs](https://app.expressconsent.com/docs/concepts/sessions): How captures from one visit are grouped into a single evidence document.
- [Access and collection](https://app.expressconsent.com/docs/concepts/access): Which organization can download a CDR, which one is charged for it, and how access moves when evidence is shared.
- [Glossary](https://app.expressconsent.com/docs/glossary): The terms used across these docs and the API field names they correspond to.

## Look something up

- [captureCDR()](https://app.expressconsent.com/docs/reference/capture-cdr): Capture a CDR, attach metadata, and generate a share URL.
- [window.ExpressConsent](https://app.expressconsent.com/docs/reference/sdk): Load the browser SDK and monitor capture errors.
- [SDK errors](https://app.expressconsent.com/docs/reference/errors): Every error the capture call can throw, what causes it, and whether retrying helps.
- [API conventions](https://app.expressconsent.com/docs/reference/api): Base URL, authentication, the response envelope, and pagination for the server-to-server API.
- [CDR endpoints](https://app.expressconsent.com/docs/reference/api/cdrs): List your domains, page through records, read one record in full, and collect a record.
- [Share endpoints](https://app.expressconsent.com/docs/reference/api/shares): Create a share URL for a record, and receive a record that another organization shared with you.

Working with an AI coding assistant? [Point it at these docs](https://app.expressconsent.com/docs/ai) so it stops guessing.