looktme API

Work with your looktme workspace from your own scripts, tools and AI agents. Use the REST API or connect an agent through MCP with the same API key. Available on every plan. API keys are for your own workspace.

What you can do

  • List your connected accounts and what the API can do on each.
  • List your recent posts and check the status of one post.

On X accounts where you turned on agent publishing (opt-in per account), an agent prepares a post and gets back an exact preview and a one-time confirmation token, valid 10 minutes. The post goes out only after an explicit confirm. Each X account allows up to 10 agent posts a day, and a post-now can be undone for 30 seconds. LinkedIn stays drafts-only: create_draft returns an approval link (valid 72 hours) to review, edit and approve each post yourself, and agents can't publish, schedule or approve LinkedIn posts. X accounts without the opt-in work the same way.

Get an API key

Sign in, open Developers → API keys and create a key with the access it needs. Copy it right away: it's shown only once. Send it as Authorization: Bearer YOUR_API_KEY. Keep it secret, and revoke it there if it leaks.

REST API

Base URL https://api.looktme.com/v1. OpenAPI spec: https://api.looktme.com/v1/openapi.json

List your connected accounts (read scope)

curl https://api.looktme.com/v1/connections \
  -H "Authorization: Bearer $LOOKTME_API_KEY"

Check a post

curl https://api.looktme.com/v1/posts/POST_ID \
  -H "Authorization: Bearer $LOOKTME_API_KEY"

Built for production

  • Stable and versioned under /v1, described in OpenAPI 3.1. Within v1 we add fields but don't remove or rename them, except when a network's API or policy, security or the law requires it. Where practicable, we announce breaking changes and retirements at least 30 days in advance on this page or by email.
  • One error shape everywhere: { message, code, requestId }, with stable codes.
  • Send an Idempotency-Key header on POST requests to retry safely.
  • Authenticated responses include X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset.

Security

  • Keys stored as a hash: We keep only a SHA-256 hash of each API key. The full key is shown once, when you create or rotate it, and we can't show it again.
  • Scopes per key: Give each key only what it needs: read (accounts and post status), draft (create drafts), schedule (schedule posts). Scopes are independent; new keys start with all three.
  • Rotate and revoke: Rotate a key to replace it in one step, or revoke it. A revoked key stops working right away. Each key shows when it was last used.
  • Encrypted in transit: The API and MCP server are served only over HTTPS (TLS).
  • Activity log: Every API and MCP call that a valid key makes is logged with the key, the client, the operation, the result and the IP address. Calls rejected by the rate limit are not logged. Logs are kept for 12 months.
  • What we don't store: The full API key, and the post text in the activity log: it records ids and outcomes, not your content.
  • Stops with the account: Keys stop working if the person who created them leaves the workspace, loses the owner or admin role, or their account is deactivated or deleted, and while the workspace is suspended.

Connect an agent via MCP

Server URL https://api.looktme.com/mcp (Streamable HTTP), with the same Authorization header.

Claude Code

claude mcp add --transport http looktme https://api.looktme.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
  • list_connections: Your connected accounts and what an agent can do on each: schedule or draft only.
  • list_posts: Your 100 most recent posts and their status.
  • create_draft: A draft with one version per network, marked as AI-generated. LinkedIn and X drafts come with an approval link for you.
  • schedule_post: Schedules a draft version on a connected account at a future time.
  • get_post_status: The status of one post.

Networks and limits

  • LinkedIn: Drafts only (agentAccess: draft_only). Each draft returns an approvalUrl, valid for 72 hours. The person who connected the account, or a workspace owner, opens it signed in to looktme, reviews and edits the text, and approves that one post: post now or schedule. Agents can’t publish, schedule or approve LinkedIn posts. Up to 3,000 characters.
  • X: On X accounts where you turned on agent publishing (opt-in per account), an agent prepares a post and gets back an exact preview and a one-time confirmation token, valid 10 minutes. The post goes out only after an explicit confirm. Each X account allows up to 10 agent posts a day, and a post-now can be undone for 30 seconds. X accounts without the opt-in stay drafts only (agentAccess: draft_only), approved through the approvalUrl. Up to 280 characters, counted the way X does (links count 23).
  • TikTok: drafts only. You choose the privacy and post settings and publish in looktme.

Scheduled posts follow the same fair use as your other posts (see pricing). Requests are limited to 60 per minute per API key and 120 per minute per IP address, shared between REST and MCP.

Use of the API is subject to our Terms, Privacy Policy and Acceptable Use Policy.