manifest / integrations / 360-api-sync
360 API Sync
Synchronizes clinic and doctor data from the PR360 API into WordPress custom post types for the 360 medical site network.
★ 0stars
0forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/kazimiralvis/360-api-sync/archive/refs/heads/main.zipDeclares an update source (https://github.com/KazimirAlvis/360-api-sync), so updates arrive through the plugin's own updater.
From the readme
360 API Sync
Stage 2 responsibility note: API Sync remains the upstream transport and canonical writer. When 360 Platform Core is active, relationship persistence and entity/sync lifecycle events use the Core contract while legacy compatibility writes remain intact.
Repository: https://github.com/KazimirAlvis/360-api-sync
Plugin Overview
360 API Sync synchronizes clinic and doctor content from the PR360 API into existing WordPress clinic and doctor CPTs. It supports remote API mode and mock JSON mode.
Installation
1. Place plugin in wp-content/plugins/360-api-sync.
2. Activate 360 API Sync.
3. Open 360 API Sync → Settings.
4. Configure API values or enable mock mode.
5. Run manual sync.
Configuration
Settings page fields:
- API Base URL
- API Key
- GitHub Token (optional, for private-repo plugin updates)
- Site Slug
- Enable Mock API
- Dry Run Mode
- Manual Sync button
Mock file:
- mock-data/clinics.json
API Sync Architecture
- Base URL:
- https://cmltutizsixpurslzfzl.supabase.co/functions/v1
- Endpoint:
- GET /sync?siteslug={siteslug}
- Auth headers:
- x-api-key: APIKEY
- temporary fallback: Authorization: Bearer APIKEY (compatibility only)
Remote Tr