What authentication does the Lytho (InMotionNow) API use?

The Lytho API uses HTTP bearer tokens - pass 'Authorization: Bearer <token>' on every request. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and never reaches the agent's context.

Can I create projects and tasks programmatically?

Yes. POST /projects creates a project (returning the project ID), and POST /tasks creates a task that can reference the project. PUT /projects/{projectId} updates an existing project - for example, to flip status when work is approved.

What are the rate limits for the Lytho (InMotionNow) API?

Rate limits are not encoded in the spec. Lytho enforces them per token; check the Lytho admin console or contact Lytho support via zapierdocs.ignite.inmotionnow.com for the per-minute limits applied to your account.

How do I list creative proofs through Jentic?

Search Jentic for 'list Lytho proofs' to find GET /proofs. Load the schema, supply any filters required, and execute. Cross-reference the assignee against GET /users to identify who owns the next review step. Get started with Jentic One, the self-hosted execution layer.

Is the API the same one InMotionNow used before the rebrand?

InMotionNow rebranded to Lytho. The base URL is api.lytho.com but the API still serves customers who originally signed up with InMotionNow - endpoints, auth model, and data shapes remain consistent for existing integrations.

Can I limit what my agent is allowed to do with the Lytho (InMotionNow) API?

Yes. Because you run Jentic One yourself, your own rules decide which Lytho operations and credentials the agent may use. You can allow it only the reads you want, such as GET /projects, GET /tasks, GET /proofs, and GET /users, and leave out write operations like POST /projects or POST /tasks so the agent cannot create work. Since the project id sits in the URL path (/projects/{projectId}), a rule can also pin the agent to reading and updating a single project rather than the whole workspace.