---
title: "Check Google Play purchase synchronization status"
method: GET
path: "/google-play/purchases/synchronizations/{synchronizationId}"
---

# Check Google Play purchase synchronization status

`GET /google-play/purchases/synchronizations/{synchronizationId}`

Use this endpoint to retrieve the status and result of a purchase synchronization or transfer process initiated by the [`/purchases`](https://developers.cleeng.com/reference/register-google-play-purchase) or [`/purchases/transfers`](https://developers.cleeng.com/reference/transfer-google-play-purchase) endpoint. This endpoint provides a concise response with the essential status information, including `status`, `accessGranted`, `offerId`, and `result`. <br><br> For real-time updates on the synchronization status, you can also subscribe to the [`inappPurchaseSyncResult`](https://developers.cleeng.com/docs/webhooks-in-app-purchase-topics#inapppurchasesyncresult) webhook, which provides a more detailed payload (`WebhookSynchronizationStatus`) with additional information about the transaction. <br><br> The `status` field indicates the current stage of the synchronization process: <br> - `processing`: The synchronization is in progress.  <br> - `retrying:` The synchronization encountered an error and is being retried. This status may appear multiple times. <br> - `finalized:` The synchronization process has completed. <br><br> The `result` field provides more detailed information about the outcome of the synchronization and is only available when `status` is `finalized`. The `accessGranted` field indicates whether the user is entitled to the offer. The `offerId` field provides the ID of the offer. You can see some possible scenarios and the corresponding response fields in the [polling](https://developers.cleeng.com/docs/google-play-billing#polling-statuses) section of the integration tutorial. <br><br>Please note that **this endpoint can be authorized with a publisher (X-Publisher-Token) or JWT (Bearer) token**. Depending on how you integrate with Cleeng (directly or through middleware), use either a <<glossary:JWT>> or X-Publisher-Token header authorization. <br> <br> <span style="color:green">**Please use JWT (Bearer) token to try out the endpoint in the API console in this documentation**.</span>

## Path parameters

- `synchronizationId` string, required

## Headers

- `Authorization` string
- `X-Publisher-Token` string
- `X-App-Version` string
- `X-Device-Id` string
- `X-Device-Type` string
- `X-User-Action` string

## Response `200`

200

- object
  - `status` string
  - `accessGranted` boolean
  - `offerId` string
  - `correlationId` string
  - `result` string

## Other responses

- `400` — 400
- `404` — 404
- `500` — 500

---

[API](https://skmtc.net/cleeng/apis/mediastore-api.md) · [All operations](https://skmtc.net/cleeng/apis/mediastore-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cleeng/mediastore-api/versions/00cbfe7998a4/schema)