---
title: "Discussion on \"Custom REST API Integration for WordPress: Endpoints, Auth and Caching Done Right\" | Hashnode"
description: "Discussion on \"Custom REST API Integration for WordPress: Endpoints, Auth and Caching Done Right\". This guide was first published on Swift Web Dev, where it stays up to date.\nSooner or later every serious WordPress site has to talk to something that is not WordPress: a mobile app, an ERP, a React f"
url: "https://hashnode.com/posts/custom-rest-api-integration-for-wordpress-endpoints-auth-and-caching-done-right/6afa07d566ea1c58757afbee"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Custom REST API Integration for WordPress: Endpoints, Auth and Caching Done Right](https://raselhk.hashnode.dev/custom-rest-api-integration-for-wordpress-endpoints-auth-and-caching-done-right?utm_source=hashnode&utm_medium=feed)

This guide was first published on Swift Web Dev, where it stays up to date. Sooner or later every serious WordPress site has to talk to something that is not WordPress: a mobile app, an ERP, a React f

1d ago · 10 min read · raselhk.hashnode.dev  
Read the article

-   [#wordpress](https://hashnode.com/tag/wordpress)
-   [#rest-api](https://hashnode.com/tag/rest-api)
-   [#php](https://hashnode.com/tag/php)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[Rasel Hakkani](https://hashnode.com/@raselhk)

@raselhk · Bangladesh

  
[View profile](https://hashnode.com/@raselhk)

WordPress developer, founder of Swift Web Dev. Plugins, speed fixes and free web tools.

WordPress developer with 9+ years of experience. I run Swift Web Dev (https://swiftwebdev.com): custom WordPress and WooCommerce builds, Bricks sites, Core Web Vitals fixes, free WordPress plugins and free web tools.

## Responses 1

Markdown supported · ⌘↵ to post

[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.
