> For the complete documentation index, see [llms.txt](https://onestore-dev.gitbook.io/dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onestore-dev.gitbook.io/dev/eng/tools/billing/old-version/v19/one-store-iap-upgrade-guide/one-store-iap-api-upgrade-guide/server-api-details-change-history.md).

# Server API Details Change History

| Items        | API list                                                  | API URI                                                                             | Changes                                                                                          |                                                                                                                                                                                                                                                                    |
| ------------ | --------------------------------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| V5 (SDK V17) | V6 (SDK V19)                                              |                                                                                     |                                                                                                  |                                                                                                                                                                                                                                                                    |
| Change       | Issue OAuth token                                         | /v2/oauth/token                                                                     | /v6/oauth/token                                                                                  | <p>Delete the status field among the response specifications.</p><p>Check normality (200) with Http response code.</p><p><br></p>                                                                                                                                  |
| Remove       | Check purchased in-app product details                    | <p>/v2/purchase/details/{purchaseId}/</p><p>{packageName}</p>                       | N/A                                                                                              | <p>Remove the ‘Check purchased in-app product details’ API for enhanced security.</p><p>Integrate with ‘Check purchased in-app product details by in-app ID’.</p><p><br></p>                                                                                       |
| Change       | Check purchased in-app product details by in-app ID       | <p>/v2/purchase/details-by-productid<br>/{purchaseId}/{packageName}/{productId}</p> | <p>/v6/apps/{packageName}/purchases/inapp/products<br>/{productId}/{purchaseToken}</p>           | Add the purchaseId, acknowledgeState fields to the response specifications.                                                                                                                                                                                        |
| Change       | Check purchased Monthly auto-renewal product details      | /v2/purchase/recurring-details/{purchaseId}/{packageName}                           | <p>/v6/apps/{packageName}/purchases/auto/products<br>/{productId}/{purchaseToken}</p>            | <p>Add acknowledgeState, lastPurchaseId, lastPurchaseState to the response specifications.</p><p>Remove price, developerPayload, purchaseState from the response specifications.</p><p><br></p>                                                                    |
| Remove       | Check last purchased Monthly auto-renewal product details | /v2/purchase/last-recurring-details/{purchaseId}/{packageName}                      | N/A                                                                                              | Integrate to the ‘Check purchased Monthly auto-renewal product details’ API.                                                                                                                                                                                       |
| Change       | Cancel automatic payment                                  | /v2/purchase/manage-payment-status/{purchaseId}/{packageName}/cancel                | <p>/v6/apps/{packageName}/purchases/auto/products<br>/{productId}/{purchaseToken}/cancel</p>     | Change the response specifications for processing success.                                                                                                                                                                                                         |
| Change       | Cancel automatic payment cancellation                     | /v2/purchase/manage-payment-status/{purchaseId}/{packageName}/reactivate            | <p>/v6/apps/{packageName}/purchases/auto/products<br>/{productId}/{purchaseToken}/reactivate</p> | Change the response specifications for processing success.                                                                                                                                                                                                         |
| Change       | Check purchase cancellation details                       | <p>/v2/purchase/voided-purchases/</p><p>{packageName}</p>                           | /v6/apps/{packageName}/voided-purchases                                                          | <p>For improving API usability, the standard for checking purchase cancellation details (startTime, endTime) is changed to the purchase cancellation time in the purchase time.</p><p>Add purchaseToken, marketCode to the response specifications.</p><p><br></p> |
| Change       | Consume purchased in-app product                          | <p>/v2/purchase/consume/{purchaseId}/</p><p>{packageName}</p>                       | <p>/v6/apps/{packageName}/purchases/inapp/products/<br>{productId}/{purchaseToken}/consume</p>   | Change the response specifications for processing success.                                                                                                                                                                                                         |
| Add          | Acknowledge purchase                                      | N/A                                                                                 | <p>/v6/apps/{packageName}/purchases/all/products/<br>{productId}/{purchaseToken}/acknowledge</p> | Newly add the ‘acknowledge purchase’ API.                                                                                                                                                                                                                          |


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://onestore-dev.gitbook.io/dev/eng/tools/billing/old-version/v19/one-store-iap-upgrade-guide/one-store-iap-api-upgrade-guide/server-api-details-change-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.