Update README.md

Author: goldlabelapps

app/api/flickr/README.md

@@ -1,28 +1,37 @@
-# README for Flickr API integration
 
-This module provides API routes for accessing Flickr data, similar to the GitHub integration. It expects the following environment variables to be set in your .env file:
+# Flickr API Integration
 
-- FLICKR_USER
-- FLICKR_KEY
-- FLICKR_SECRET
+This module provides API routes for accessing and syncing Flickr data, mirroring the GitHub integration. It expects the following environment variables in your `.env` file:
 
-### Route
+- `FLICKR_USER`
+- `FLICKR_KEY`
+- `FLICKR_SECRET`
+
+## Endpoints
 
 - **GET /flickr**: Returns counts and recent records from all Flickr tables.
+- **POST /flickr/createtable**: Drops all Flickr tables if they exist, then recreates them with the correct schema and constraints.
+- **POST /flickr/emptytables**: Deletes all rows from all Flickr tables (does not drop tables).
+- **POST /flickr/sync**: Fetches public photos for the configured Flickr user and stores them in the database.
 
-### Proposed Table Design
+## Table Design
 
-1. flickr_accounts
+1. **flickr_accounts**
    - One row per Flickr account/user profile.
    - Stores account identity fields and full raw payload.
-2. flickr_photos
+2. **flickr_photos**
    - One row per photo.
+   - `flickr_id` is unique.
    - Stores photo metadata plus raw JSON payload.
-3. flickr_albums
+3. **flickr_albums**
    - One row per album.
    - Stores album metadata plus raw JSON payload.
-4. flickr_resources
+4. **flickr_resources**
    - Generic catch-all for any future Flickr resource type.
    - Supports additional Flickr objects through jsonb payload storage.
 
-This structure mirrors the GitHub integration for consistency and flexibility.
+## Notes
+
+- The `/flickr/createtable` endpoint will **drop all Flickr tables** before recreating them. Use with caution—this will erase all Flickr data.
+- The `/flickr/sync` endpoint currently fetches public photos for the configured user and inserts them into `flickr_photos`.
+- The structure and endpoints are designed for consistency and flexibility, matching the GitHub integration.