Poko
PricingDocsResources

Join the community

hello@poko.video
BlogRoadmapAPI pricingFree ToolsAffiliateTermsPrivacy
© 2026 Poko. All rights reserved.
Poko Motion Docs
GuidesAPI Reference
⌘ K
Support

Getting started

  • Quickstart
  • Install and sign in

Create a video

  • Create a video
  • Repo to video
  • URL to video
  • PDF and PowerPoint
  • Research paper explainer
  • MotionCut

Workspace

  • Projects and Canvas

Studio

  • Edit with chat
  • Project setup
  • Chat and context
  • Video preferences
  • Voices and narration

Animations

  • Create and manage animations

Settings

  • Models and API keys
  • Connections and skills
  • API

API Reference

  • Automation API

Exporting

  • Render and export

Help

  • Troubleshooting
Need help?
Browse documentation

Getting started

  • Quickstart
  • Install and sign in

Create a video

  • Create a video
  • Repo to video
  • URL to video
  • PDF and PowerPoint
  • Research paper explainer
  • MotionCut

Workspace

  • Projects and Canvas

Studio

  • Edit with chat
  • Project setup
  • Chat and context
  • Video preferences
  • Voices and narration

Animations

  • Create and manage animations

Settings

  • Models and API keys
  • Connections and skills
  • API

API Reference

  • Automation API

Exporting

  • Render and export

Help

  • Troubleshooting
DocsSettings

Settings

API

Find and configure API access from Poko Motion settings.

Last updated September 2026

Create a public URL

Select API in the desktop sidebar or open Settings → API. Choose a hostname slug between 6 and 30 characters using lowercase letters, numbers, and hyphens; saving it creates your public URL. The desktop app must remain running for callers to reach your local Motion instance.

Open the API reference →View endpoints, request fields, authentication, and working cURL examples.

Test reachability

Use Test tunnel after saving the slug. The result distinguishes a reachable desktop from a public URL that is live while this machine is disconnected.

Create and revoke keys

Create a named key for a caller such as n8n, Claude, or ChatGPT. Copy the secret immediately: it is shown only once. Saved key listings retain only a prefix plus created and last-used times. Revoke an exposed or unused key immediately. The same key is also valid on a self-hosted worker URL if you run one.

Protect credentials

Treat API keys like passwords: store them only where required, revoke them if exposed, and never share them in screenshots or support requests.

PreviousConnections and skills ←NextAutomation API →