---
title: "Manually resolve a scheduling proposal"
method: POST
path: "/v1/scheduling/proposals/{id}/resolve"
tags: ["Scheduling"]
---

# Manually resolve a scheduling proposal

`POST /v1/scheduling/proposals/{id}/resolve`

## Request

- Base URL: `https://api.chronary.ai`
- URL: `https://api.chronary.ai/v1/scheduling/proposals/{id}/resolve`
- Auth: HTTP bearer

Runs the scoring algorithm immediately (without waiting for all participants to respond) and picks the best slot. If all existing responses are declines, the proposal is cancelled instead. **Requires Pro plan.**

## Path parameters

- `id` string, required

## Response `200`

Resolution result

- ResolveResult
  - `status` string, required
  - `resolved_slot` object, nullable, required

## Other responses

- `401`: Unauthorized — missing or invalid API key
- `403`: Plan upgrade required — feature is not available on the current plan
- `404`: Resource not found
- `409`: Proposal is not in a pending state
- `429`: Rate limited — 10 requests per second per key exceeded
- `500`: Internal server error

---

[API](https://skmtc.dev/chronary/apis/chronary-api.md) · [All operations](https://skmtc.dev/chronary/apis/chronary-api/llms.txt) · [OpenAPI document](https://skmtc.dev/chronary/apis/chronary-api/revisions/0d1a330294ae?raw)