@bijection/connectors/storecove entrypoint to declare Storecove (Peppol) resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Peppol submissions and events
submissions: Submissions with pulled events
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:storecove/peppol/submissions/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: storecove. Keep credential material in the private credential inventory.
Inspect the complete configuration contract below for settings and conditional requirements.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Compiled declaration examples and configuration details are published in the connector reference. Peppol is reached through Storecove’s certified access point; Bijection runs no access point. Install the API key as astorecove credential
(storecove.credential(name)); the API origin is fixed. Configure the
Storecove webhook in pull mode.
- Submission.
submitDocument({ legal_entity_id, receiver_scheme, receiver_id, document, syntax })posts the base64 UBL or CII document once, with the operation identity asidempotencyGuid(32 hex digits). A 200 settlespending: Storecove accepted it, nothing more. 401, 403 and 422 refuse it. Anything else, or no reply, is unknown and is never resent: Storecove states no retention foridempotencyGuidand no read addressed by it. - Corner 3 receipt. A pending submission settles
confirmedonly when its sending evidence (the receiving access point’s AS4 receipt) answers 200, read by the GUID the submission’s own response named. A lost reply has no GUID, so no read is made and it stays unknown. - Corner 4 statuses. Invoice Response statuses (
acknowledged,accepted,rejected,paidand the others) arrive only aseventsrows, never as a command outcome. An event row keeps Storecove’sbodystring verbatim; the event type, the submission GUID, the echoedidempotencyGuidand the buyer status inside it are product meaning, and an echoedidempotencyGuidis how a product recognizes that an unknown submission was accepted after all. - Queue release. The queue shows one event at a time and keeps it until it is deleted. The host deletes each event after the page that retains it is published (release after custody); a lost deletion is sent again when the head is read again, and a 404 is an event already deleted.
idempotencyGuid without hyphens is accepted; what sending
evidence answers before delivery. Push-mode webhooks are not offered: the
documentation read does not state the pushed body’s shape.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.