Skip to main content
GET
/
api
/
calendar
/
media
Get social media upload limits
curl --request GET \
  --url https://app.puffle.ai/api/calendar/media \
  --header 'Authorization: Bearer <token>'
{
  "limits": {
    "image": {
      "maxSize": 8388608,
      "maxCount": 20,
      "extensions": [
        ".jpg",
        ".jpeg",
        ".png",
        ".gif"
      ]
    },
    "video": {
      "maxSize": 209715200,
      "maxCount": 1,
      "extensions": [
        ".mp4",
        ".mov",
        ".avi"
      ]
    },
    "document": {
      "maxSize": 104857600,
      "maxCount": 1,
      "extensions": [
        ".pdf",
        ".ppt",
        ".pptx",
        ".doc",
        ".docx"
      ]
    }
  }
}

​
Overview

Returns the hard limits enforced by the upload endpoint. These come from LinkedIn’s platform rules — other platforms may have lower effective limits the caller should apply on top.
TypeMax sizeMax countExtensions
Image8 MB20 per post.jpg, .jpeg, .png, .gif
Video200 MB1 per post.mp4, .mov, .avi
Document100 MB1 per post.pdf, .ppt, .pptx, .doc, .docx
LinkedIn also disallows mixing media types in one post — if you attach an image, you cannot also attach a video.

​
AI agent notes

Cache this response client-side. Values are effectively static — they change only when Late updates its own limits, which is rare.Related verbs on this path:
  • POST /api/calendar/media — upload a file (uploadSocialMedia)
  • DELETE /api/calendar/media — no-op convenience endpoint (deleteSocialMedia)

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Response

Media upload limits.

​
limits
object
required

Per-media-type size and count limits. Agents should check these client-side before attempting uploadSocialMedia to avoid wasted bandwidth.