Best time to post

GET /v1/analytics/best-time looks at the posts an account (or a whole profile) already published and tells you which hours of the week earned the most engagement. It is your own history, not an industry average, so it gets better as you post more.

#Get the best slots

curl "https://api.pozy.ai/v1/analytics/best-time?accountId=6650c1e2a3b4c5d6e7f80a22" \
  -H "Authorization: Bearer $POZY_API_KEY"

const res = await fetch("https://api.pozy.ai/v1/analytics/best-time?accountId=6650c1e2a3b4c5d6e7f80a22", {
  headers: { Authorization: `Bearer ${process.env.POZY_API_KEY}` },
});
const data = await res.json();
if (!res.ok) throw new Error(data.error);

const top = [...data.slots]
  .filter((s) => s.post_count >= 3)
  .sort((a, b) => b.avg_engagement - a.avg_engagement)
  .slice(0, 5);
console.log(top);

import os
import requests

resp = requests.get(
    "https://api.pozy.ai/v1/analytics/best-time",
    headers={"Authorization": f"Bearer {os.environ['POZY_API_KEY']}"},
    params={"accountId": "6650c1e2a3b4c5d6e7f80a22"},
    timeout=30,
)
slots = [s for s in resp.json()["slots"] if s["post_count"] >= 3]
print(sorted(slots, key=lambda s: s["avg_engagement"], reverse=True)[:5])

{
  "slots": [
    { "day_of_week": 1, "hour": 17, "avg_engagement": 412.5, "post_count": 8 },
    { "day_of_week": 3, "hour": 12, "avg_engagement": 388.0, "post_count": 6 },
    { "day_of_week": 6, "hour": 9, "avg_engagement": 120.3, "post_count": 2 }
  ]
}

#How to read a slot

Pozy groups every published post by the weekday and UTC hour it went out, then averages engagement per group. Slots with no posts are left out, so a sparse history returns few slots.

#Filters

#Convert to the account's timezone

Slots are in UTC. Convert them before you show them or schedule against them:

function slotToLocal(slot: { day_of_week: number; hour: number }, timeZone: string) {
  // Pick any Monday at 00:00 UTC, then move to the slot.
  const base = Date.UTC(2026, 9, 26); // Monday 26 October 2026
  const at = new Date(base + (slot.day_of_week * 24 + slot.hour) * 3_600_000);
  return new Intl.DateTimeFormat("en-GB", { timeZone, weekday: "long", hour: "2-digit", minute: "2-digit" }).format(at);
}

slotToLocal({ day_of_week: 1, hour: 17 }, "America/New_York"); // "Tuesday 13:00"

#Schedule into the best slots

Two common patterns:

• Pick a time per post. Take the best slot after now and pass it as scheduledFor when you create the post. Keep the timezone explicit, as described in Scheduling.
• Feed a queue. Turn the top slots into a recurring queue schedule, so every post you add goes out at one of them. See Queues.

#How often to post

GET /v1/analytics/posting-frequency answers a different question: does posting more often help or hurt? It groups past weeks by how many posts went out and reports the engagement of each group, per platform.

Look for the cadence where the engagement rate stops rising. As with slots, ignore rows backed by one or two weeks.

#When followers are online

For Instagram accounts with at least 100 followers, GET /v1/analytics/instagram/online-followers returns how many followers were online in each hour of each of the last 30 days. It works before you have a posting history. Instagram does not document the timezone of its hour keys, so compare it with your own best-time slots before relying on the exact hour.

#Endpoints