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:
- the API partner exists and is switched on;
- the papiNet version is live;
- the operation exists, and is one this partner is permitted to be asked;
- the partner has a current endpoint for its environment (test or production);
- the address is
https, unless that partner is explicitly allowed otherwise; - 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
- Network guard. No private, loopback or link-local address is called unless that partner is allowed it, and the check is made on the address the connection is actually made to. Redirects are not followed, and the destination always comes from the partner's endpoint, never from the message.
- Credentials stay in Archr.Hermod. A partner's key is write-only in the Admin pages: it is stored through Archr.Hermod's secret store, never shown again and never logged. API-key authentication is available now; OAuth 2 and mutual TLS are planned.
- Permitted operations. Which operations may be called at each partner is one list, with rules such as "all reads", and is enforced before anything leaves your network.
- Audit and metrics. One record for every request (partner, operation, version, outcome, status, time taken) and OpenTelemetry metrics by partner and outcome.
- A master switch. The hub is off until an administrator switches it on in Settings, and can be switched off again at once, with no restart.