content360（content360 控制）

Content360 Skill

Authentication

Content360 uses a session + bearer token auth mechanism built on Laravel Sanctum + Inertia.js.

Setup

1. Get your bearer token at https://app.content360.io/os/profile/access-tokens
2. Set secrets in Zo: Settings → Advanced → Secrets

- CONTENT360_API_KEY = your bearer token - CONTENT360_ORG_ID = your workspace UUID (from the dashboard URL)

1. Set your credentials (for automatic session auth):

- CONTENT360_EMAIL = your login email - CONTENT360_PASSWORD = your login password

Note: Access tokens require an active web session to work. If the token returns 401, re-authenticate by logging in via the web interface or using the session login flow in content360_sync.py.

Auth Flow

The API requires all of these headers on every request:

Authorization: Bearer {token}
X-Requested-With: XMLHttpRequest
X-Inertia: true
X-Inertia-Version: {version}       # from any authenticated page response
Accept: application/json
Content-Type: application/json

The X-Inertia-Version is a hash that changes on app updates. It's returned in every Inertia JSON response under the X-Inertia-Version response header. The sync script handles this automatically.

Base URLs

• App: https://app.content360.io
• API namespace: /os/api/{workspace} (workspace = org UUID)
• Web namespace: /os/{workspace} (same routing, differs only by Accept header)

API Endpoints

All require auth headers above. Responses are Inertia JSON.

Posts

Create Post Payload

{
  "content": "Post text content",
  "accounts": ["126117", "126129"],
  "status": "draft",
  "versions": [
    {
      "account_id": 126117,
      "is_original": true,
      "content": [
        {
          "body": "<div>Post content</div>",
          "media": [],
          "url": "",
          "opened": true
        }
      ]
    }
  ]
}

• status: "draft" or "schedule"
• accounts: array of account IDs (strings)
• versions: per-account content blocks (body uses HTML)
• For plain text, use "<div>text</div>" in body

Accounts

Media

Tags

Other

Webhook Endpoints

Running the Sync Script

# Dry run
python3 /home/workspace/Skills/content360/scripts/content360_sync.py --dry-run

# Real sync
python3 /home/workspace/Skills/content360/scripts/content360_sync.py

# Sync specific platforms
python3 /home/workspace/Skills/content360/scripts/content360_sync.py --platforms facebook,linkedin,youtube

The script reads from your Notion content calendar, creates posts in Content360 as drafts, and schedules them. See README.md for full setup instructions.

Notion Database Properties

The sync script expects these properties in your Notion content calendar database: