Skip to main content

Welcome to Krebit Sign

Krebit Sign is a multi-tenant digital signing platform that lets your product automate document reviews, approvals, and legally binding signatures. Every tenant lives on its own subdomain (https://{organization}.krebit.se), giving you dedicated signing environments for production, staging, and customer-specific deployments.

Use this documentation to understand the platform, authenticate securely, and work with the OpenAPI-powered reference that describes every REST endpoint. The generated reference already exposes full request/response schemas—this guide focuses on connecting the dots so your team can ship reliable signing workflows.

Platform highlights​

  • Draft-to-completion lifecycle – Assemble signing packages, edit them while in draft, and dispatch once documents and recipients are ready.
  • Flexible authentication – OAuth 2.0 access tokens protect all API traffic. Choose the client credentials flow for server-to-server integrations or Authorization Code for delegated access.
  • Document and signer management – Upload compliant PDFs, add recipients with ordering and identification rules, send reminders, and download sealed copies when complete.
  • Operational safety – Cancellation, expiry windows, and automatic notifications ensure signers always receive the latest status.

How the docs are organized​

These docs combine conceptual guides with a generated API reference:

  • Getting started – Authentication, hands-on walkthroughs, and AI prompts to help you send your first signing package.
  • Guides – Deep dives into managing signings, users, and webhooks with best practices for production.
  • API reference – The OpenAPI integration exposes every endpoint with request/response schemas, code samples, and filter descriptions.

You will also find callouts for operational rules (such as the 14-day reminder window) and troubleshooting guidance based on common support questions.

Before you begin​

  1. Set up your tenant – Confirm your Krebit Sign organization domain (for example, yourco.krebit.se) and create any sandbox environments you plan to use.
  2. Provision OAuth credentials – Create an app at https://{organization}.krebit.se/developer/my-apps to obtain a client_id and client_secret. Secrets are shown only once—store them securely.
  3. Decide on an integration pattern – Krebit Sign works well for back-office tooling, server-to-server automation, and customer portals. Pick the authentication flow that matches your use case.
  4. Review PDF requirements – Uploads must be PDFs no larger than 10 MB, without passwords, annotations, or existing signatures.

Next steps​

  • Follow the Quickstart to create, populate, and send your first signing package.
  • Configure Authentication and verify access with GET /api/1.0/me.
  • Explore the guides for Signings, Users, and Webhooks to learn how the pieces fit together.
  • Browse the generated API reference from the sidebar whenever you need exact parameter and schema definitions.

Ready to dive in? Head to the Quickstart and start automating signatures with confidence.