API Key

This key is used to authenticate and secure communication between the application and the server. Requests without a valid API key will be rejected.

API Endpoint

1. Config Endpoint: This endpoint is used to retrieve configuration data for the mobile application. Requests must include the X-API-Key header. Define it in /src/config/config.ts.

2. API Key: API key for mobile app authentication. Keep this secure.

Important Rule

• To ensure the 3rd endpoint works properly, go to Permalink Settings in your WordPress admin panel.

• Make sure Post name is selected as the permalink structure.

• You can find this setting under: Settings → Permalinks → Post name.

• If this option is not enabled, the endpoint will not work correctly.

// ============================================
// MagicUI API CONFIGURATION
// API Key and Config URL for fetching settings from WordPress
// ============================================

// Paste the full config endpoint URL from WordPress plugin settings
export const MAGICUI_CONFIG_URL = 'https://magicuidemo.local/wp-json/magicui/v1/config';

// Set this in WordPress Admin > Settings > Magic UI
export const MAGICUI_API_KEY = 'eG42x36myO8Bv5t2k1LIZwSxHK0rHhZH';

WooCommerce REST API

1. WooCommerce Consumer Key: WooCommerce REST API Consumer Key (from WooCommerce > Settings > Advanced > REST API).

2. WooCommerce Consumer Secret: WooCommerce REST API Consumer Secret.

OneSignal

Product Documentation: OneSignal Docs

1. OneSignal Key ID: OneSignal REST API Key ID (for sending notifications from website). Get it from OneSignal Dashboard > Settings > Keys & IDs.

2. OneSignal Token: OneSignal REST API Key Token (for sending notifications from website). Get it from OneSignal Dashboard > Settings > Keys & IDs.

3. OneSignal App ID: OneSignal App ID for push notifications (used in mobile app).