API
Getting Started with the looktme REST API (curl)
Get started with the looktme REST API using curl. Check the current API reference for supported endpoints, authentication, and request formats.
By looktme · Published · 2 min read
The looktme REST API lets you list connected accounts and posts, create drafts, check status, and schedule eligible drafts. It uses Authorization: Bearer ltk_…; start with a read-scoped key and keep it server-side. The live contract is OpenAPI.
Key safety: Keep API keys server-side. Never place real credentials in browser code, prompts, or public repositories.
Before your first request
- Create an API key in Settings → API keys with only the required scope.
- Store the
ltk_key in server-side secret storage. Never expose it in browser code or a public repository. - Set the API base URL from
/developersand list your connections first. - Use
draftscope for draft creation. Theschedulescope exists, but scheduling LinkedIn and X posts through the API is not available yet.
# Set LOOKTME_API_KEY in your shell; never paste a real key into the document.
curl --request GET "https://api.looktme.com/v1/connections" --header "Authorization: Bearer ${LOOKTME_API_KEY}" --header "Accept: application/json"
GET /v1/connections lists connected accounts and their agentAccess. The contract also defines GET /v1/posts, POST /v1/posts (creates drafts), GET /v1/posts/{postId}, and POST /v1/drafts/{variantId}/schedule. Draft creation requires title, text, and networks. Use an Idempotency-Key when retrying writes, and check the live OpenAPI reference for current schemas.
Agent-created posts are drafts by default. Publishing or scheduling to LinkedIn and X through the API is not available yet; finish and publish those posts in the looktme app. Review endpoint effects before automating. Need help? Visit looktme Help.
FAQ
Where do I find the API base URL?
Use the current value shown in looktme Developers.
Can I put an API key in client-side code?
No. Keep it server-side and do not send it to support.