Penneo core concepts

Shared foundations

These apply no matter which product you integrate with.

Authentication

Every request to a Penneo API must be authenticated, and it works the same way
for both products. See the Authentication section.

Environments

Penneo provides separate sandbox and production environments. Develop and
test against sandbox, then switch to production once you're ready. Credentials and
data are not shared between the two environments, and the same base URLs apply to both Penneo
Sign and Penneo Collect.

Staying in sync: webhooks and polling

How you keep your system up to date depends on the product:

• Penneo Sign supports webhooks — subscribe to events (for example, a case file being completed) and Penneo notifies your system automatically.
• Penneo Collect does not offer webhooks yet, so you poll for new submissions on a schedule that fits your use case.

Penneo Sign concepts

Penneo Sign is built around the case file — a container for the files to
be signed and the people who sign them. A typical integration builds a case file,
sends it, tracks its progress, and retrieves the signed result.

• Case file — the top-level object representing one signing process. It bundles
  the files and signers, and moves through a lifecycle from created to
  completed.
• Documents — the files to be signed. A file always belongs to a case
  file, and is either signable (requires signatures) or an attachment
  (included for reference).
• Signers — the people who sign.
• Signing methods — signers verify their identity and sign using an
  electronic ID (eID) such as MitID or BankID.
• Statuses — a case file progresses through a lifecycle (broadly: draft →
  pending → completed, and it can also be rejected, deleted, or later anonymised).
  Use the status to drive your own workflow.
• The signed result — once a case file is signed by all signers, Penneo produces the signed
  files.

Penneo Collect concepts

Penneo Collect is built around forms and the submissions they produce. All Penneo Collect submissions are signed.

• Form — a configurable online form that defines the data and documents you
  want to collect. You create a form, then publish it to make it available to
  respondents.
• Submission — the data and files a respondent provides when they complete a
  form. Every submission is signed as part of the flow, so a completed submission results in signed file(s).

Where to go next

• Set up access in the Authentication section.
• Decide your approach in Choosing the right product.