Skip to main content

Acumatica ERP - GitOps CLI

acu configures Acumatica ERP from YAML files in a git repo (GitOps).

No UI clicks, no Configuration Wizard.

Tested against Acumatica ERP 26.101.0225 on Windows Server 2025, contract REST endpoint 25.200.001. Other versions will likely work, but only this combination is verified.

Why

Acumatica configuration normally lives in the web UI: wizards, screens, and manual data entry that nobody can review, version, or reproduce.

acu moves that configuration into YAML files in a git repo, so a tenant can be rebuilt from scratch, audited in a pull request, and checked for drift like any other infrastructure.

What this tool is capable of

YAML in git is the source of truth; the live tenant is the target. apply is the only writer.

You can Command Effect
Seed a tenant from YAML apply Idempotent PUT of acu-config/ into the live tenant
Detect drift diff Compare seed YAML to live (exit 2 when they diverge)
Pull live config into YAML survey extract Inverse of apply — GET into acu-config/{bootstrap,baseline,setup,master}/
Run transaction scripts run Forward documents from acu-scenario/ (capital, buy, build, sell, migrated AR/AP/IN documents)
Capture derived balances state Inquire trial-balance etc. into state/ (not seed)
Create and destroy tenants tenant SSH control plane: list / create / delete / recycle
Publish the Bootstrap contract bootstrap REST publish of AcuBootstrap (or --export zip for the UI)
Prove a cold rebuild tenant create then apply then run then diff Compose on a fresh tenant. No wrap command.
Snapshot a site offline survey inventory SM203520 XML ZIP or ac.exe export xml writes inventory/
Cross-check snapshot vs seed survey reconcile inventory/ plus optional --config writes findings/ only
Dump the contract schema schema OpenAPI swagger.json for the pinned endpoint
Scaffold a data repo config init Full acu-config/, acu-scenario/, .env tree
Preflight a target config check Discovery, secrets, REST, endpoints, SSH

Seed YAML covers features, company, credit terms, subaccounts, chart of accounts, ledger, UOMs, financial year / calendar / periods, numbering sequences, inventory and distribution masters, roles, and users.

REST is the data plane (apply, diff, run, survey extract, state, bootstrap, schema). SSH is the control plane (tenant *).

Hosted sites skip SSH.

Quick start

uv tool install acumatica-cli

acu config init --host erp.example.com my-erp
cd my-erp                                # edit .env: ACU_PASSWORD, ACU_TENANT
                                         # ACU_BASE_URL is where; ACU_API_VERSION pins Default
                                         # start from a brand-new empty tenant

acu config check                         # read-only preflight
acu tenant create --login DEV            # create + bootstrap (SSH; --id optional)
# or hosted: acu --tenant DEV bootstrap
acu --tenant DEV apply acu-config        # seed acu-config/{bootstrap,baseline,setup,master}/
acu --tenant DEV run acu-scenario        # once capital → buy → build → sell
acu --tenant DEV diff acu-config         # prove zero drift (exit 2 on drift)
acu --tenant DEV state acu-config/views  # capture state/ trial-balance

apply / diff / run / state require an explicit data path.

Hosted Acumatica (no SSH): the tenant already exists; set a blank ACU_SSH= in .env. The scaffold omits the key — without it, acu defaults to Administrator@<ACU_BASE_URL host> for SSH boxes.

acu config init --host customer.acumatica.com my-erp
cd my-erp                                # edit .env: ACU_TENANT, ACU_PASSWORD; add ACU_SSH=
acu config check                         # REST preflight; ssh probe is skipped
acu --tenant DEV bootstrap               # publish AcuBootstrap via REST only
acu --tenant DEV apply acu-config
acu --tenant DEV diff acu-config
# offline UI fallback when REST publish is blocked:
acu bootstrap --export AcuBootstrap.zip  # import + publish on SM204505

CLI map

acu [--tenant NAME] [--url URL] [--ssh USER@HOST] [--api-version V]
    [--username U] [--password P] [--version] [--completion [SHELL]]
│
├── tenant                            tenant CRUD (ac.exe over SSH — control plane)
│   ├── list                          CompanyID, sign-in name, internal CD, type
│   ├── create --login NAME [--id N]  create + bootstrap; re-run to republish (SSH)
│   │          [--type SalesDemo|T100|U100] [--parent N] [--hidden] [--no-init]
│   │                                 omit --id → next free CompanyID (max list + 1)
│   ├── delete --id N | --login NAME [--yes]
│   │                                 delete the tenant and its data, recycle app pool
│   └── recycle [--yes]               restart site app pool (tenant map + free API slots)
│
├── bootstrap [--export PATH]         publish AcuBootstrap (REST); --export = offline zip
├── apply [--dry-run] <FILES...>      push YAML via REST (idempotent PUT upserts)
│         [--plan|--changed-only] [--concurrency N] [--checkpoint PATH]
├── diff  <FILES...>                  drift check vs the live tenant (exit 2 on drift)
├── run   [--dry-run] <FILES...>      execute transaction scenario YAML (exit 1 on any miss)
│         [--concurrency N] [--checkpoint PATH]
├── state [--out DIR] [--diff] [--assert-unchanged] [--dry-run] <FILES...>
│                                     capture derived state into state/ (not seed)
├── survey                            existing-tenant dual-reader (never L1 extract/inventory/reconcile)
│   ├── extract [--out DIR] [--only NAME]... [--force] [--dry-run]
│   │                                 inverse of apply into acu-config/{bootstrap,baseline,setup,master}/
│   ├── inventory [--out DIR] [--force] [--dry-run] ARTIFACT
│   │                                 offline snapshot artifact → inventory/ (not seed)
│   └── reconcile [--inventory DIR] [--config DIR] [--out DIR] [--force] [--dry-run]
│                                     inventory/ + optional --config DIR → findings/ only
├── schema [--out DIR]                dump the endpoint's OpenAPI schema (swagger.json)
│
└── config                            configuration ops
    ├── init [--host HOST] [DIR]      scaffold full data repo (acu-config/, acu-scenario/, .env)
    ├── show                          print the resolved config as a complete .env
    └── check                         preflight: discovery, secrets, REST, endpoints, SSH

apply / diff / run / state require an explicit data path. Zero args print that command's help and do not call HTTP.

A dir with SEED_DIRS children (bootstrap|baseline|setup|master) expands those subdirs in that order. Typed path is used as given (acu apply acu-config, or acu apply config/ if that dir exists).

--out defaults: state → state/; survey extract → acu-config/ (SEED_DIRS into that root); survey inventory → inventory/; survey reconcile → findings/; schema → schemas/.

Scenario YAML may use ${current_period} (host-local MMyyyy) on steps, expect params, and once.present params.

A scenario file may hold many scenarios split by --- (a generated load: one YAML document per ERP document, reported as <file>#<n>). Guard each with its external reference so a re-run creates nothing twice:

---
scenario: so-LEGACY-1042
once: true
present:
  get: { entity: SalesOrder, filter: "CustomerOrder eq 'LEGACY-1042'" }
steps:
  - id: order
    put: SalesOrder
    record: { OrderType: SO, CustomerID: C0042, CustomerOrder: LEGACY-1042 }

acu-config/views and state keep Period pinned.

Bulk loads (thousands of records or documents) take two flags on apply and run:

  • --concurrency N opens N sessions before the first write and spreads one file's records (apply) or documents (run) across them. Each session takes one API-user license slot; if a login is refused, acu logs out the open sessions and exits 1 with nothing written. Files stay in order. Company and action files, and scenario files with an inquire delta expect, stay serial.
  • --checkpoint PATH appends one JSON line {tenant, unit, digest} per record, action or scenario done, flushed at once. Re-run the same command after a killed load and acu skips what is done on that tenant (skip <unit> (checkpoint)); a record whose content changed is applied again. A scenario's key includes its file name and document number, so renaming the file or inserting a document ahead of it runs it again. Not valid with --plan or --dry-run; a malformed line exits 1 before login.
acu --tenant DEV apply --concurrency 4 --checkpoint load.jsonl data/

survey extract writes SEED_DIRS into --out (default acu-config/).

survey inventory and survey reconcile are offline (no REST, SSH, or password). survey inventory turns an SM203520 Settings XML ZIP or ac.exe export xml folder into inventory/.

survey reconcile compares inventory/ to optional --config DIR and writes findings/ only. It never writes seed.

Optional snapshot_map.yaml (data-repo root, or package defaults) maps DAC tables to catalog entities. It normalizes the join: pad-trim, key/field aliases, Account/Sub FK CD resolve, enum label to code.

acu --completion emits a completion script for bash, zsh, or fish — source it from your shell profile.

Run acu --help for the full mental model (workflow, planes, exit codes, command map). That is enough for an agent to learn the tool without extra docs.

Run acu <command> --help (or -h) for flags, examples, and prerequisites.

Dual readers, one writer

Two read paths, one mutator (V35). Do not confuse them with each other or with state:

Command Plane Input Writes Role
survey extract REST (live) tenant via contract API acu-config/{bootstrap,baseline,setup,master}/ Inverse of apply — seed YAML
survey inventory Offline SM203520 Settings XML ZIP or ac.exe export xml folder inventory/ (summary.yaml + tables/) Full-table snapshot IR — not seed
survey reconcile Offline inventory/ + optional --config DIR findings/ only Cross-check gaps/deltas — never mutates seed or tenant
state REST (live) acu-config/views/ state/ Derived balances/totals — not seed, not inventory
apply REST (live) seed YAML under acu-config/ tenant Sole tenant writer (keyed PUT)

inventory/ and findings/ are engagement outputs: not SEED_DIRS, never loaded by apply/diff, not scaffolded by config init. Binary .adb snapshots are rejected (XML only).

Machine-readable output (--output json)

acu --output json <diff|apply|run|state> ... prints one JSON document on stdout; progress and result lines move to stderr. Exit codes do not change (diff still exits 2 on drift), and other commands ignore the flag.

diff:

{
  "command": "diff", "tenant": "DEV", "base_url": "https://...", "drift": 1,
  "files": [{
    "file": "acu-config/baseline/10-uoms.yaml", "entity": "UnitsOfMeasure",
    "records": 2,
    "drifts": [{
      "file": "acu-config/baseline/10-uoms.yaml", "entity": "UnitsOfMeasure",
      "keys": {"UOM": "KG"}, "field": "Description", "kind": "changed",
      "source": "Kilogram", "live": "kg",
      "text": "UnitsOfMeasure [KG].Description: source='Kilogram' live='kg'"
    }]
  }]
}
  • kind: changed, missing, extra (detail row), not_returned or not_applied (setup action).

  • field: path below the record (e.g. Details[A].Qty); "" when the record itself is missing.

  • source / live: set only for changed.

  • apply: {command, tenant, mode (all|plan|changed|dry_run), ok, failed, counts, errors, stopped, not_applied, files: [{file, entity, ok, errors}]}; counts keys create, update, unchanged, invoke, put; with --checkpoint, counts.checkpoint and top-level checkpoint = units skipped from the file.

  • run: {command, tenant, counts: {passed, failed, skipped, not_run}, scenarios: [{file, doc?, outcome, misses, error?}], not_run}; doc = 1-based YAML document index in a multi-document file; not_run lists <file> or <file>#<n>; misses = failed expectation lines; with --checkpoint, counts.checkpoint = scenarios skipped from the file and those entries carry checkpoint: true.

  • state: {command, tenant, mode (write|diff|assert), exit, changed, views: [{view, file, rows, status (wrote|changed|unchanged), differences}]}.

The data repo

Your configuration lives in its own git repo. acu config init scaffolds a single full seed under acu-config/ (features, company, credit terms, expanded COA, masters) plus lifecycle acu-scenario/, observer acu-config/views/, and README.

It does not write a customization tree.

The Bootstrap endpoint contract is package SoT (bootstrap_project.xml inside the CLI — Bootstrap/1.13.0). config init never writes project.xml, and data repos must not keep one (a present file hard-errors on bootstrap/publish).

There is no --flavor.

Path What it holds
acu-config/bootstrap/ virgin-tenant config: features, company, credit terms (no project.xml)
acu-config/baseline/ reference data: subaccounts, COA, ledger, UOMs
acu-config/setup/ one-time actions: financial year, master calendar, open periods
acu-config/master/ inventory/distribution masters: numbering (05-…) before prefs, warehouse, items, parties, tax chain (76-tax-reporting, 77-taxes, 78-tax-zones), non-stock items (81-…) + Role/User (90-roles then 91-users then 92-role-users)
acu-scenario/ lifecycle txns for acu run: once capital, then buy, build, sell; migration documents (50-ar-documents, 60-ap-documents, 70-inventory-receipt), one once-guarded scenario per document
acu-config/views/ observer views for acu state (inquire: / entity: / gi:; not SEED_DIRS)
state/ committed derived-state observations (evidence, not seed; money/qty fixed-point)
inventory/ engagement: offline snapshot tables from acu survey inventory (not seed; not SEED_DIRS)
findings/ engagement: acu survey reconcile cross-check output (never apply path)
.env secrets + where (ACU_BASE_URL) + pin (ACU_API_VERSION)

Files in each directory apply alphabetically; the numbered prefixes (10-, 20-, and so on) encode dependency order.

A file can also name what it needs first with depends_on: (see Seed depends_on:). Commit seed YAML; keep .env out of git (scaffold .gitignore already lists it).

Seed YAML is state: apply upserts it, diff proves it. acu survey extract is the inverse of apply: GET live tenant rows into seed YAML under acu-config/{bootstrap,baseline,setup,master}/ (hard-cut).

Packaged seed_catalog.yaml is the sole extract registry (entity, endpoint, keys, file, strip/include, filter-split). A row marked template: false extracts a CLI test-seed file that config init never scaffolds (external file storage).

Features synthesize to acu-config/bootstrap/features.yaml. Existing files skip unless --force; empty live sets skip.

Row failures continue (exit 1 only if any row failed). Drift stays with diff.

acu --tenant DEV survey extract --force           # refresh acu-config/** from live tenant
git diff acu-config/                           # review extract delta before commit
acu --tenant DEV apply acu-config             # replay extracted seed
acu --tenant DEV diff acu-config              # expect exit 0

Acumatica API limits

Seed and scenario templates work around these contract-API limits (live-verified on Default/25.200.001, 26r1):

Limit Workaround
A SalesInvoice of type Finance Charge (or Overdue Charge) cannot be created through the contract API: PUT answers 500 "Index was outside the bounds of the array". Finance charges come only from the AR overdue-charge process. 50-ar-documents.yaml loads a migrated finance charge as a Debit Memo with an income account line.
The list GET returns Tax TaxSchedule.ReportingGroup as a per-tenant group id ('1'), while the single-record GET returns the group name. The CLI reads Tax one record at a time by key, so seed holds the group name and diff compares names.
A Tax schedule row needs a reporting group (422 "'Reporting Group' cannot be empty"). 76-tax-reporting.yaml sorts before 77-taxes.yaml.
External File Storage (SM202540) detail arrays (Settings, FilesInDatabase) come back empty ([]) on GET and PUT with $expand, so a Settings detail write does nothing. $custom reaches only the current row. Bootstrap ExternalFileStorage maps a top-level LocalFolder to the current settings row.
SM202540 Provider reads back as the UI label Local File Folder; the database stores PX.SM.PXBlobStorageFileProvider. Seed holds the label; PUT accepts it.
SM202540 lists System-tenant files (CompanyID 1, shared through CompanyMask) in each tenant's database-files grid. CompanyID is not a DAC field, so the API cannot filter them out. Move Files to Storage is not exposed; files stored before the switch stay in the database.

Seed endpoint: symbols

Dual-served entities (on both Bootstrap and Default) need an explicit endpoint: line.

Value Resolves to
omitted Default/<api_version> for Default-only entities
bootstrap active Bootstrap/<ver> from the packaged contract only
default Default/<api_version> — tracks the resolved API version
Bootstrap/1.4.0 or Default/25.200.001 literal pin (ignores the resolved Default version)

api_version resolves as --api-version flag, else ACU_API_VERSION in .env, else code default 25.200.001. base_url resolves as --url, else ACU_BASE_URL (required).

Prefer symbolic default over a pinned Default/25.200.001 so the seed tree travels with the dataset pin.

Seed depends_on:

Any seed file (records or action) may list the files that must run before it. Paths are relative to the seed-tree root, the directory that holds bootstrap/, baseline/, setup/ and master/:

entity: Customer
key: CustomerID
depends_on: [master/77-taxes.yaml]
records:
  - CustomerID: C001

apply and diff (including --plan, --changed-only and --dry-run) run files in a stable topological order over depends_on. Files with no constraint keep the directory order (SEED_DIRS, then alphabetical), so a tree without depends_on runs exactly as before.

When a dependency sorts later, the file that declares it moves down; the dependency stays where it was.

These stop the run with exit 1 before any session opens, listed with any other seed-file errors:

  • a depends_on entry that names no file
  • a cycle, printed as depends_on cycle: a.yaml -> b.yaml -> a.yaml
  • depends_on in a file outside a seed directory

A named file that exists but is not in this run is not pulled in for you. The run prints a warning and assumes it is already applied, so acu diff acu-config/master/90-roles.yaml or re-running a stopped run's not applied: files still works.

--concurrency is unchanged: files still run one after another. survey extract does not write depends_on, so --force re-extract drops it from that file.

Installation

Requires Python 3.14 or newer.

uv tool install acumatica-cli

pipx install acumatica-cli and pip install acumatica-cli work too.

Or clone and install editable for development:

git clone https://github.com/kborovik/acumatica-cli.git
cd acumatica-cli
gmake install    # uv sync; does not replace the PyPI tool

Verify with uv run acu --version (+dev).

Configuration

Secrets, REST where, and the Default contract pin live in one .env file (ACU_* vars). Leftover matrix.yaml is ignored and never loaded.

ACU_BASE_URL=http://erp.example.com/AcumaticaERP        # REST where (required)
ACU_API_VERSION=25.200.001                              # Default contract half
ACU_TENANT=LAB5                                         # sign-in name of the tenant API sessions use
# ACU_SSH omitted → defaults to Administrator@ + resolved base_url host
# ACU_SSH=                                              # hosted opt-out (blank key)
ACU_USER=admin                                          # optional, defaults to admin
ACU_PASSWORD=...                                        # required for live commands

Ad-hoc override: acu --api-version 24.200.001 … (version half only, never Default/25.200.001 — a full path would nest as /entity/Default/Default/...).

api_version resolves as --api-version, else ACU_API_VERSION, else 25.200.001. base_url resolves as --url, else ACU_BASE_URL, else a hard error naming sources.

acu config show prints the resolved .env (password excluded; includes ACU_API_VERSION).

Multi-host overlays (V44)

One trunk seed in the data repo serves every host. Version fan-out is not long-running product branches (acu-25r1, acu-26r1, …).

Piece Role
Trunk seed Canonical acu-config/ + acu-scenario/ (newest supported Default half)
.env pin Per-checkout ACU_BASE_URL + ACU_API_VERSION
Optional overlays Surgical seed deltas keyed by Default half (e.g. overlays/default-24.200.001/)
OpenAPI Live acu schema dump only (gitignored); never multi-version swagger trees in package or data repo

Overlays live under overlays/default-<api_version>/ (scaffolded by acu config init). No --overlay flag.

Pass overlay trees as extra explicit paths when you need them.

Pin = resolved api_version (--api-version, else ACU_API_VERSION, else code default).

# ACU_API_VERSION=24.200.001 — this overlay is scenario-only
acu apply acu-config
acu diff acu-config
acu run acu-scenario overlays/default-24.200.001/acu-scenario/

Add a future half by creating overlays/default-<new-half>/ with the minimal rewrite; no long-running product branches and no multi-version OpenAPI trees (V11/V44).

Sibling data-repo retirement of release branches: acumatica-gitops#2.

Worth knowing:

  • The .env file is found by walking up from the current directory, so any subdirectory of the data repo works.
  • Without a .env, global flags plus the process environment supply the configuration.
  • When ACU_SSH is absent, acu defaults to Administrator@ + the resolved base_url hostname. A present blank ACU_SSH= is the hosted opt-out. Only acu tenant requires a non-empty value post-default.
  • acu config show prints the resolved .env (password excluded).
  • Redirect it to turn resolved state into a working config: acu config show > .env.

Verify before touching anything live:

acu config check           # discovery, secrets, REST, endpoints, SSH
acu apply --dry-run        # show what would be written, write nothing

Development

Requires GNU Make at least 3.82 — the Makefile uses .ONESHELL. On macOS use Homebrew's gmake (brew install make); /usr/bin/make is 3.81 and fails the guard.

Elsewhere plain make is fine when it is GNU Make.

git clone https://github.com/kborovik/acumatica-cli.git
cd acumatica-cli
gmake install    # uv sync; does not replace the PyPI tool
gmake check      # offline gate: ruff, basedpyright strict, pytest

The default test suite is fully offline. REST is faked with httpx.MockTransport, SSH with a monkeypatched subprocess.run — no live instance is needed.

gmake check must pass before every commit. GitHub Actions runs the same gate on every push and pull request to main.

Release

Human release notes live in root CHANGELOG.md (Keep a Changelog). During development, append user-facing work under ## Unreleased in ### Added / ### Changed / ### Fixed as appropriate.

Empty Unreleased (no bullets) hard-fails the release — nothing to ship.

gmake release patch   # or minor | major

gmake release is the sole release path (never local gh release create):

  1. gmake check (ruff, basedpyright, offline pytest)
  2. Fail if ## Unreleased has no bullets
  3. Bump pyproject.toml version (major | minor | patch)
  4. Promote Unreleased body to ## [vX.Y.Z] - YYYY-MM-DD, leave an empty ## Unreleased
  5. Commit CHANGELOG.md + pyproject.toml (+ lock if bumped) together
  6. gmake check again on the promoted tree — fail keeps the commit, creates no tag, pushes nothing
  7. Tag vX.Y.Z and push branch + that tag — GitHub Actions publishes

GitHub Actions on tag v* re-runs CI, builds sdist+wheel, publishes to PyPI via OIDC trusted publishing, and creates a GitHub Release whose notes are the promoted CHANGELOG section for that tag (plus the artifacts).

Live end-to-end tier

gmake e2e runs the opt-in live tier against a real Acumatica instance (pytest marker e2e, deselected by the default suite).

Configuration is one file: a decrypted .env at the repo root names the instance — ACU_BASE_URL, ACU_TENANT, ACU_PASSWORD (and optional ACU_SSH; omitted defaults to Administrator@ + base-url host). gmake e2e refuses to start without it.

The tier is three pipeline files: provision (apply/diff), scenario (run/state), and extract round-trip. Per-bug contract probes fold onto those tenants.

Each run scaffolds a synthetic single-org company from the packaged acu config init templates into a temporary directory, copies the real .env into it, and runs the installed acu binary from there — no data repo, no pre-existing fixtures on the instance.

Scratch tenants (E2E, E2EA, E2EB, E2ESCEN) are created on the way in and always deleted on the way out, so nothing persists. The packaged full config init seed (under acu-config/) is the only scaffold.

gmake e2e                                # whole tier, three files
gmake e2e FILE=test_provision_lifecycle  # apply/diff + folded probes
gmake e2e FILE=test_scenario_lifecycle   # scenario + state + kit alloc
gmake e2e FILE=test_extract_roundtrip    # extract inverse

CLI test-seed soak

This checkout carries a CLI test seed at repo-root acu-config/ and acu-scenario/ (no customization YAML under acu-config/). Soak the live CLI tenant from here with --tenant ACUCLI.

Never use tenant CNBN. Never cd the sibling GitOps repo for CLI soak.

The test seed also turns on external file storage (acu-config/setup/40-42): a Local File Folder provider at F:\AcumaticaFiles\AcumaticaERP, then Enable Provider and Switch Direction. The folder must already exist and be writable on the server; acu never creates it.

gmake e2e still scaffolds from packaged config init templates into a tmp dir. That path is not the soak.

uv run acu --tenant ACUCLI apply acu-config
uv run acu --tenant ACUCLI run acu-scenario
uv run acu --tenant ACUCLI diff acu-config
uv run acu --tenant ACUCLI state acu-config/views

License

This project is licensed under the PolyForm Noncommercial License 1.0.0. Noncommercial use is free under that license.

Commercial use requires a separate license — contact lab5.ca.

See LICENSE and NOTICE.

Copyright 2026 Konstantin Borovik.

Metadata

Release files for acumatica-cli 0.38.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for acumatica-cli 0.38.0
File Size Uploaded Provenance Actions
acumatica_cli-0.38.0.tar.gz 163.1 kB With provenance Details for acumatica_cli-0.38.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for acumatica-cli 0.38.0
File Interpreter ABI Platform Actions
acumatica_cli-0.38.0-py3-none-any.whl Python 3 none any Details for acumatica_cli-0.38.0-py3-none-any.whl

Total release size: 343.9 kB

Release files / acumatica_cli-0.38.0.tar.gz

Download URL acumatica_cli-0.38.0.tar.gz
Size 163.1 kB
Tags Source
SHA-256 checksum
How to use checksums
946929081b0ced33e6af55b39bb22b57c1512b1be0b8237c316c2e10d8f88370
BLAKE2b-256 checksum
How to use checksums
cbc77c210703b290d29efe7b0d4342345fac4a64df6b5e4adcae442cbbbca963
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Release files / acumatica_cli-0.38.0-py3-none-any.whl

Download URL acumatica_cli-0.38.0-py3-none-any.whl
Size 180.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
92976fa64c697742626e3e2c9c1835bdac92b355853a994fb1f99deeb1e49be6
BLAKE2b-256 checksum
How to use checksums
1226cb6950bed41d7c928f50df0be2e758e69841b7b07c8f06d5ddc192f511db
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Security for acumatica-cli 0.38.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for acumatica_cli-0.38.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.38.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page