Skip to main content
This is the feature the tool exists for. You and your partner disagree about whose side is wrong. You have a report showing exactly which request was sent, what came back, and which clause of the specification it violates. You send them a link. The argument ends, or it moves on to something substantive.
Returns { "success": true, "data": { "shareToken": "..." } }. The report is then readable, with no authentication, by anyone holding the link that carries that token. Your partner does not need an account. They do not need to sign up, and they do not need to trust our verdict, because the link carries the evidence and not just the conclusion. Minting a link again replaces the previous token, so the old link stops resolving and the new one takes its place.

​
What your partner sees

The report, in full: the verdict, each check, the clause it tests, and the request and response that produced it. Nothing about your account travels with it. Credentials tokens are redacted from every captured exchange, including the Authorization header and the token field of an OCPI Credentials object, which a conformance run reads when it checks GET /credentials. They are scrubbed where the exchange is captured, before it is stored, so a report cannot carry one and a share link cannot leak one.
A shared report is public to anyone holding the token. That is the point, and it is also the caveat: treat the link like the URL of an unlisted document, because that is what it is. When the conversation is over, cut the link off: share the run again to replace the token (the old link stops resolving), or delete the run (DELETE /api/v1/testing/runs/:id), which kills the link immediately.

​
Why the evidence matters more than the verdict

An engineer who receives “your OCPI implementation failed conformance” from a vendor’s tool has every reason to be skeptical, and should be. An engineer who receives the exact POST that was sent, the 200 OK that came back where the spec requires 405, and the clause requiring it, has something they can act on in the next ten minutes. We built the report to be forwarded, which means it has to survive being read by someone who does not trust us. Delete the share token and the link stops working immediately:
Re-sharing afterwards mints a fresh token; the old link stays dead.