Brightery Woo-Order-Api
Connecting WooCommerce to customer service chatbots shouldn’t require exposing your entire store to complex webhook setups or granting full read/write API access. Brightery Woo-Order-Api acts as a secure, read-only bridge. It provides two highly specific API endpoints tailored exactly to what chatbots need: order statuses and tracking links. It is perfectly suited for developers building automated customer support flows on platforms like ManyChat, Chatfuel, Dialogflow, or custom AI agents. Features Secure API Key Authentication: Easily generate an API key from the WordPress admin dashboard to ensure only your bot can access the data. Targeted Data: Exposes only the necessary data (order status, shipping dates, courier, tracking links) without leaking sensitive customer information. Search by Email or Phone: Allows bots to query a user’s purchase history using their contact information. Order Verification: The specific order endpoint requires the billing email to match the order ID, adding an extra layer of privacy. API Endpoints Base URL: https://your-site.com/wp-json/Brightery-api/v1 1. Get Specific Order (Ideal for “Where is my order?” flows) * GET /order/{order_id}?email=customer@example.com 2. Get Customer Order History * GET /orders/by-contact?phone=1234567890 * GET /orders/by-contact?email=customer@example.com Authentication: All requests must include the header: X-Brightery-API-Key: YOUR_API_KEY
WPGraphQL Smart Cache
Do you want your API data fast or accurate? With WPGraphQL Smart Cache, you can have both. WPGraphQL Smart Cache is a free, open-source WordPress plugin that provides support for caching and cache invalidation of WPGraphQL Queries. To get the most out of this plugin, we recommend using GET requests with Network Caching, which requires your WordPress install to be on a supported host. Note: WPGraphQL Smart Cache is now part of the WPGraphQL monorepo. All releases, issues, and discussions are managed in the main repository. BREAKING CHANGES: We may make breaking changes in the future to improve functionality and experience. If we do, we will use semver to do so. Pay attention to release notes and upgrade notices before updating. Video Overview Docs Overview Quick Start Features Network Cache Object Cache Persisted Queries Cache Invalidation Extending / Customizing Functionality FAQ and Troubleshooting Known Issues Providing Feedback Upgrading It is recommended that anytime you want to update WPGraphQL Smart Cache that you get familiar with what’s changed in the release. WPGraphQL Smart Cache publishes release notes on GitHub. Look for releases tagged with wp-graphql-smart-cache/v*. WPGraphQL Smart Cache will follow Semver versioning. The summary of Semver versioning is as follows: MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes. You can read more about the details of Semver at semver.org Privacy Policy WPGraphQL Smart Cache uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements. Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users. Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case. When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below). Learn more about how Appsero collects and uses this data.
