Feat: add peppyrus integrator#15
Merged
pritambiswal merged 5 commits intoJun 20, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new Peppyrus integrator option and implementation for sending and polling PEPPOL documents via the Peppyrus API.
Changes:
- Introduce a new
PeppyrusAPIClientplus helper functions to transmit invoices and poll the inbox. - Add “Peppyrus” as a selectable integrator in integration settings.
- Extend existing transmit/poll entry points to route to the Peppyrus implementation.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| edocument_integration/peppyrus_api.py | New Peppyrus API client + transmit/poll helpers. |
| edocument_integration/edocument_integration/doctype/edocument_integration_settings/edocument_integration_settings.py | Allows “Peppyrus” and routes polling to Peppyrus. |
| edocument_integration/edocument_integration/doctype/edocument_integration_settings/edocument_integration_settings.json | Adds “Peppyrus” to the integrator Select options. |
| edocument_integration/api.py | Routes transmit + polling API to Peppyrus when selected. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+105
to
+107
| error_msg = f"Peppyrus API error ({response.status_code}): {error_text}" | ||
| frappe.log_error(f"{error_msg}\nRequest Payload: {json.dumps(payload)}", "Peppyrus API Error") | ||
| raise Exception(error_msg) |
Contributor
|
@i1mercep I will check this and get back this week. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have been looking for a free Peppol API and found Peppyrus. Please add the support
This pull request adds support for the Peppyrus integrator to the EDocument integration system, allowing users to transmit and poll electronic invoices via the Peppyrus PEPPOL API. The changes include updates to configuration options, type annotations, and integration logic, as well as the introduction of a new API client module for Peppyrus.
Peppyrus Integrator Support
peppyrus_api.pymodule implementing the Peppyrus PEPPOL API client, including methods for sending documents, polling the inbox, and validating the connection.edocument_integratorfield in the integration settings JSON and type annotations to include "Peppyrus" as a selectable option. [1] [2]Integration Logic Enhancements
edocument_integration/api.py) to support transmitting and polling invoices using the Peppyrus integrator, alongside existing support for Recommand. [1] [2]poll_incoming_documentsmethod in the integration settings DocType to handle Peppyrus as a valid integrator, importing and using the new Peppyrus polling logic.