Release notes

Easier sign-in with the authenticator app, a verified mobile number as the last way in, and the guide inside your console.

New

• After the password, sign-in first asks for the code of your authenticator app, without sending an email; the emailed code is one click away, on the same page. It applies to every account.
• Verified mobile number: in your profile you enter your number and confirm it with the code we send you by SMS. From then on, if you can use neither the app nor email, the sign-in page can text you the code, with two minutes between one message and the next. Without a verified number the page gives the support address.
• Coming from Carbone or Docmosis? One call (POST /api/v1/compose/templates/convert) rewrites the tags of your Word templates into ours, lists those it could not convert and stores nothing: your JSON data stays the same. The guide has a page of its own, with a ready prompt for an AI agent.
• The console is in Italian too, all of it: it follows the language of your profile (Italian, or English if you choose it), and the sign-in page that of your browser.
• Sign a Word document from the console, without the API: you upload it already filled in, say who signs, the order, the copies, the expiry and the reminders, and Validate shows the cost before you send. It costs what a Document Fly flow costs. Where each person signs is decided by a tag in the Word file ({{ signature.A }}); without tags the signature goes at the end of the last page.
• The console's signature request from a PDF now also asks for the signing order, SMS code, watchers, expiry and reminders.
• Watchers: people who follow a request without signing it, each with their own level (everything, completion, none), in the API (settings.watchers, and signature.watchers in the flow) and in the console. With everything they hear about every step: sending, each signature, a decline, the expiry, a revocation, a delegation, an undelivered invitation and the completion.
• DoConure speaks English and Italian everywhere: the site, sign-up, sign-in, the guide, the legal documents, the release notes, the emails and the text messages. Before you sign in your browser's language decides (English if it states none) or the flag at the top right; after, your profile's. The English site is at doconure.com, the Italian one at doconure.com/it/.
• Each organisation has a language, changed from its settings: it is the language of billing emails and alerts, and its signers' when a request names no other. In the API the language can be given for the whole envelope (settings.language) or for each signer (signers.X.language).
• The legal documents are published in English too; where the two differ, the Italian text prevails.
• A signer can sign by uploading an image of their handwritten signature (PNG or JPEG): we clean it and place it on the document like a drawn signature. The organisation can refuse it, from its settings.
• The same person can sign in several places of one document: signers with the same email are one person, who gets one invitation, signs once for all their places and is charged as one signature. Name, phone, verification, language and turn must agree, or the request is refused naming the field that differs.
• A signer whose tags are all inside a false condition ({% if %}) is left off the envelope and receives nothing: the answer says so (SIGNER_NOT_ON_ENVELOPE). If no signer is left the request is refused and the signature is not charged.

Improvements

• ccNotifyOn and bccNotifyOn "everything" now mean every step, as for watchers: besides sending, reminders and completion, also each signature, decline, expiry, revocation, delegation and undelivered invitation.
• The guide's error page explains every code in Italian too; the API's answers stay in English.
• A malformed request names the first wrong field, and a flow with the envelope's data outside signature says where to move it. A test call warns, already in Validate, that the PDF carries the word TEST.
• A template with Carbone or Docmosis tags is converted from its page in the console, with one click.
• Mails carry at the bottom right, in small print, the line "Powered by DoConure (Limepeak)" with links to both sites; signing pages the same line, at the bottom.
• The signing page is simpler: the greeting at the top, then "Read the document" and "Sign the document" side by side; below, on its own, the way out for whoever does not want to sign. The verification code is asked for with a "Send" button and the box to enter it appears once the code has gone out; the preview of how the signature will be printed is in the last step, before confirming, and shows the signature chosen: the name typed, the one drawn or the image uploaded.
• The Italian site has its own domain, doconure.it; the old doconure.com/it/ addresses lead there.
• The API has its own address, https://api.doconure.com: use it for your integrations. The paths on app.doconure.com keep working.
• Whoever signs up can try bulk jobs straight away: the starter key accepts them and the welcome page shows two ready test calls, a single one and a bulk one, free as long as they remain test calls.
• The guide has examples in cURL, JavaScript, React, PHP, WordPress, Java, C#, Go and Ruby, a page for Make, Zapier and n8n without code, and a page that says what is available, what is coming and what is not there for now.
• Support's response time is in the FAQ. A permission missing from the key says which permission is needed and where to create it, and DocuSign's terms (such as clientUserId) get an answer that explains what to do.
• If you upload a template with Carbone or Docmosis tags, the upload and the validation warn you instead of producing a PDF with the tags printed as text.
• A non-existent API path answers ENDPOINT_NOT_FOUND with the path and where to find the right ones; a method that is not accepted answers METHOD_NOT_ALLOWED with the allowed methods. They used to answer DOCUMENT_NOT_FOUND and INTERNAL_ERROR, the latter marked as retryable.
• A body that is not JSON answers INVALID_JSON saying what to fix: the missing Content-Type header, or the quotes the Windows command prompt adds to cURL. The guide has the examples for Windows (a JSON file and PowerShell).
• The guide and your profile open inside your console, with your menu.
• The signup emails arrive in the language of the page, and the one with the API key opens with the welcome and suggests the authenticator app.
• Replying to a DoConure email now writes to our support.
• The example call in the guide and the console has an up-to-date date.

Fixes

• When registration is closed, the page explains why in Italian.
• The release notes show the date of the version in use instead of "next release".

A new price list, the detail of the credits in every answer, the "Sign now" button in the invitation and your organisation's time on the signed document too.

New

• Registration is open: a business or a professional signs up on their own, with no invitation, and the account is active at once, with the welcome credit.
• EarlyBird, the first annual plan: 1,200 signatures, 2,400 SMS and 5,000 documents a year for €899 VAT excluded, on sale from 1 November 2026 to 30 April 2027 and renewable at the same price until the end of 2030. You choose it from Plan & Billing, beside prepaid credit, which stays as it is.
• A more linear console: the menu is divided into Build (templates, API keys, webhooks), Activity (documents, signatures, flows, log) and Account; in Home a "Getting started" list takes you from the first call to choosing how to pay, and each step ticks itself when it is done.
• On a document's page: the curl command ready to paste to make the same call again (it reads the key from DOCONURE_API_KEY and never shows it) and, if it failed, the error code that leads straight to its row in the guide. In webhooks, when the next attempt comes.
• A new "API errors" page in the console, under Build: what your keys were refused in the last day, week or month, by code, key and operation, with a link to the explanation of each code. With no request data: only the counts.
• In Plan & Billing, beside each plan, what the same package would cost in prepaid credit at your rates: you see at once when the plan pays off.
• A queue for documents: when the platform is at its maximum, a call that asks for it (settings.queueIfBusy, or the Prefer: respond-async header) gets 202 and a job to follow instead of a refusal; the document is made as soon as there is room, the credit is held at the door and returned if it is not made within 15 minutes. Without the request the answer stays as always.
• Every answer reports in output.credits.items the detail of what it cost, item by item (document, signature, SMS, seal, timestamp), with quantity, credits and who paid it: the credit or your subscription. The total is output.credits.used.
• Annual subscriptions, when the price list shows one: signatures, SMS and documents to use within the year at a fixed price, before the credits. They can be cancelled at any time and stay active until expiry; you move to a larger plan whenever you like, paying the difference; in the last thirty days you confirm the plan or choose another. The renewal costs what the paid period cost. We write to you thirty days before expiry, for every choice and when the new period starts.
• A subscription's card: at every payment you can use the saved card ("ending 4242, expires 12/30") or add a new one, which for a plan replaces the saved one. From Billing you can delete it: the renewal switches off and we write to you that the plan will not renew and what happens next. If the card expires before the renewal we let you know. We do not keep the card: Revolut keeps it, we keep a token, the last four digits and the expiry.
• Cookies on the public site: a banner of our own, with no third-party services, with "Reject all" and "Accept all" on the same footing and preferences by purpose (necessary, statistics, advertising). The choice lasts six months and reopens from the "Manage cookies" link at the bottom of the page. Before a choice the site contacts no third-party service; without consent no measurement tool is loaded.
• Branding: a section of the console for coordinators, with three tabs. Brand (a PNG or JPEG logo, header, button and footer colours, footer text in both languages), Emails (the text of every email a signer receives, in Italian and in English: start from our text, insert the placeholders with a click, see the preview on a computer and on a phone, send yourself a test and restore the default text whenever you like) and Signing pages (logo, colours and a few lines of your own: introduction, after signing, after declining, link no longer valid). Everything is checked before saving, with the errors shown one by one: allowed placeholders, text only, anti-spam rules and colour contrast. The email with the code always stays ours.
• The invitation's introduction line and the reply-to address, already in the settings but not yet used, now work in the emails to signers.
• Whoever has a Pioneer plan with additional blocks can buy them from the console (Billing → Plan): the calls are added to the period as soon as the payment arrives.
• Validating a document (dry run) also says how many calls or units of your plan it would take and how many remain.
• The site has a page in English (doconure.com/en/) and a page for each product, Composer Fly, Signer Fly and Document Fly, in Italian and in English.

Improvements

• Faster Word and Excel documents: the conversion to PDF takes about 60% less time, with the same result.
• Under load the platform serves more documents at the same time and answers at once, with its code, those it cannot take.
• The console's Home shows what is new in the latest version and a "Report a problem" button: the report reaches support with your organisation, the version and the browser, and the form also asks what you expected and which document or request it is about.
• The email with the sign-in code no longer carries the code in the subject: you find it only in the text, so it does not appear in a preview, on a locked screen or in the mail list.
• Webhooks is now a tab of Environments, in the same menu entry: where we send the callbacks and what we have sent are on the same page. The old address still works.
• Settings no longer repeats Branding: logo, colours and email texts are only in the Branding entry of the menu.
• In the list of templates the main folder is called Root: templates outside any folder are there, and from there you create a new folder.
• The PDF uses free fonts, now many more of them: for Arial, Times New Roman, Courier New, Calibri and Cambria it has the same measurements as Word, so lines wrap at the same points. If a Word template uses a font the server does not have (Aptos, Verdana, Georgia...), the template's page says which font replaces it and what changes, and the guide explains which to use for an identical PDF.
• The line printed under each signature in the document ("Signed by …") and the date fields give your organisation's time and day, with the time zone shown, instead of UTC.
• The charts on the Home count hours and days in your organisation's time zone.
• The site and /llms.txt state the price list plainly, also for AI assistants that answer questions about prices.
• The emails about the life of the account (archiving, anonymisation, reactivation) state the day as your organisation lives it, even when the deadline falls close to midnight.
• The activity log shows, for every change, the previous value and the new one (never a password or a personal detail), and every day a timestamp from a third party attests the date of the log.
• The text of emails and SMS with a code is deleted after 7 days, that of invitations and signing notices 30 days after the request closes, that of other emails 30 days after sending; the record of the sending stays 12 months.
• In the console's Help, the reference for integrators is the public guide at /docs, the only one always up to date: the old address of the API reference page leads there.
• HTML templates become PDF in a separate service, one process per document, with no network access: with many requests at once a long HTML document is ready in a few seconds instead of minutes. The errors stay the same (CONVERSION_FAILED, CONVERSION_TIMEOUT).
• An Excel report with hundreds of repeated rows is prepared much faster: for 480 rows, a tenth of a second instead of several seconds, with the same PDF.
• Validate flags an HTML table that repeats rows from a list without table-layout: fixed: with the column widths fixed, a long table becomes a PDF about a quarter faster. The guide explains how (Lists and repeating rows).
• The guide publishes the API's versioning policy (Versions of the API): what /api/v1 promises, what never changes and how something is removed, never before six months and only in a new version. Calls on the old addresses (/api/v1/documents, /api/v1/templates, /api/v1/signatures) work as before and now say so in the Deprecation and Link headers, with the new address.
• In the console, in Webhooks, "Send all abandoned again" resends in one go every notification your server had not taken after all the attempts: the same events, oldest first, never the same one twice.
• In the guide, Example payloads: five ready payloads (invoice, quote, delivery note, monthly report, agreement), each with a template that reads it. In the console, a template's Test with JSON box fills with plausible example values and two rows for each list, and copies with Copy JSON.

Fixes

• The check of missing fields no longer flags a field written with internal capitals (customer.vatNumber) or a list inside a list (the products of each parcel): they were in the document but showed as missing, and with "error on missing fields" the call was refused.
• The invitation to sign shows the "Sign now" button: the link appeared as plain text, under a sentence that spoke of a button.
• A Word template with tables without inner borders no longer prints in the PDF lines between the cells that Word does not show: the PDF has the borders you see in Word.
• The boxes of a Word template (☐ and ☒) always print in the PDF: before, an unticked box could vanish and a ticked one land on top of the word beside it.
• An Excel template that repeats rows ({% row for ... %}) uploads again, from the API and the console: since 1.2 it was refused with TEMPLATE_FILE_REJECTED.
• The conversion of Word and Excel documents no longer stops after many requests: since 1.1, after a few dozen documents, it could answer CONVERSION_FAILED until the next restart.
• Under many simultaneous requests the service stays reachable: before, it could stop and answer 503 to everything until it was restarted. Now the requests in excess get a refusal with its code (SERVER_BUSY, TENANT_CONCURRENCY_LIMIT_REACHED) to retry.
• With the platform at its maximum, a request that cannot be served in time gets CONVERSION_TIMEOUT, to retry, instead of a 504 or 502 error with no code.
• The guide recommends a client timeout of at least 120 seconds (it said 60): under load a call may wait its turn, and the service always answers within 120 seconds.

Changes

• A new price list: composing a document costs 2 credits (€0.20, it was 5), a signature 10, so a document and a signature in one call 12 (€1.20). The qualified seal costs 2 credits and seal with timestamp 6.
• The qualified electronic seal and the qualified timestamp are now on sale for every organisation that is not a test one, and can also be paid with the welcome credit. The seal attests the origin and integrity of the file, not who signed; with the timestamp the file is PAdES B-LT.
• On a signature request, the seal and the timestamp are paid at sending, together with the signature, even though they are applied at completion. If the request is withdrawn, expires or is declined, or if the seal or the timestamp cannot be applied (also when the provider does not answer us), they are credited back at once to the credit they came from, and you find it in the activity log. The signature is not refunded.
• The welcome credit stays at 50 credits: with the new price list that is 25 documents.
• A single purchase of credit is at most €1,000 VAT excluded (it was €5,000); there is no limit on the number of purchases or on the credit you may hold.
• Registration is reserved for businesses and professionals with a VAT number.
• Updated legal documents: Terms and conditions (businesses and professionals only, qualified seal and timestamp, when credits come back), privacy notice, cookie policy, data processing agreement, list of sub-processors and subscription conditions. At the first sign-in to the console we ask you to accept the new Terms; API calls do not stop.
• If your organisation signed the service contract with us, that is what applies: the console does not ask you to accept the online Terms again. A purchase made online, instead, asks for them, because they apply to that purchase.
• With a plan counted in calls, signing a document composed in an earlier call does not count a second call: composing and signing is a single call, as in the flow.
• The data processing agreement commits us to notify you of a data breach within 48 hours; the cookie policy and the privacy notice say precisely to whom we send conversion events (none to Meta).
• When we refund purchased and unused credit, in the cases the contract provides for, the movement appears in the credit history with the number of the credit note.

Times in your time zone, signing emails with your brand, revoking and replacing signers.

New

• A single purchase of credit is at most €5,000 VAT excluded; for larger amounts make several purchases or contact us. The limit is also on the Limits page.
• A signer can be replaced also in a request still in draft: name, email and mobile number are corrected, without sending anything to anyone.
• Emails with your brand have a closing text in Italian and one in English: each email uses the one in the request's language, or the other if it is empty.
• Each organisation has its own locale, chosen from a list, which sets the time zone and the way date and time are written: the console, the emails, the certificate of completion and the exports show times in your organisation's time. We set it; write to us to change it.
• The emails signers receive can have your look: your logo, the colours of the header, the button and the footer and a closing text. You switch it on from Settings, in the Branding section; the verification code always stays ours.
• Whoever has signed can receive the signed copy by email: you decide, in Settings.
• A signer can be replaced by whoever sent the request (from the console or via the API): the fields and the place in the signing order pass to the new signer, the old link stops working and the certificate says who replaced whom.
• When a request is revoked or expires, the signers who had been invited receive a message saying so.
• Your system can be told when a signer is replaced: give a third address, callbackUrl.onEvent, and it receives the recipient.replaced event, signed and retried like the others. It is optional and separate from onSuccess and onError, which keep saying only how the request ended.
• GET /api/v1/callback-environments lists your organisation's callback environments (code, whether it is the default one, type of authentication and default paths), so your system knows which env it may name. Read only: no address, no secret.
• The button to withdraw a signature request is now called "Revoke" in the console; the API path stays /cancel.
• In the emails with your brand the line "DoConure by Limepeak" no longer appears: the footer is yours. The note that the message is automatic and the link to report abuse remain.
• The lists of signature requests (GET /api/v1/sign/envelopes) and of flows (GET /api/v1/flow) filter with ?kind=production or ?kind=test, as in the console: tests and production do not end up in the same list unless you ask.
• GET /api/v1/usage now reports every row of the Limits page: the largest size of an uploaded file (limits.assetBytes), the default and maximum duration of download links (limits.downloadLinks) and the days uploaded files are kept (limits.storedFilesDays).

Improvements

• Signing links that expired, were withdrawn or replaced say why, in the request's language, instead of "invalid link".
• Whoever passes the signature to another person on a request with an SMS code gives the new person's mobile number: the code no longer goes to the old number.
• The Billing page shows, read only, the VAT applied: rate, regime and invoice wording. If your regime is different you can still tell us.
• Suspending a user, changing their sign-in method or generating new recovery codes closes the sessions opened before.
• The guide explains how to write the message of a signature request (bold with **, line breaks, links) and how to write a template.
• The signing email and the reminder state the time and time zone at which the link stops working, not only the day.
• The console's tables sort by clicking their header, ascending or descending.
• Settings are grouped by theme, with an index at the top and Branding at the bottom; forms put the label on the left and the field on the right when there is room.
• The search is on the Help page; the Limits page has its columns aligned in every section; the Release notes entry opens in a new tab.
• The guide explains how to have the request reach again a signer who lost the email, without creating a new request and at no cost: the resend issues a new link and the old one stops working. The same answer is among the FAQ of the reserved area.
• The "Callback environments" page is now called "Environments" and also holds the default success and error paths of each environment.
• The profile, the API keys, a user's invitation and the organisation's name also put the label on the left and the field on the right, like Settings.
• The Limits page states when test calls refill in your organisation's time (for example 02:00 in Italy in summer) and how long is left.
• In the data export, signature_recipients.csv and bulk_items.csv have the is_test column and the README gives the production and test totals apart.
• The guide describes download links for what they are: signed, expiring (one hour unless you say otherwise), revocable and, if you wish, single use.
• The signing pages are designed for the phone too: larger buttons and boxes to tap, fields that do not make the page zoom on iPhone, no sideways scrolling.
• A template can be renamed from the console; its id does not change.
• The console works better on a phone: larger buttons and menu entries, 16 px fields, wide tables scroll within their box.
• A template's page also lists Word's checkboxes and no longer asks for the signature placeholders as data.
• The /verify page is in Italian and in English.
• The subject of each of our emails starts with "DoConure - ", so you recognise them at once in the inbox; signing emails with your brand keep your subject, without our name.
• In emails the button is centred, with the address underneath, and beside the DoConure name there is our pen, as on the site.
• Credit notices put the figure that matters in bold (the percentage left and how many documents you can still produce) and say "1 document" in the singular.

Fixes

• A signer asked for a verification code (by email or SMS) can sign again from the signing page: the code entered was lost on submitting and the page asked for it again.
• The upload limit is 25 MB everywhere: templates, files for bulk composition and verification of signed documents. The Limits page and GET /api/v1/usage report the real value (before they said 50 MB for templates).
• Audit log: the From/To filters and the CSV export use your organisation's time zone, with ISO 8601 times with the offset from UTC; the page states the time zone.
• The consumer's declaration at purchase refers to art. 8.7 of the Terms on credit refunds.
• In emails, a link at the end of a sentence no longer includes the final full stop.
• The integrators' guide in the console correctly describes deletion after 12 months and JSON Schema validation.
• The site's bar no longer wraps between 900 and 1180 px.
• You can also sign with JavaScript switched off, by typing your name.
• The page of an expired signing link is in the request's language.
• The console checks an uploaded template's file as the API does: a file that cannot work is refused at once, with the reason, instead of being saved.
• A file too large uploaded from the console shows a message in the console instead of an empty error page.
• Replacing a signer also works after the first signature: the new signer is invited when it is their turn; for a signer with an SMS code you give their number; an invalid address is refused.
• In the emails with your brand, the words of the closing text are no longer removed from the body of the message when they appear in it.

Changes

• Simpler VAT: Italian organisations pay 22%, those of any other country 0% (reverse charge in the EU), unless we set a VAT regime for the organisation after verification. The VIES check of the VAT number stays as documentation but does not change the amount.
• A body over 25 MB sent to /api/* or /verify.json gets the standard JSON error answer (PAYLOAD_TOO_LARGE, 1803) instead of a line of text.
• The API and webhooks keep always using UTC. The "Time zone" and "Date format" settings, which had no effect, are replaced by the locale.
• A purchase is always charged at your account's rate (22% for an Italian organisation). If a different VAT regime applies to you, you tell us from the Billing page: we check it and, if confirmed, set the regime and customer care can grant additional credit. You can no longer buy at zero VAT on a declaration alone.
• The two default callback addresses in Settings are gone: they are configured as paths on the default environment.

A single way to pay: every organisation is prepaid and spends the credit it has bought.

New

• API keys have an entry of their own in the console's menu, "API keys", and are no longer a section of Settings.
• A key's permissions are chosen one by one, with a box for each, instead of the list of preset profiles: the key has exactly what you ticked, and only what your account includes.
• Tests and production no longer mix in any number: console, lists, billing, export and GET /api/v1/usage count the real documents and show the tests apart ("1,240 documents · 37 tests"). Documents, signatures and flows can be filtered by All / Production / Test, and every test row has a red TEST badge.
• The counter of test calls is where you look for it: in the console's home ("17 / 20, resets in 5 h 12 min"), in GET /api/v1/usage (testItems) and in every answer of an isTest call (output.credits.testRemaining). The count resets every day at midnight UTC.
• A "Limits" page in the console's menu, under Reference: requests per minute, the largest sizes of template, data and file, pages per document, test calls per day and the duration of download links and uploaded files, as they apply today to your organisation.
• Questions and answers, grouped by topic (keys, tests, credit, signing, errors, limits): two or three lines each with a link to the page that says the rest. They are the same in the guide (/docs/faq) and on the console's Help page.
• A single search across the guide, answers and help, at the top of the console's menu and in the guide: it opens with / or Ctrl-K.
• Ready-to-copy examples in cURL, Python and JavaScript to compose a document, send it for signature or do both in one call, each with its test version (/docs/examples), and a page "How do I make a test call?".
• Scheduled maintenance: when we switch it on, API calls get the MAINTENANCE_MODE code (503, with Retry-After) and the pages show a notice, with nothing carried out or charged. Before starting we finish the bulk jobs already running: in those minutes a new bulk job is refused, the console shows the countdown and the API answers carry X-Maintenance-Pending.
• The signature is placed with a tag in the template, like any other field: {{ signature.A }} puts signer A's signature where the tag is (.name and .date for name and date). The template's tag leaves no trace in the PDF. Coordinates remain the alternative and, if you give them, prevail. A tag for a signer the request does not have, or, when the template uses tags, a signer with neither tag nor coordinates, is refused before composing or charging. In an uploaded PDF the tag written in the text is read if you ask for it with signatureTags: true, and stays in the file.
• Callback environments: a new "Callback environments" entry in the console's menu. For each environment you give the base address and how to authenticate at your system (Bearer token, an API key in a header or OAuth2 client credentials, as Salesforce wants); the call sends only callbackUrl.env and the paths. The HMAC signature stays on every callback.
• In Word templates a checkbox is ticked from the data: a true or false value with the same name as the box (the bookmark of a legacy checkbox, or the Tag of a content control) ticks or clears it; without a value it stays as in the template.

Improvements

• The guide pages that explain how to do something have as their title the question one asks ("How do I sign a document?", "How do I get an API key?").
• The signing page of a test request shows the document with the same red TEST band as the signed file: whoever signs sees at once that it is a test.
• A test PDF cannot be mistaken for a real document: a red band "TEST — NOT VALID — NO LEGAL VALUE" at the top of every page and the red word repeated across the page, also in the signed file.
• Every email of a test request opens with a red warning ("TEST — this document has no legal value", or in Italian), besides [TEST] in the subject: invitation, reminder, code, signing confirmation and copies.

Fixes

• Eleven pages of the guide showed an extra word after the title and lost their layout: now they read like the others.
• With many DOCX or XLSX conversions at the same time, a request waiting for its turn could time out with CONVERSION_TIMEOUT even though it would have been converted in time: now the conversion's time counts from when it starts.
• In a test signing request with several documents, those after the first had no TEST band: now every page of every document carries it, on screen and in the signed file.
• A new API key appeared in the page's address, and so stayed in the browser's history: now it appears only on the page that creates it, once.
• Credit movements are listed in the order they were recorded: with two charges at the same instant, the balance after each row could appear out of sequence in the console and in the export (the balance was correct all the same).

Changes

• An API key's name is required and cannot repeat among the active keys of the same organisation (upper and lower case count the same). The name of a revoked key can be reused.
• API keys are created only in the organisation's console: they are no longer issued by us and no longer appear when an organisation is created.
• Every organisation is prepaid: paying in arrears no longer exists and there is nothing left to choose. The monthly limit of documents no longer exists: what counts is the credit, and with the credit used up the call is refused with QUOTA_EXCEEDED, as already happened.
• In the answer of GET /api/v1/usage, thisMonth.documentsSucceeded and documentsFailed still count the tests together with the real documents: they are deprecated, will be removed in version 2.0, and are to be replaced by thisMonth.documents.production and .test.
• In the answer of GET /api/v1/usage the fields organisation.deliveryMode (always "prepaid") and limits.documentsPerMonth (always null) are deprecated and will be removed in version 2.0: they no longer serve to decide anything.
• The Terms and conditions move to version 1.5: art. 8.2 says the service is prepaid only.
• The limits are no longer on the billing page, which speaks only of credit: they are on the new "Limits" page. The "longest time of a generation" (300 seconds) no longer appears: it was not an enforced limit.
• In the answer of GET /api/v1/usage the field limits.timeoutSeconds is gone: it reported a limit of 300 seconds the service never enforced. Whoever read it can simply ignore it.

The first public version of Composer Fly, Signer Fly and Document Fly: documents from a template and your data, simple electronic signatures with the evidence kept, and both in a single call.

New

• Export your organisation's data yourself: a ZIP archive of CSV files with invoices, orders, credit movements, templates, requests, signing requests, users and API keys. Free, one request every 24 hours, ready in a few minutes and downloadable for 48 hours. Never a secret, a code or the content of a document.
• Report a bug or suggest an improvement from the console, with the version and the page attached automatically.
• The "Complaint" topic in the contact form, so that a complaint is read as one.
• These release notes.

Improvements

• A signing link already used now says "already signed" when reopened, instead of a generic error.
• Retrying a document-plus-signature call spends only what was missing: a document already delivered is never charged twice.
• Bulk jobs: if a bulk product is withdrawn from an organisation, new submissions and new retries are refused, but cancelling a running job always works and the export stays available.

Fixes

• A paid order could be closed as expired by a sweep run at the wrong moment: a closed order that already has its credit is now brought back to paid.
• A payment notification received twice no longer answers with an error and no longer writes a double audit row.

Changes

• SMS are switched off for every organisation until we switch them on for you: verification by email and signing with the link alone do not change.
• The qualified electronic seal and the qualified timestamp are shown as coming everywhere, and asking for them gives a clear refusal, with no charge.
• The services run with a read-only file system and tighter resource limits.
• The data processing agreement (DPA) moves to version 1.3: requests from authorities, return of the data and certification of deletion, times to forward data subjects' requests, contacts, and a new annex that says what remains of every composed document.