Cerclen API
Proposals

List proposed requests

The running side's proposals, pending first, then decided ones newest first. The other side gets an empty list.

GET
/api/v1/deals/{deal_id}/proposals

The running side's proposals, pending first, then decided ones newest first. The other side gets an empty list.

Authorization

ApiKey
headerAuthorizationBearer <token>

An API key from your organization's API Keys page in Cerclen.

Path Parameters

deal_id*Deal Id
Formatuuid

Response Body

Successful Response

application/json
  1. response
[index: integer]?

A request an editor proposed, for one of the deal's admins to file or decline. It has no number until approved, when it becomes a request; the other side never sees it.

curl -X GET 'https://app.cerclen.com/api/v1/deals/497f6eca-6276-4993-bfeb-53cbbbba6f08/proposals' \  -H "Authorization: Bearer $CERCLEN_KEY"
[  {    "assignee_id": "string",    "body": "string",    "can": {      "decide": true,      "withdraw": true    },    "category": "string",    "category_id": "string",    "created_at": "2019-08-24T14:15:22Z",    "decided_at": "2019-08-24T14:15:22Z",    "due_date": "2019-08-24",    "id": "string",    "priority": "low",    "proposed_by_id": "string",    "reason": "string",    "request_id": "string",    "requester": "string",    "state": "pending",    "title": "string"  }]