> 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/integrations/review-queue.md).

# Review Queue

List the external write proposals stored in a workspace and record a review decision on one. A decision does not send a write to an external system.

The review queue operations list the external write proposals stored in a workspace and record a reviewer's decision on a proposal in `proposed` status. The platform does not stage new proposals, and a decision does not send a write to an external system. To change an external system during a conversation, use an [integration](/developer-guide/platform-api/integrations.md) and verify the result at the destination.

{% hint style="info" %}
**Separate from integration approvals.** An integration's `approval_policy` does not add to this queue; conversation-scoped integration calls use the endpoints documented in [Approval-Gated Integration Writes](/developer-guide/platform-api/integrations/approval-gated-integration-writes.md).
{% endhint %}

All endpoints are workspace-scoped and require authentication with an API key or session token that carries the matching ReviewQueue permission.

## Endpoints

### List external write proposals

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/external-write-proposals" method="get" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

Returns a paginated list of stored proposals, newest first, with each proposal's identifier and status.

**Permissions:** Requires `ReviewQueue:View`.

***

### Approve external write proposal

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/external-write-proposals/{proposal\_id}/approve" method="post" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

Records approval of a proposal in `proposed` status. The reviewer identity is derived from the authenticated session. Approval does not deliver the write.

**Error responses:**

| Status | Condition                                                                                     |
| ------ | --------------------------------------------------------------------------------------------- |
| `403`  | Caller has no authenticated user identity (e.g., an API key without a bound person identity). |
| `404`  | Proposal not found in this workspace.                                                         |
| `409`  | Proposal is no longer in `proposed` status.                                                   |

**Permissions:** Requires `ReviewQueue:Review`.

***

### Reject external write proposal

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/external-write-proposals/{proposal\_id}/reject" method="post" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

Records rejection of a proposal in `proposed` status. The reviewer identity is derived from the authenticated session.

**Error responses:**

| Status | Condition                                   |
| ------ | ------------------------------------------- |
| `403`  | Caller has no authenticated user identity.  |
| `404`  | Proposal not found in this workspace.       |
| `409`  | Proposal is no longer in `proposed` status. |

**Permissions:** Requires `ReviewQueue:Review`.

***

## Concurrency safety

The approve and reject endpoints use guarded state transitions. If two reviewers decide the same proposal at the same time, only one succeeds. The other receives `409 Conflict` and should reload the list to see the current status.

## Audit logging

Every approval or rejection is audit-logged with the connector type, resource type, and reviewer identity. The proposed payload is never included in audit log entries.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/platform-api/integrations/review-queue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.