Getlate Late API

Name: Late API
Brand: Late API
Availability: InStock

✓ Official Vendor SpecSocial MediaSocial Publishingbearer, apiKey177 EndpointsREST

For Agents

Schedule and publish posts across major social platforms, pull cross-network analytics, and manage account groups through a Bearer-authenticated API.

Use for: I need to schedule a post across LinkedIn and Twitter for tomorrow morning, Get analytics for posts published in the last 7 days, List the account groups configured for an agency client, Check whether a post fits the LinkedIn character limit before scheduling

Not supported: Does not handle paid ad campaigns, native CRM workflows, or email marketing - use for organic social scheduling, analytics, and media tooling only.

Late is a multi-channel social media scheduling and publishing platform that exposes a 177-endpoint REST API covering posts, profiles, accounts, account groups, analytics, comments, messages, and media uploads across major networks. The API also bundles utility tools for downloading content from YouTube, TikTok, Instagram, Twitter, Facebook, LinkedIn, and Bluesky, plus validators for post length, hashtags, and media URLs. Authentication uses Bearer API keys for app-level requests and an X-Connect-Token header for end-user delegated access. It is built for agencies, social tools, and AI agents that need to publish, analyze, and manage content at scale.

Jentic One on Github

Install Jentic One Beta

Connect the Late API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Late API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetlate.dev%2Fgetlate" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetlate.dev%2Fgetlate" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Late API.

Schedule posts across multiple social networks from a single POST through the /v1/posts endpoints

Pull cross-network analytics including daily metrics, best-time-to-post recommendations, and content decay through /v1/analytics

Manage account groups with /v1/account-groups for agencies handling many client portfolios

Validate post content, length, and media URLs before scheduling through /v1/tools/validate endpoints

GET STARTED

Start building with Late API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Late API for, with concrete tasks.

★ Multi-Network Social Scheduling

Schedule a single post payload across multiple social networks from one API call so that an internal tool does not need per-network publishing logic. The integration calls the /v1/posts endpoints to create scheduled posts and /v1/analytics to track performance after they go live. Setup typically takes a day or two given the breadth of supported networks.

Call POST /v1/posts with content and a list of profile ids spanning Twitter and LinkedIn, scheduled for 09:00 tomorrow, and confirm a 200 response.

Pre-Schedule Content Validation

Catch invalid posts before they get scheduled by running the /v1/tools/validate endpoints. The integration calls POST /v1/tools/validate/post-length to check character counts per network, POST /v1/tools/validate/post for content rules, and POST /v1/tools/validate/media for media URLs. Reduces failed posts and customer support escalations.

Call POST /v1/tools/validate/post-length with the post body and a target network array, and reject the schedule if any network reports invalid=true.

Cross-Network Analytics Dashboard

Build a dashboard that surfaces post analytics, daily metrics, content decay curves, and best-time-to-post recommendations across networks. The integration calls GET /v1/analytics, GET /v1/analytics/daily-metrics, GET /v1/analytics/best-time, and GET /v1/analytics/content-decay. Consolidates data that would otherwise require per-network analytics endpoints.

Call GET /v1/analytics/daily-metrics for the last 30 days and GET /v1/analytics/best-time for the connected profile, then return both as a chart payload.

Agency Client Workspace Management

Manage many client portfolios from a single API consumer by using /v1/account-groups to group connected social accounts per client. The integration creates and updates groups as clients are onboarded or churned, and reads the group when scheduling posts. Suited to social agencies running tens to hundreds of brands.

Call POST /v1/account-groups with name='Client A' and profile ids for that client's connected accounts, then PUT to update membership when accounts change.

AI Agent Social Manager

An AI agent acts as a social manager that drafts posts, validates them, schedules across networks, and pulls analytics - all through Jentic. The agent uses intent search to discover the right Late operation rather than reading the OpenAPI directly, and Jentic stores the Bearer key out of context. Time-to-first-post-scheduled drops from hours to minutes.

Search Jentic for 'schedule a Late post', load the schema for POST /v1/posts, and schedule a post for the connected LinkedIn profile at 14:00 today.

Key Endpoints

177 endpoints — late is a multi-channel social media scheduling and publishing platform that exposes a 177-endpoint rest api covering posts, profiles, accounts, account groups, analytics, comments, messages, and media uploads across major networks.

METHOD

PATH

DESCRIPTION

GET

/v1/analytics

Get post analytics across connected networks

GET

/v1/analytics/best-time

Get best times to post per profile

GET

/v1/account-groups

List account groups for agency client management

POST

/v1/account-groups

Create an account group

POST

/v1/tools/validate/post

Validate post content before scheduling

POST

/v1/media/presign

Generate a presigned upload URL

GET

/v1/analytics

Get post analytics across connected networks

GET

/v1/analytics/best-time

Get best times to post per profile

GET

/v1/account-groups

List account groups for agency client management

POST

/v1/account-groups

Create an account group

POST

/v1/tools/validate/post

Validate post content before scheduling

POST

/v1/media/presign

Generate a presigned upload URL

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Late by hand means picking between its bearer key and X-Connect-Token, selecting the right header per operation, and shaping media, analytics, and scheduling payloads across many endpoints yourself. Through Jentic you install once, import the Late API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Late routes most actions through account groups and profiles carried in the request body rather than a resource id in the path, so you limit the agent to the operations it needs, such as reading analytics or scheduling a post. Because you pick the operation set, anything beyond those is not reachable unless you add it.

Credential isolation

Your Late API key and any connect token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a social post' or 'find the best time to post', and Jentic returns the matching Late operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Late API through Jentic.

What authentication does the Late API use?

Late supports two authentication schemes: HTTP Bearer for app-level requests using an API key, and an X-Connect-Token header for delegated end-user access. Jentic stores both credential types in its encrypted vault and injects the right header per operation.

Can I schedule a post across multiple networks with the Late API?

Yes. Call POST /v1/posts with the post content and a list of connected profile ids spanning networks like LinkedIn, Twitter, Instagram, and TikTok. The Late platform handles per-network formatting and queues each delivery for the scheduled time.

What are the rate limits for the Late API?

Late applies per-API-key throttles that are not encoded in the spec. Plan for sustained throughput around 10 requests per second per Bearer key and back off when you receive 429 responses; the Retry-After header indicates the cooldown.

How do I validate a post before scheduling it through Jentic?

Search Jentic for 'validate a Late post', load the schema for POST /v1/tools/validate/post or POST /v1/tools/validate/post-length, and execute with the post body and target networks. Reject scheduling when the response reports invalid for any selected network.

Does the Late API support analytics across networks?

Yes. /v1/analytics returns post-level metrics, /v1/analytics/daily-metrics returns aggregated daily data, /v1/analytics/best-time returns optimal posting windows per profile, and /v1/analytics/content-decay reports performance fall-off after publish.

Can I download media from social platforms with the Late API?

Yes. The /v1/tools/{network}/download endpoints fetch downloadable URLs for YouTube, TikTok, Instagram, Twitter, Facebook, LinkedIn, and Bluesky media. Useful for repurposing existing content into a Late publishing workflow.

Can I limit what my agent is allowed to do with the Late API?

Yes. Because you self-host Jentic One, your own rules decide which Late operations the agent may call, so you can grant just the ones it needs, such as GET /v1/analytics for reading metrics or POST /v1/posts for scheduling, and leave account-group management or media downloads out. Late carries account groups and profiles in the request body rather than in the path, so scoping the operation set also bounds which connected accounts the agent can reach. Any operation you do not add stays unreachable to the agent.

Getlate Late API

Connect the Late API to your agent

Capabilities

Start building with Late API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs