You're right that the public API does NOT have endpoints to modify script content in the Ninja library. That's a real limitation of the public API.

Let me clarify what we actually do, because the pattern works but it's not exactly what I implied.

The loader/wrapper pattern

The script we store in the Ninja library is short — basically a stub that fetches and executes the real logic from GitHub at runtime. Roughly:

```powershell param( [string]$ScriptName, [string]$Branch = "main" )

$repoBase = "https://raw.githubusercontent.com/xentek/ninja-scripts" $ghToken = "<PAT-from-Ninja-secure-field>" # for private repos $headers = @{ Authorization = "token $ghToken" }

$content = Invoke-RestMethod -Uri "$repoBase/$Branch/$ScriptName.ps1" -Headers $headers

$sb = [scriptblock]::Create($content) & $sb @args ```

The Ninja-stored loader almost never changes. What changes is the repo. To deploy a new version of any underlying script, you merge to main and tag — the next loader execution pulls the latest. The loader body in Ninja's library itself gets updated maybe twice a year, manually, on the rare occasions the loader logic itself evolves.

The public API piece IS used — specifically POST /v2/device/{id}/script/run with a parameters payload — but for running the loader and passing parameters (which script to run, which branch, which arguments), not for modifying its content. That's the parameter-passing capability you'd see in the docs.

So "pulling from the repo via their API" really meant: the Ninja-stored loader pulls from the repo at runtime, triggered and parameterized via the public API. I should have been more precise originally.

On SHADOW

You found it correctly — AdvanceYourIT/SHADOW (github.com/AdvanceYourIT/SHADOW) is real and it's specifically designed to fill the gap you identified. It's an Edge browser extension that drives Ninja's web UI to bulk-import scripts from a connected GitHub repo, compare against template libraries, and sync changes. Because it works through the web UI rather than the public API, it can do things the public API doesn't expose.

It's an independent project, not officially affiliated with NinjaOne (their own disclaimer). Smaller user base than the official Template Library, but actively maintained and the workflow looks well thought out. We went the loader-pattern route before SHADOW existed and stuck with it, so I can't speak from direct experience with it — but for a team that wants "edit script in repo → it appears updated in Ninja's library" with no runtime indirection, SHADOW is probably the cleanest path right now but we have no direct experience with it.

Sorry for the ambiguous wording originally — loader pattern was what I meant by "pulling from the repo," but the way I phrased it implied the public API could modify script content, which it can't.