Postman Echo

• Send a test requestSend a request to Postman Echo and get back exactly what it received: the query values, the headers and the data, as they arrived. The step to point a half-built workflow at when you need to see what it is really sending before you send it anywhere that matters. No account or API key required.
• Test a response codeAsk Postman Echo to answer with one particular response code, so you can see what the rest of your workflow does about it. Pick a success code and the step succeeds. Pick an error code and the step fails with that error - which is the point: it is the only way to watch a retry, a fallback or an alert path actually run. No account or API key required.
• Test a slow responseAsk Postman Echo to take a few seconds before it answers, so you can see how your workflow handles a service that has gone slow rather than gone down. Waits up to ten seconds, which is as long as the service will hold a request. No account or API key required.
• Test response headersAsk Postman Echo to send back headers of your choosing, and see which of them survived the trip. The way to check that a header a workflow depends on reading - a rate-limit count, a request id, a signature - really does come back. No account or API key required.
• Test a username and passwordSend a username and password the standard way and see whether the server accepted them. Postman Echo accepts one published test pair and rejects everything else, so this proves the credentials your workflow builds leave it intact and arrive readable. Being rejected is reported, not treated as a failure, so a workflow can branch on it. No account or API key required.
• Get your outbound IP addressFind out which public address your workflows call out from. This is the address another service sees, and the one to put on its allow-list when it only accepts calls from addresses you have named. No account or API key required.

No actions match that.