---
title: "Simulate routing result for conversation"
method: GET
path: "/ccaas/1/conversations/{conversationId}/simulate-routing"
tags: ["customer-engagement", "conversations", "conversation-management"]
---

# Simulate routing result for conversation

`GET /ccaas/1/conversations/{conversationId}/simulate-routing`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/ccaas/1/conversations/{conversationId}/simulate-routing`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Use this method to simulate routing for an existing conversation.
This method will resolve the routing rule applicable to the current conversation state and return the queue ID and priority
that would be applied if the conversation was actually routed at this moment.
Closed conversations cannot be routed.

## Path parameters

- `conversationId` string, required

## Response `200`

OK

- E89661b226e518f36a162935afcdf1132c95b0e63e9c86c5ef5f31c5a8d865a2ConversationRoutingResultApiResponse
  - `id` string: Conversation Id.
  - `queueId` string: Resolved queue Id.
  - `priority` 'URGENT' | 'HIGH' | 'NORMAL' | 'LOW': Conversation priority.

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)