@brandon_mcclure curious if you’ve seen any differences between the TAP url_decode API and our decode plugin that uses regex? I wasn’t aware that they had an endpoint for this.
Thanks Holly. Getting errors, looks like an API call via Python script plugin will be where to go from here. This URL is one where google.com contains another URL, useful for evading controls.
Are you getting errors in configuring the step, or when the step runs? If you have an example of the error, we can take a look and see if it’s a bug we need to fix on our side.
I do where they only put a single slash after the protocol, the regex left it like that when the API call put it back in (I have an Advanced Regex after to add this just in case).
But also, the API includes the TAP cluster, message GUID, and intended recipient which is nice information to have.
I found the HTTP (formerly REST) Plugin works fine.
Connection uses https://tap-api-v2.proofpoint.com and the header info.
Then Step has the Route of /v2/url/decode and body as {"urls":[]}
for the v2/campaign/ids endpoint you have to both use basic auth creds AND service app auth?? The POST endpoints work just fine using only basic auth…