Hey there! I have a new integration, and can see in Pactflow that my consumer and provider integration are added (albeit unverified, since only the new consumer pact has been uploaded to Pactflow so far). However, when I execute

/pacts/provider/:provider/for-verification

endpoint, it shows no pacts to verify. Does anyone know what could be causing this? I have verified the provider I'm passing in for

:provider

matches the actual provider shown in Pactflow:

I assume you have no branch or tags applied to the published consumer?

Sending JSON to ***/pacts/provider/auth-api/for-verification using POST: {"providerVersionTags":[],"includePendingStatus":true,"consumerVersionSelectors":[],"providerVersionBranch":"15696/merge"}

you have no consumer version selectors here, so currently you would be need to verify your pact by URL, provider verification tasks will traditionally pick up deployed or released consumers, plus those against the configured main branch (main/master if published will automatically set it as the main branch)

Ah, yep. That would make sense - thank you for reminding me of the thing that trips me up every time I onboard a new provider. 🙏

no enable pending stops the provider build from failing. it’s not a work in pending pact so including wip pacts doesn’t work as it’s not associated to a branch or tagged, i’d recommend reading the recommend guidance on publishing, pending pact/ and work in progress pacts in the docs