Create a token in Pennylane
An administrator of the company in Pennylane opens Settings, section Connectivity, then Developers, and generates an API token. This path comes from the Pennylane documentation. The exact labels may vary between versions.
Name it Klepsi. If an expiry date is offered, note it.
Give it rights on customer invoices
Tick the customer invoices scope with read and write access: customer_invoices:all.
Klepsi needs nothing else.
What it does with it:
- read the invoices of the linked customers, to match them with the time entered;
- create an invoice as a draft when issuing. Finalizing it and sending it to the customer through Pennylane takes a separate click from an administrator.
The token is shown only once. Copy it and store it in your password vault.
Enter it in Klepsi
In Klepsi, open Settings, Accounting tab. Choose the Pennylane connector, then:
- Pennylane API token: the token you copied. Once saved, it is no longer displayed. Leave the field empty to keep it.
- API URL: keep the proposed value,
https://app.pennylane.com/api/external/v2.
Keep dry run on at first
The Dry run by default option is ticked from the start. The issue window then opens as a preview: Klepsi shows what it would do, and nothing is written in Pennylane without a second click.
Leave it ticked while you check your first invoices.
Save, then test
Click Save, then Test the connection. The test uses what is saved, not what is on screen. It asks Pennylane for a single customer invoice and changes nothing.
If something goes wrong
Error 401 (shown in French: "Pennylane a répondu 401"): the token is wrong, revoked or expired. Create a new one.
Error 403 ("Pennylane a répondu 403"): the token does not have the customer invoices scope.
Need help?
Our support team can walk you through the setup. Write to us at support@aleop.eu.