Skip to main content

Peppol Technical Contact

This page is for other Peppol service providers: the access point or SMP operator that exchanges documents with GoRoute and needs to reach the technical team behind our access point, for example about a message that did not arrive, a receipt or error you did not expect, or a question about our endpoint or certificate. If you are a GoRoute customer, start from Support & Resources instead.

Who we are on the Peppol network​

OperatorGoRoute.ai (ClayDesk LLC)
Peppol seatPOP000991, the Common Name of our Peppol access point certificate
Service provider id0242:000991 (the OpenPeppol Service Provider Identification Scheme, from the seat)
AS4 endpointhttps://ap.goroute.ai/as4

Omani taxpayers we serve are published in the Oman Tax Authority's SMP, which may name another GoRoute endpoint; the way to reach us below is the same.

How to reach us​

Use the addresses published on Support & Resources:

AddressUse it for
support@goroute.aiEverything: the main way in, at every severity
engineering@goroute.aiP1 and P2 escalation only, when an issue has not moved

The hours are the ones on that page: P1 and P2 are covered 24/7/365 (a P1 is, for example, our access point unreachable on the network, AS4 delivery halted, or a compromised certificate); P3 and P4 Monday to Friday, 08:00-18:00 US Eastern (America/New_York). The severities, response times and escalation path are set out there too.

What to put in your message​

So we can find the exchange in our records at once, give us:

  1. The AS4 message id of the message in question, and of the receipt or error you got for it, if any.
  2. The SBDH instance identifier (DocumentIdentification/InstanceIdentifier in the Standard Business Document Header) of the document.
  3. Timestamps with their time zone: when the message was sent and when the problem showed. UTC is easiest.
  4. The participant ids on both sides, with their schemes: the sender and the receiver of the document, ours and yours, and your own service provider id or seat.
  5. What you saw: the error code or text, the HTTP status, or the step where the exchange stopped.

Please do not send us private keys, keystore passwords or any other secret. A certificate's subject, serial number or fingerprint is enough to identify it.

See also​

Last updated on