Advanced Coupons API
  • REST API
  • coupons/v1
    • Virtual Coupons (Premium)
      • Query a list of virtual coupons
      • Fetch virtual coupon stats
      • Create a virtual coupon
      • Retrieve a virtual coupon
      • Update a virtual coupon
      • Delete a virtual coupon
      • Bulk create virtual coupons
      • Bulk delete virtual coupons
    • Search Customers (Premium)
    • Settings
  • loyalty-program/v1
    • Dashboard
    • Customers
    • Settings
    • My Points
  • wc-loyalty-program/v1
    • Dashboard
    • Customers
    • Settings
  • wc-store-credits/v1
    • Entries
      • Query a list of store credit entries
      • Create a store credit entry
      • Fetch a single store credit entry
      • Update store credit entry
      • Delete store credit entry
    • Customers
      • Get dashboard statistics data
      • Query list of customers with store credits balance
      • Get single customer statistics and sources
Powered by GitBook
On this page
  • Namespaces
  • Authentication
  • Permissions

Was this helpful?

REST API

Nextcoupons/v1

Last updated 3 years ago

Was this helpful?

Advanced Coupons creates it own namespace and endpoints by extending the default .

Namespaces

Authentication

The plugin uses WordPress REST API in the admin app.

For remote applications (e.g Postman), you will need to authenticate using either of the following options:

  • (this should only be used for testing purposes only, and should not be recommended for production)

Permissions

Permissions are managed via . Each endpoint and its respective method varies depending of the use case of said endpoint.

For endpoints which purpose is for the admin side may only be accessed by user roles that has the manage_woocommerce user capability. (Administrator, Shop Manager, etc.)

For endpoints that will need to be used globally (settings) will not require any authentication for reads, but will need to have the manage_woocommerce user capability for doing create, update and delete actions.

For endpoints which contains private data for the current user, it will at least require the user to have an authenticated logged in status. This is checked via function.

WordPress REST API
coupons/v1
loyalty-program/v1
wc-store-credits/v1
cookie authentication
OAuth 1.0a Server
Application Passwords
JSON Web Tokens
Basic Authentication
WordPress user roles and capabilities
is_user_logged_in