---
title: "Comment by Rishabh Mishra on \"Custom REST API Integration for WordPress: Endpoints, Auth and Caching Done Right\" | Hashnode"
description: "The idempotency point is the one I would underline. A provider retry creating a duplicate order only shows up in production, so checking the webhook's idempoten"
url: "https://hashnode.com/posts/custom-rest-api-integration-for-wordpress-endpoints-auth-and-caching-done-right/6afa07d566ea1c58757afbee/comment/6afa71ab87efd5594d28d509"
---

[Discussion](https://hashnode.com/posts/custom-rest-api-integration-for-wordpress-endpoints-auth-and-caching-done-right/6afa07d566ea1c58757afbee)

Comment [Custom REST API Integration for WordPress: Endpoints, Auth and Caching Done Right](https://hashnode.com/posts/custom-rest-api-integration-for-wordpress-endpoints-auth-and-caching-done-right/6afa07d566ea1c58757afbee)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[1d ago](https://hashnode.com/posts/custom-rest-api-integration-for-wordpress-endpoints-auth-and-caching-done-right/6afa07d566ea1c58757afbee/comment/6afa71ab87efd5594d28d509)

The idempotency point is the one I would underline. A provider retry creating a duplicate order only shows up in production, so checking the webhook's idempotency key before processing is worth doing from the first version.
