According to the Api reference, a Conversation Service is the top-level container for other resources in the Twilio Conversations REST API and can be used to create multiple, distinct environments (such as dev, stage, and prod) under a single Twilio account.
I've set multiples Conversations Services, but whenever I create Conversation on the backend it is aways created under the default Conversation Service set in the configurations.
Is there a way to provide the Conversation Service Sid somewhere in the api so that I could scope my resources fetch/create under that Conversation Service?
Issue Summary
According to the Api reference, a Conversation Service is the top-level container for other resources in the Twilio Conversations REST API and can be used to create multiple, distinct environments (such as dev, stage, and prod) under a single Twilio account. I've set multiples Conversations Services, but whenever I create Conversation on the backend it is aways created under the default Conversation Service set in the configurations.
Is there a way to provide the Conversation Service Sid somewhere in the api so that I could scope my resources fetch/create under that Conversation Service?