For 3rd party tests, because they won’t be able verify your contracts, Pact style tests will only add a little value (see our AMA on the subject: https://docs.pact.io/help/amas#join-an-upcoming-ask-me-anything-ama-session) For 3rd party tests, there are a couple of options; 1. If they are untrusted, you could use record/replay style tests, but this gets hard because you need to be able to handle state. Essentially, you’d be building an approval based workflow, where tests are run on a regular basis and any failed tests need to be manually reviewed/approved. This will require more upkeep, but might be helpful in situations where the 3rd party is unreliable 2. You could use a static style check, where you compare your consumer usage to a defined spec given from the provider. This type of testing assumes the 3rd party is likely to be competent (as would be the case with Zendesk). You might find that https://docs.pactflow.io/docs/bi-directional-contract-testing/ could work for you, in this case (note it’s not an OSS feature)