Hello, I am building out a POC and I using provider states to set up my data. I am trying to setup up my api to work with provider states. I am a bit confused by the direction here.

you will need to create a dev/test only HTTP endpoint that accepts a JSON document that looks like:

```{

"consumer": "CONSUMER_NAME",

"state": "PROVIDER_STATE"

}```

The following flag is required when running the CLI:

•

--provider-states-setup-url

- the full url of the endpoint which sets the active consumer and provider state.

Does my test only endpoint need to access a body in the request that I can pass in

CONSUMER_NAME

and

PROVIDER_STATE

or is the url just supposed to pass up those values as parameters in order to pass along w/

--provider-states-setup-url

? Once I correctly parse the consumer and state, what do I need to do in my controller to properly load the provider state? Thank you in advance for any and all assistance.

If you’re using pure ruby @Kellie Persson then you don’t need to make an endpoint.

The issue is we will be using pact-broker

I think you’re misunderstanding that the pact broker does.

i have been able to verify already from the provider side but that’s just because i am testing it out locally

the pact broker is not involved with the replaying part of the interactions.

Okay. I am using pact-swift for my consumer tests (generate the pacts). I would like to be able to verify from the consumer end but for that I do need to access the test api for the provider state

there are two ways to do verification for ruby. If you’re ok using the version 2 of the specification (fewere features) then you can just use pure ruby as per the link I sent above.

Awesome. Thanks so much Beth. I have been able to verify using version 2 of the specification. Wanted to see if we would be able to support the higher version of the specification. Will go through the tutorial! Thanks again.