Do I need an account?

No. Creating a gate gives you a private link. That link is the only key to its dashboard, so keep it.

Can it test a webhook?

Yes. Point the webhook at the gate address: every delivery is checked against your contract and appears in the journal with the reason for any refusal.

Which content types are accepted?

JSON (an object or an array of objects) and CSV. The format is read from the Content-Type header, or guessed from the first character.

Can I share the contract with the other team?

Yes. Each gate has a public, read-only page for its contract, and the same contract as JSON.

A validating endpoint between two systems

Create a gate, get an address, and send messages through it. Each call is checked against your contract and answered at once: accepted, or refused with the exact reason. Every exchange is kept in a journal.

Loading the tool…

What the caller gets back

The answer comes in the same call, so the sending system can act on it: retry, alert someone, or show the reason to a user.

HTTP 200
{
  "accepted": true,
  "version": 3,
  "records": 1,
  "target": { "simulated": true, "status": 201, "body": { "id": "rcv_4f1c9a02b7e3", "stored": 1 } }
}

HTTP 422
{
  "accepted": false,
  "version": 3,
  "records": 2,
  "errorCount": 1,
  "errors": [
    { "row": 2, "path": "lines[1].label", "rule": "maxLength", "limit": 30, "actual": 50,
      "message": "\"lines[1].label\" has 50 characters, the maximum is 30" }
  ],
  "target": null
}

Versions without surprises

When the format has to change, edit the contract in the dashboard. Before you save, the gate lists the changes, marks the breaking ones, and replays the last accepted messages of its journal against the new version: “4 of the last 31 accepted messages would be refused”. You know who to warn before the change, not after.

Limits and privacy, plainly

The receiver behind the gate is simulated. Forwarding to a system of your own is not open on this public site.
A message is at most 64 KB. A gate accepts 120 messages per hour.
One call checks about 200 CSV rows of five columns. A larger message gets a partial answer that says how many records were checked: send big files in batches.
The journal keeps the last 100 messages for 7 days, and the first 8,000 characters of each.
A gate that receives nothing for 30 days is deleted.
Anyone who has the gate address can send to it. Only the private link opens the journal.
Do not send card numbers, health data or secrets: this is a testing tool.

Details are on the privacy page. To put a gate like this in front of a real system, see how it works.

Questions

Do I need an account?: No. Creating a gate gives you a private link. That link is the only key to its dashboard, so keep it.
Can it test a webhook?: Yes. Point the webhook at the gate address: every delivery is checked against your contract and appears in the journal with the reason for any refusal.
Which content types are accepted?: JSON (an object or an array of objects) and CSV. The format is read from the Content-Type header, or guessed from the first character.
Can I share the contract with the other team?: Yes. Each gate has a public, read-only page for its contract, and the same contract as JSON.