6

I am using Watson Conversation services on Bluemix. We have multiple Conversation workspaces within the service to enable better segmentation of the problem space.

I need to load information on the set of available workspaces within the Conversation service (e.g. name, workspace ID) to allow me to target the appropriate Conversation API endpoint. I've been trying to find a Watson or Bluemix API to allow me to retrieve the information directly but have not had any success.

Does anyone know if it is possible to retrieve this information programmatically and if there are any best practices for doing so?

AlanY
  • 63
  • 3
  • The API reference for the Watson Conversation service is available here ( https://www.ibm.com/watson/developercloud/conversation/api/v1/). However, I think that you are looking for additional information. – William 'Bill' Wentworth Sep 20 '16 at 19:08

2 Answers2

6

We don't have an exposed endpoint for this capability at this point. It is something being discussed internally, however.

Collin
  • 76
  • 3
  • Collin, it sounds like you are perhaps on one of the Watson or Bluemix teams? If so, can you please edit your question to state this (and which group you're with)? Authoritative answers from the source are always much appreciated. – brichins Sep 20 '16 at 20:16
  • Thanks for the information, @Collin. I'll fallback to another method until an appropriate endpoint becomes available. – AlanY Sep 21 '16 at 06:56
  • This is a greatly needed functionality. Right now, the only alternative seems to be hard-coding the list of available workspace ids on the client side... – Nicolas Miari Sep 26 '16 at 02:41
3

The API for managing Conversation workspaces is now available. It is possible to list workspaces, to create/update/delete a workspace and to download an entire workspace. The API is supported by the Watson SDKs.

Using the new API, I wrote a small tool for managing Conversation workspaces. The tool shows the API in action. The source is available on GitHub to demonstrate how the API can be of use.

data_henrik
  • 16,724
  • 2
  • 28
  • 49