canonical: https://jentic.com/apis/inmotionnow.com/inmotionnow

# Inmotionnow Lytho (InMotionNow) API

Jentic publishes the only available OpenAPI specification for Lytho (InMotionNow) API, keeping it validated and agent-ready. Lytho (formerly InMotionNow) is a creative workflow management platform used by in-house marketing and creative teams to intake, route, review, and approve creative work. The 9-endpoint API covers projects, tasks, proofs (creative reviews), and users - letting external systems create projects from briefs, push tasks into the work queue, and read review status back into upstream tools. Authentication is bearer token.

## For AI agents

Create and read Lytho projects and tasks, list users, and inspect proofs (creative reviews) for in-house creative workflow management.

## Scope

Does not handle digital asset storage delivery, brand asset distribution, or financial budgeting - use for Lytho project/task creation, user lookup, and proof review status only.

## Capabilities

- List, create, and update Lytho projects via /projects and `/projects/{projectId}`
- List and create tasks within projects via /tasks and retrieve a specific task with `/tasks/{taskId}`
- List users in the Lytho workspace via /users to assign work and lookup reviewers
- List proofs (creative review/approval records) via /proofs to track review status of creative deliverables
- Push intake forms or briefs from external systems into Lytho as new projects automatically

## Use cases

### Brief-to-Project Intake Automation

When a marketing team submits a brief in a form, ticketing tool, or chat, automatically create the matching Lytho project so creative work starts without manual data re-entry. POST /projects accepts the project fields; POST /tasks adds the breakdown tasks under it. Cuts time-to-start for creative requests that previously sat in inboxes.

Example prompt: POST /projects with name 'Q3 Product Launch Email', then POST /tasks for each deliverable in the brief (banner, email, landing page).

### Creative Status Reporting

Pull project, task, and proof status from Lytho into a central reporting dashboard or stakeholder update. GET /projects, GET /tasks, and GET /proofs return the current state across the creative pipeline. Useful for marketing leaders who want a single view across multiple campaigns without logging into Lytho.

Example prompt: Call GET /projects and GET /proofs, then summarise how many proofs are awaiting review by project.

### Cross-System Task Sync

Sync Lytho tasks with the rest of the marketing operating stack - for example, mirroring tasks into a project management tool the wider company uses, or pushing a 'task complete' event when a proof is approved. PUT `/projects/{projectId}` updates project fields; the GET endpoints surface state for one-way reads.

Example prompt: Update project ID 12345 with status 'completed' via PUT `/projects/12345` once all proofs return 'approved'.

### AI Agent for Creative Operations

An LLM agent acting as a creative operations coordinator uses Lytho to spin up projects, route tasks to the right reviewers, and report on proof status. Through Jentic, the agent searches by intent ('create a creative project', 'list proofs awaiting review'), loads the schema, and executes - bearer-token credential handling is abstracted away.

Example prompt: List proofs with GET /proofs, identify those waiting more than 3 days, and notify the assigned user retrieved from GET /users.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/projects` | List all projects |
| POST | `/projects` | Create a new project |
| GET | `/projects/{projectId}` | Get a project by ID |
| PUT | `/projects/{projectId}` | Update a project |
| GET | `/tasks` | List all tasks |
| POST | `/tasks` | Create a new task |
| GET | `/users` | List users in the workspace |
| GET | `/proofs` | List proofs / creative reviews |

## Key resources

- **Projects** — List, create, retrieve, and update creative projects
- **Tasks** — List, create, and retrieve tasks within projects
- **Users** — List users in the Lytho workspace for assignment and reviewer lookup
- **Proofs** — List creative review and approval records

## Why Jentic

- **Setup:** Wiring the Lytho (InMotionNow) API by hand means learning its bearer auth and mapping its project, task, and proof endpoints on the api.lytho.com host yourself. Through Jentic you install once, import the Lytho (InMotionNow) API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Lytho puts the project id in the URL path (`/projects/{projectId}`), so a rule can pin your agent to reading and updating one project. You choose the operations it may call, so creating projects or tasks is not included unless you add them.
- **Credential handling:** Your Lytho bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a creative project' or 'list proofs awaiting review', and Jentic returns the matching Lytho operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana API** — Asana is a general-purpose work management platform; Lytho is purpose-built for creative review workflows.
- **monday.com API** — monday.com is a flexible work-OS that can model creative workflows but lacks Lytho's native proofing.
- **Smartsheet API** — Smartsheet is often used for project rollups across teams that include creative.

## FAQ

### Why is there no official OpenAPI spec for Lytho (InMotionNow) API?

Lytho does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lytho (InMotionNow) API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### 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.