I don't want to use Zap, but I'm being forced to use it by Salesforce. We have developed a "Managed Package" which we would like to release in the Salesforce App Exchange. The app calls our external API. Salesforce is insisting that we run Zap against the API. But I'm not sure that Zap is the right tool.
Normally I start a session by getting a JWT token:
Which gives me this JWT token:
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjoibGF3cmVuY2VAcHJpdmNvLmNvbSIsInVzZXJfaWQiOjQyMDAwLCJpYXQiOjE0OTM4NDAxNjcsImV4cCI6MTQ5Mzg2ODk2N30.RpqOBA8vWvDIBYS-cSz73O5H8Sslh0bFEOQ'
So now I can do a real query for business data:
curl --verbose -d '{ "revenue_upper_limit" : "1000000000", "revenue_lower_limit" : "1000000000", "emplyee_count_lower_limit" : "200", "employee_count_upper_limit" : "2000", "industry" : "transportation" , "api_pagination" : "4" }' -X POST "
https://api.example.com/v1/verbose/" --header "Content-Type: application/json" --header 'Accept: application/json' --header 'x-api-key: RSF82tPTTkxq3tfaIyTWXJPKJR9lcdwFKn' --header 'Authorization: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjoibGF3cmVuY2VAcHJpdmNvLmNvbSIsInVzZXJfaWQiOjQyMDAwLCJpYXQiOjE0OTM4NDAxNjcsImV4cCI6MTQ5Mzg2ODk2N30.RpqOBA8vWvDIBYS-cSz73O5H8Sslh0bFEOQ'
How do I recreate this in Zap? Where do I put in all of the HTTP headers, and how do I do POST?