Integration & interfaces
See what comes in, validated and profiled.
Systems send each other messages all day long, and when something goes wrong you rarely get to see the message itself. This is where they arrive: every message kept, checked against what you expect, and personal data covered up before anyone reads it.
Every message that arrives is kept exactly as it came in, so you can look at what a sender actually sent instead of what it says it sent.
Each message is measured against what you expect: a field that is missing, empty or the wrong shape shows up here, not weeks later in another system.
Mark a field as personal and its content is hidden everywhere it could be read — on screen, in a download and in a report — while the checks still run on the real value.
What people use it for
Point the sending system here during testing. You see what it actually sends, not what its documentation claims, and the profiler shows which fields come in empty, inconsistent or not at all — while there is still time to fix it.
Let a sender post here as well as to the real endpoint. When something goes wrong you have the message itself instead of a log line about it, and enough history to show when the sender changed.
Give the name of your team and sign in on the next screen. You see the endpoints of the teams you are in; what you may change there follows from your role.
Want an endpoint of your own, or a team for your organisation? Not sure whether this fits what you are building, or is something not arriving the way you expect? Ask the administrator of this site.
If it is about one endpoint, send its key along — but never the messages themselves, because those may hold personal data.