Late API

**Quick judgment**: This skill is a strong, domain-specific API reference for integrating the Late Social Media Scheduling API. It’s well-suited for developers building multi-platform social posting, scheduling, and analytics tools, but it’s narrowly focused on the Late ecosystem. **What it’s good for** - Implementing end-to-end flows: create profiles, connect social accounts via OAuth, and create/schedule posts across 13 platforms. - Handling production concerns: media uploads, queues/slots, webhooks, retries, and error/rate-limit handling. - Dealing with platform-specific behavior (limits, formats, analytics fields) without reading 13 separate native platform docs. **Key risks / limitations** - **Vendor/API dependency**: Behavior, endpoints, and limits may change on Late’s side; you must still handle versioning, deprecations, and fallbacks. - **Platform policy risk**: Using the API to automate posting must respect each platform’s ToS and rate limits; misuse can lead to account restrictions. - **Security considerations**: Requires careful management of API keys, OAuth tokens, and webhook signature verification in your own code. - **Scope**: It is a reference for the Late API only; it doesn’t replace general-purpose HTTP, auth, or infrastructure tooling. **Recommended scenarios** - Building or extending a social media scheduler, content calendar, or social CRM that posts to many platforms from a single backend. - Creating internal tools for marketing teams to manage accounts, queues, and posting analytics via Late. - Prototyping a unified social publishing or analytics service where Late acts as the abstraction over individual network APIs.