> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/platform-api/workspaces/use-cases.md).

# Use Cases & Bindings

Bind a provisioned communication use case to a workspace service, inspect its routing, and remove the binding when routing should stop.

A use case identifies an approved channel setup and purpose. Concurrence provisions the channel resources and supplies the use-case identifier; the Platform API connects that use case to the service handling its conversations.

## Provisioning and Workspace Routing

Use-case creation, inventory, and deletion belong to managed channel provisioning and are not part of the public Platform API contract. The former Platform use-case list and explicit ownership endpoints have been removed. There is no separate ownership claim before binding: the service binding establishes the workspace linkage.

Complete the channel setup with Concurrence, then bind the supplied use-case identifier to a service in your workspace. Removing a binding stops that routing; it does not delete the upstream number, line, domain, or use case. See [Channel Manager](/developer-guide/platform-api/conversations/channel-manager.md) for channel availability.

## Service Binding

A use case can be bound to a platform service. A binding is unique per workspace for a given service and channel pair: only one use case may bind a given (service, channel) at a time.

### Bind a Service

Upserts a binding for the use case. Rebinding within the same workspace replaces the prior service. A binding in another workspace returns a conflict. A different use case cannot bind a service and channel pair that is already bound.

**Permission required:** Channel.create

{% openapi src="<https://api.platform.amigo.ai/v1/openapi.json>" path="/v1/{workspace\_id}/use-cases/{use\_case\_id}/service-binding" method="put" %}
<https://api.platform.amigo.ai/v1/openapi.json>
{% endopenapi %}

### Unbind a Service

Removes the use case binding from its service. Fails if no live binding exists for the use case.

**Permission required:** Channel.delete

{% openapi src="<https://api.platform.amigo.ai/v1/openapi.json>" path="/v1/{workspace\_id}/use-cases/{use\_case\_id}/service-binding" method="delete" %}
<https://api.platform.amigo.ai/v1/openapi.json>
{% endopenapi %}

### Get the Service Binding

Returns the current service binding for the use case. Fails if no binding exists for the use case.

**Permission required:** Channel.view

{% openapi src="<https://api.platform.amigo.ai/v1/openapi.json>" path="/v1/{workspace\_id}/use-cases/{use\_case\_id}/service-binding" method="get" %}
<https://api.platform.amigo.ai/v1/openapi.json>
{% endopenapi %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.concurrence.com/developer-guide/platform-api/workspaces/use-cases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.