Skip to main content
Electronic signature · Scrive and Odoo

Scrive Odoo Integration: E-Signing Without Leaving the ERP

Scrive's own integrations directory does not list Odoo. What a Scrive connector for Odoo does: which records go out for signature, how it connects to Scrive since version 2.1.0, which Document API endpoints it calls, how BankID and MitID map onto the eIDAS levels, and what has been tested so far.

Scrive Connector for Odoo — send, track and archive e-signatures without leaving Odoo

If you run Scrive and you run Odoo, Scrive will not point you to an Odoo integration. Its own integrations directory names dozens of systems, among them Salesforce, HubSpot, Dynamics 365, Teamtailor, SD Worx, Zapier, Make and Microsoft Teams, and Odoo is not one of them; what it offers instead is a form to request one. Search for a Scrive Odoo integration and you mostly get generic Odoo-integration pages from consultancies and automation platforms. Here is the answer written down: what a Scrive connector for Odoo does, endpoint by endpoint, and what it does not do yet.

Who is writing this. FlexigoTech is an official Scrive System Partner (Scrive AB, Sweden), see our partners page. We built the connector described below and we maintain it. It is published on the Odoo App Store for Odoo 17, 18, 19 and 20, at version 2.1.0. Where something has only been tested against a simulator and not against a real Scrive account, this article says so, and one section below covers exactly that.

Scrive integrates with dozens of systems. Why not Odoo?

Nothing technical is in the way: Scrive publishes a Document API v2 and a separate OAuth2 service, both ordinary REST over HTTPS. Everything below is built on those two. Why the directory has no Odoo entry is a commercial question and not ours to answer; what we can answer is what building it takes.

It also takes one branch per Odoo version, and that gets its own section below. A module written for Odoo 19 does not install on Odoo 17, so whoever builds the connector maintains four branches, for Odoo 17, 18, 19 and 20. Odoo Enterprise does ship a native Sign app, and for internal acknowledgements it is enough, but it does not talk to BankID, MitID or the Finnish Trust Network, and it does not produce a sealed evidence package from a provider your compliance officer already accepts.

Which Odoo document actually goes out for signature

The connector adds no separate signature silo to feed by hand. It adds a mixin to the records that already carry the content worth signing, so the send button lives on the record itself. Since version 2.0 they all come in one module. Purchase orders, employment documents, delivery notes and project tasks get the button when those Odoo apps are installed; the connector never installs them:

  • Quotations and sales orders (sale.order), signed before they become confirmed orders.
  • Invoices and other journal entries (account.move).
  • Purchase orders (purchase.order) — the supplier side of the same problem.
  • Employment documents: hr.version on Odoo 19 and 20, hr.contract on 18 and 17.
  • Delivery notes (stock.picking) — proof of delivery signed where it happens.
  • Work acceptance on project tasks (project.task), on plain Community Project rather than the Enterprise-only Field Service app.

From any of those, a wizard opens with the PDF Odoo already knows how to print, the parties pre-filled from the record's partner, the signing order, the document language and, per party, the authentication method. Parties can carry extra fields the signer must complete — checkbox, radio group or free text, the three Scrive's API supports. There is no native date type, and a radio group caps at eight options.

Connecting to Scrive: OAuth2 only since version 2.1.0

This is where these projects get stuck. Versions before 2.1.0 had more than one way in. The simplest asked for your Scrive login once, fetched a set of personal API credentials from Scrive and kept them in FlexigoTech Cloud (the earliest versions kept them in Odoo). Version 2.1.0, published for Odoo 17, 18, 19 and 20, removed that path: the connector now connects to Scrive with OAuth2 only, on Scrive's own login page.

Before connecting, an administrator turns on the FlexigoTech Cloud trial or subscription and accepts it on the Scrive account in Odoo. Then you ask Scrive for an OAuth2 client for the redirect URI that the account shows, enter the client ID and secret, and press “Connect with Scrive”. Scrive's login page opens, and you sign in there and grant access. Underneath it is an authorization code flow with a refresh token (scope doc:create doc:check doc:send offline_access) on Scrive's OAuth2 host, oauth2.scrive.com or oauth2.api-testbed.scrive.com for the testbed. The Document API lives on a different host, scrive.com or api-testbed.scrive.com.

Every request to Scrive goes through FlexigoTech Cloud, which keeps the OAuth2 authorization of your Scrive account and the client secret encrypted. Odoo keeps neither. Because you sign in on Scrive's own page, your Scrive login never passes through Odoo or FlexigoTech.

The catch is the redirect URI. Each Odoo database has its own address, so each one needs its own OAuth2 client from Scrive, registered for the redirect URI its account shows. A one-click connection through FlexigoTech's own app would remove that step, but it is not available yet: Scrive has to register that app first.

If you used the connector before 2.1.0 with those personal credentials, the update disconnects the account and deletes them. Documents and signed PDFs stay in Odoo, and the account form shows a notice that says what happened. Connect the account again with OAuth2 as described above. If an earlier version saved an OAuth2 client in Odoo, that client is paused until an administrator moves it to FlexigoTech Cloud.

The API surface the connector actually uses

These are the Document API v2 endpoints it calls, always through FlexigoTech Cloud:

StageEndpointsWhat it does
Preparedocuments/new · {id}/setfile · {id}/update · newfromtemplate/{id} · {id}/setattachmentsCreates the Scrive document from the Odoo PDF and writes parties, fields, language and authentication methods — or starts from a Scrive template.
Send{id}/start · {id}/setautoreminderMoves the document to Pending and optionally arms Scrive's automatic reminder.
Follow{id}/get · documents/list · {id}/callbackReads state back; the list endpoint also imports documents created outside Odoo.
Correct in flight{id}/remind · prolong · restart · cancel · trash · forward · {signatory}/resend · changeemailandmobile · getqrcodeThe unglamorous half of e-signing: wrong address, deadline tomorrow, wrong person — all from the Odoo record.
Retrieve{id}/files/main/{filename} · {id}/files/zip/{filename}The sealed PDF, and the full evidence package as a ZIP.
Accountusagestats/daysReads the last 30 days of Scrive usage back into Odoo.

Two notes on how those calls are made. Every document carries two mandatory Scrive System Partner tags — a system partner name and an integration name — which is how Scrive attributes traffic to the partner that built the integration; both are constants in the code. And outbound requests do not follow redirects: any 3xx from an API host is rejected rather than chased.

What comes back, where it lands, and what the audit trail is

Two mechanisms bring state back, and having both is the point. Scrive calls a callback URL on your Odoo, scoped per account and protected by a rotatable token in the path. Because callbacks get lost, an hourly cron also polls anything still pending.

The Odoo record mirrors Scrive's lifecycle instead of flattening it to sent/signed: Draft, Preparation, Awaiting Start, Pending, Signed, Canceled, Timed Out, Rejected, Error and Saved as Template. “Timed Out” and “Rejected” are different conversations. Every callback is stored as its own row with the event id, the raw payload and whether it processed cleanly; duplicate deliveries are stopped by a unique database constraint. A daily cron prunes those rows after a configurable window, ninety days by default.

Once signed and sealed, the connector downloads the sealed PDF and attaches it to the Odoo record it came from, retrying the documented race where the sealed file is not ready the instant the callback fires. The full evidence package — sealed PDF, evidence log, attachments — is one button away as a ZIP. In a dispute it is Scrive's evidence log that carries weight. Odoo's chatter tells you who pressed send; it is not the audit trail.

Nordic specifics: BankID, MitID, and why “signed” means three things

Scrive's Document API separates authentication to view a document from authentication to sign it, and the two lists differ. Fifteen values let someone view: no eID at all, SMS PIN, Swedish and Norwegian BankID, Danish MitID and MitID Erhverv, the Finnish Trust Network, iDIN, Freja eID and OrgID, and document-based identity checks. Nineteen let someone sign. That list drops plain Norwegian BankID and plain Verimi, which Scrive accepts only for viewing, and adds six qualified options: Norwegian BankID (QES), itsme, Smart-ID, Verimi (QES) and Scrive's own qualified signature in two flavours.

That split is the whole eIDAS conversation in one data structure. Under Regulation (EU) 910/2014 a simple, an advanced and a qualified signature are three legal categories, and only the qualified one has, under Article 25(2), the equivalent legal effect of a handwritten signature across the EU. In Scrive's API that distinction is not a setting buried in an account — it is which value you put on the party. Norwegian BankID and Norwegian BankID (QES) are two different strings. For signing, Scrive only accepts the QES one; plain Norwegian BankID is for viewing. Our companion piece on SES, AES and QES in Odoo covers the legal side properly.

Two details the connector enforces rather than discovers the hard way. Swedish BankID needs the signer's personal number, so the connector refuses to send a BankID party without one rather than let the call fail on Scrive's side. And Scrive's nineteen document languages include Swedish, Norwegian, Danish, Finnish and Dutch; the connector maps the partner's Odoo locale onto that list — bokmål and nynorsk included — so the signing page opens in the signer's language.

Running the same connector on Odoo 17, 18, 19 and 20

“Supports Odoo 17 to 20” is not a line in a manifest; it is four branches that genuinely differ. Four examples, each enough on its own to stop a module installing on the wrong version:

What differsOdoo 19 and 20Odoo 18 and 17
Employment recordhr.versionhr.contract — same feature, different model, so the HR bridge is written separately on each branch
Security groupsres.groups.privilege groups the access rightsA plain res.groups with a module category; the 19 and 20 security file does not load at all
SQL constraintsmodels.Constraint class attributesThe older _sql_constraints list
List views<list>, on Odoo 18 as wellOdoo 17 still wants <tree>, and its validator insists any field used by a modifier is present in the view, even invisible

The only way to keep that honest is to run the tests on each version instead of assuming the port worked. Since version 2.0 everything is one module, and each branch carries more than 1,100 automated tests: 1,183 test functions on 17.0, 1,181 on 18.0, 1,178 on 19.0 and 1,180 on 20.0.

What has been tested, and against what

A green test suite is a claim about your own code, not about the other side's server. Here is the split:

StatusWhat that covers
Tested end to end against a simulatorThe OAuth2 connection with your own Scrive OAuth2 client, end to end, against a simulator built from Scrive's official API documentation.
Covered by the automated testsMore than 1,100 tests on each branch. They patch the HTTP client at the seam and replay payload shapes from the Document API v2 reference and the eID Hub OpenAPI specification. That proves the connector behaves correctly given those shapes. It does not prove Scrive returns those shapes for your account.
Still pendingThe test with a real Scrive account, and any test of version 2.1.0 against production scrive.com. The one-click connection through FlexigoTech's own app does not exist yet: Scrive has to register that app first.

Ask any e-signature connector for that same split, in writing. “Fully integrated” next to a mocked test suite is the claim worth checking.

Where this does not fit

  • You only sign internal acknowledgements and you are already on Odoo Enterprise. Its native Sign app is enough and costs nothing extra.
  • You are not already a Scrive customer. The connector is not a reason to become one — the eID coverage is, or it is not. Choose the provider first, then integrate.
  • Your documents are generated outside Odoo, in a policy administration or core banking platform. Signing from Odoo would then mean moving document generation into Odoo — a far bigger project than a connector.
  • You need a qualified signature in a country Scrive's sign-authentication list does not cover. Check that list against your jurisdictions before anyone writes code.
  • Your Odoo is a heavy fork. The connector assumes stock Odoo 17, 18, 19 or 20 models; budget for the fork, not for the connector.
  • Your Scrive account has no OAuth2 client and Scrive will not issue one. The connector only connects with OAuth2, so that conversation with Scrive comes first.

Useful links within FlexigoTech

An Odoo connector for your softwareHow we build and maintain Odoo integrations for technology partnersTechnology partnersIncluding our position as an official Scrive System PartnereIDAS in Odoo: SES, AES and QESWhat each signature level means in lawOdoo modulesThe published FlexigoTech catalogue

Scrive guides

Example: you sign with Scrive and your contracts live in folders, so what changes with Odoo?What the Send button of Scrive Connector does, step by stepScrive Connector: the credentials error that only an administrator can avoidScrive Connector and HR contracts: what changes between Odoo 17, 18, 19 and 20How to sign an Odoo quotation with Scrive, from start to finishThe Scrive Connector error: Only signed documents can be forwarded.Scrive Connector: «Odoo could not produce the PDF», when it appears and how to fix it

All Scrive guides

Frequently asked questions

Does Scrive have an official Odoo integration?

Not in Scrive's own integrations directory, which names dozens of systems and leaves Odoo out. FlexigoTech is an official Scrive System Partner and has built and maintains a Scrive connector for Odoo 17, 18, 19 and 20, published on the Odoo App Store for the four versions (version 2.1.0).

Which Odoo versions does the connector support?

Odoo 17, 18, 19 and 20, as four separate branches rather than one branch with version switches. Each branch carries more than 1,100 automated tests. The differences are real: the employment record is hr.version on 19 and 20 and hr.contract on 18 and 17, and security groups use res.groups.privilege only on 19 and 20.

How does the connector connect to Scrive?

Since version 2.1.0, only with OAuth2. You ask Scrive for an OAuth2 client for the redirect URI shown on the Scrive account in Odoo, enter its ID and secret and press “Connect with Scrive”, which opens Scrive's login page. FlexigoTech Cloud keeps the OAuth2 authorization and the client secret encrypted; Odoo keeps neither. An account that used the older personal credentials is disconnected by the update and has to be connected again this way; its documents and signed PDFs stay in Odoo.

Can I sign with Swedish BankID or Danish MitID from inside Odoo?

Yes, because those are values in Scrive's own Document API. The connector exposes Scrive's authentication-to-view list (fifteen methods, including Swedish BankID, Norwegian BankID, Danish MitID, MitID Erhverv, the Finnish Trust Network and iDIN) and its authentication-to-sign list (nineteen methods) as fields on each signing party.

Does a BankID signature count as a qualified signature under eIDAS?

Not automatically. Scrive's API treats Norwegian BankID and Norwegian BankID (QES) as two different values, and the qualified options exist only in the authentication-to-sign list. For signing, Norwegian BankID is therefore always the QES variant, and the eID you pick for each party decides the level.

What has been tested against Scrive so far?

The OAuth2 connection with your own client has been tested against a simulator built from Scrive's official API documentation; the test with a real Scrive account is still pending. The automated tests, more than 1,100 on each branch, replay payload shapes from Scrive's Document API v2 reference. With version 2.1.0, production scrive.com has not been exercised yet. In July 2026 an earlier version, connected with personal access credentials, passed a connection test against production scrive.com.

Using Scrive and Odoo?

Tell us which documents you sign, in which countries and at which eIDAS level, and we will tell you on the first call what the integration looks like and what it does not solve. Email comercial@flexigotech.com or call +34 616 809 504.