Technical Reference

papiNet outbound API hub

One place your applications use to call trading partners' papiNet APIs: endpoints, credentials and limits live in Archr.Hermod, not in every application.

The outbound hub is the other direction. When one of your applications needs to read a trading partner's delivery note, or to push a goods receipt to a partner's endpoint, it does not talk to the partner. It puts a request message on the queue that names the API partner and the operation. Archr.Hermod does the rest and puts the reply back on the queue.

Your application never holds a partner's URL or a partner's credentials, and it does not need a route to the internet. Adding, moving or stopping a partner is an administrator's task in the Admin pages, not a release.

What Archr.Hermod checks before it calls

For each request, in this order:

  1. the API partner exists and is switched on;
  2. the papiNet version is live;
  3. the operation exists, and is one this partner is permitted to be asked;
  4. the partner has a current endpoint for its environment (test or production);
  5. the address is https, unless that partner is explicitly allowed otherwise;
  6. the parameters and the body comply with the papiNet document.

Only then does Archr.Hermod read the partner's key, make the call, and reply with an outcome: delivered, refused, unavailable, timeout or failed.

Safe by construction

← Back to the technical reference