# Electronic signature triggered from your own system. > Public API and open-source libraries The program you already use can send a document for signature and collect the finished file on its own - without logging into our application and without copying documents around. API access carries no fee of its own, and for testing you get free sandboxes kept apart from production. Canonical page: https://autosignly.eu/en/api Language: en ## Your system sends the document. We handle the rest. The program you already use - a CRM, an HR system, a customer portal, a spreadsheet with a macro - can send a document for signature and collect the finished file on its own. **Nobody has to log into our application or copy files around.** ### The system hands over the document Your program sends a PDF and the list of people who are to sign it - first name, last name, e-mail, country. With several signers you also give the order. ### People sign where they are Each person receives a link by e-mail and signs on their own phone or computer. The next one gets their link only once the previous person has finished. ### Your system knows straight away When the document is signed, we send a notification to your program together with the finished file. Nobody has to watch for it or check a mailbox. ## Ready-made libraries for the three most popular languages. Your developer does not start from scratch and does not have to translate our documentation into code. For Java, Node.js and Python we ship ready-made libraries - a few lines and the integration works. **All three are generated from one shared specification** , so they behave identically and never drift apart between languages. The code is public under the Apache-2.0 licence. Your team or your auditor can read it before the rollout, and you are not dependent on us alone at this point. ### Java Java 17 or newer. The only transitive dependency you inherit is Jackson. ### Node.js Node 20 or newer. No dependencies - it uses what Node already has inside. ### Python Python 3.10 or newer. One command, like any other package. We do not print version numbers here, because they change more often than this page - you will find the current one in your language's package registry or on GitHub. The packages are public and need no account with us; an account is needed only to generate an access key. ## The integration can be tested on your own computer. To check whether notifications from an outside service arrive where they should, you normally have to expose a company machine to the internet. IT departments dislike such requests, and rightly so. So we ship a small tool that **intercepts the traffic meant for your system and forwards it to the developer's machine** . Nothing has to be open to the world; you set up no tunnel and no firewall rule. Notifications arrive untouched, together with the signature we secure them with. **What works on the developer's desk works the same way in production** - there is no "tests only" mode here. On sign-in the tool prints which company and which environment the key leads to, and warns you clearly when you have reached production. Production and test credentials can sit side by side without any risk of a mix-up. ## Five free sandboxes alongside production. A sandbox is a separate, complete test environment - with its own data and its own access key. Thanks to that nobody learning the integration will send a real document to a real client by mistake. **You can have up to five sandboxes** , for example one per team or one per attempt at the rollout. The address is the same for tests and for production - the key you use is what decides which environment you are working in. Moving from tests to production therefore needs no rewriting of the integration. ### Everything in a sandbox is free of charge Signatures made in a sandbox carry no cryptography - we buy no qualified timestamp and no seal for them, so there is nothing to charge for. Test as much as you need and pay only for the documents signed in production. How a sandbox differs from production #### A signature with no legal weight A document from a sandbox gets a visual seal only, with no cryptography. It is there to check the flow, not to sign anything real. #### A watermark on documents Documents generated from templates in a sandbox carry a watermark, so that nobody mistakes a test copy for a binding one. #### No e-mails to signers In a sandbox we send no invitations by e-mail - your system collects the signing link. Tests never reach a real counterparty's mailbox. #### Data kept fully apart A sandbox key cannot see production documents, parties or tags. A sandbox can also be deleted together with everything in it. ## Frequently asked questions ### Do I have to pay extra for API access? No. API access, keys, webhooks and the client libraries carry no fee of their own - you pay exactly what you pay signing in the app: from 0,25 AC for a simple signature and 0,88 AC for a signature with SMS verification in Poland. There is no API plan, no entry threshold and no call package to buy separately. ### How many sandboxes can I have? Up to five alongside production, so six environments in total. You create each one under its own name and it gets its own access key. In practice that covers one per team, or a separate environment for automated tests. ### Are sandboxes free? Yes - every operation in a sandbox is free of charge. Signatures made in a sandbox carry no cryptography, so we buy no qualified timestamp or seal for them and there is nothing to charge for. Test as much as you need; you pay only for the documents signed in production. ### How does a sandbox differ from the production environment? The address is the same - the key you use decides the environment, so nothing has to be rewritten when you move to production. There are four differences: a sandbox signature has no legal weight (the seal is visual only, with no cryptography), documents generated from templates carry a watermark, signing invitations are not e-mailed (your system collects the link, so tests never reach a real counterparty), and the data is completely separate from production. The flow, the statuses and the webhooks are identical. ### Do I pay per user? The first user on an account is free; every additional one costs 5 AC per month. A user is someone at your company who sends documents and manages the workflow. Signers don't need an account - you pay for their signature, not for an account. ### What are AC credits? AC stands for AutoCoin - AutoSignly's internal currency used to pay for signatures and verifications. The conversion is simple: 1 AC = 1 PLN net. You top up your account with any amount you want - for example, topping up 100 AC gives you 100 credits to use in the system, and an invoice for 123 PLN (100 PLN net + 23% VAT). You use credits to pay for signatures, verifications, and add-on services - no subscription and no packages that expire at the end of the month.