From the documentation at git-scm, there are two git stash commands that mention relevance to scripting, but not general use:
Create a stash (which is a regular commit object) and return its object name, without storing it anywhere in the ref namespace. This is intended to be useful for scripts. It is probably not the command you want to use; see "save" above.
Store a given stash created via git stash create (which is a dangling merge commit) in the stash ref, updating the stash reflog. This is intended to be useful for scripts. It is probably not the command you want to use; see "save" above.
git stash create
git stash store
git stash save
You can use
git stash create when you're writing scripts that need to stash as an implementation detail and you don't want to disturb the user's stash reflog.
Depending on what happens next, you might (in the case of error, say) decide you do want to disturb the stash reflog after all, at which point you can use
git stash store.
Obviously a regular stash can be implemented in terms of
store, but I can also imagine it being used in a hypothetical
update-branch command that does something like this:
git stash create git fetch git rebase git stash apply