---
title: "Get ChurnScore from ChurnScoreCalculation"
method: GET
path: "/ChurnScoreCalculation({Id})/ChurnScore"
tags: ["ChurnScoreCalculation"]
---

# Get ChurnScore from ChurnScoreCalculation

`GET /ChurnScoreCalculation({Id})/ChurnScore`

## Path parameters

- `Id` number, nullable, required

## Query parameters

- `$select` string[]
- `$expand` string[]

## Response `200`

Retrieved navigation property

- ChurnZeroChurnScore — A ChurnScore definition — a configurable scoring framework that estimates an Account's likelihood to renew on a 0 (low risk) to 100 (high risk) scale. Composed of weighted ChurnScoreFactors that must sum to 100 points and graded on a red/yellow/green scale. May be Standard (built from raw signals) or Composite (built from other ChurnScores). Scores are recalculated nightly and only apply to Active Accounts.
  - `Id` number — Internal identifier for ChurnZero.
  - `ChurnScoreType` 'Standard' | 'Composite' | 'Family' — The type of Churn Score: Standard (built from raw signal factors), Composite (built from other ChurnScores used as weighted factors), or Family.
  - `GradingBottom` number — The lower cut point of the red/yellow/green grading scale: calculated scores at or below this value grade green (healthy / low churn risk).
  - `GradingTop` number — The upper cut point of the red/yellow/green grading scale: scores above GradingBottom and at or below this value grade yellow; scores above this value grade red (high churn risk).
  - `Name` string — The name of the Churn Score, as configured by the admin.

## Other responses

- `400` — Bad Request|This usually occurs because of a missing or malformed parameter. Check the documentation and the syntax of your request and try again.
- `401` — Unauthorized|A valid authentication token was not provided with the request, so the API could not associate a user with the request.
- `403` — Forbidden|The authentication and request syntax was valid but the server is refusing to complete the request. This can happen if you try to read or write to objects or properties that the user does not have access to.
- `404` — Not Found|Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist.
- `409` — Conflict|The underlying model/schema has changed. Usually caused by a race condition. Sending the request again will succeed.
- `429` — Too Many Requests|You have exceeded one of the enforced rate limits in the API. See the documentation on rate limiting for more information.
- `500` — Internal Server Error|There was a problem on ChurnZeros's end.
- `default` — error

---

[API](https://skmtc.net/churnzero/apis/churnzero-rest-api-for-marketingpony.md) · [All operations](https://skmtc.net/churnzero/apis/churnzero-rest-api-for-marketingpony/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/churnzero/churnzero-rest-api-for-marketingpony/revisions/fa74265a328d/schema)