If your team ships software, you are producing a steady pile of files at the end of every build: packages, libraries, container images, installers. Somebody has to keep track of which version is which, who is allowed to download it, and which build is actually ready to go out the door. Doing that by hand, or in a shared folder, breaks down fast. JFrog Artifactory is built to hold all of it in one place, and it does the work through an API, which means your build tools, your scripts, or an AI assistant can store, find and promote those files for you. You can see the full profile on APIs.io.
What JFrog Artifactory does
JFrog describes Artifactory as a universal artifact repository manager. An “artifact” is just the finished output of a build, the thing you actually install or deploy. Artifactory supports the major package formats and build tools, including Maven, Gradle, npm, NuGet, PyPI, Docker, Helm, RubyGems and CocoaPods, and it sits at the center of the wider JFrog Platform. It plugs into continuous integration and delivery pipelines (CI/CD, the automated systems that build and ship code) through plugins for Jenkins, GitHub Actions, CircleCI and others. You can learn more on the JFrog website.
What you can get done
APIs.io maps Artifactory to 4 business capabilities. Here is what each one means for your business.
Package Registries & Distribution
This is the heart of it: a single, controlled place to publish the things your team builds and to pull down the things it depends on, container images included. Instead of hunting for the right file, everyone gets the same approved version from the same place.
PUT /{repoKey}/{itemPath}uploads (deploys) a file into a repository.GET /{repoKey}/{itemPath}downloads a stored file.GET /api/storage/{repoKey}/{itemPath}reads the details about a file or folder.POST /api/copy/{srcRepoKey}/{srcItemPath}copies a file to another location;POST /api/move/{srcRepoKey}/{srcItemPath}moves it.GET /v2/{name}/manifests/{reference}fetches a container image’s manifest, the description of what is inside it.
Identity & Access Management
Not everyone should be able to publish or delete your software. This capability lets you manage who has an account and which groups they belong to, so access follows your org chart instead of a shared password.
GET /api/security/userslists the people with accounts.PUT /api/security/users/{username}creates or replaces a user.DELETE /api/security/users/{username}removes a user when they leave.GET /api/security/groupslists groups, andGET /api/security/groups/{groupName}shows one group’s details.
Continuous Integration Management
Every build leaves a record: what went into it, what came out, and when. Keeping those records lets you answer the question “what exactly did we ship?” and clean up old builds on a schedule so storage does not grow forever.
PUT /api/buildpublishes the information about a finished build.GET /api/build/{buildName}lists the runs of a build.GET /api/build/{buildName}/{buildNumber}reads the details of a single run.POST /api/build/retention/{buildName}sets how long old builds are kept.DELETE /api/build/{buildName}deletes a build record.
Software Release & Deployment Management
Most teams move software through stages, such as development, testing and production. Promotion is the step where a build is approved to move forward, and doing it through the API means the approval is recorded and repeatable.
POST /api/build/promote/{buildName}/{buildNumber}promotes a build to the next repository stage.
Workflows that put it together
A workflow is a recipe: several API calls run in a set order to finish a whole job. APIs.io lists 18 Arazzo workflows for Artifactory; here are some of them.
- Deploy, Tag, and Search Artifact uploads a file, labels it with properties, then finds it again by those labels.
- Compare Build Versions confirms a build exists and shows what changed since an earlier one.
- Create User and Verify Membership sets up a group, adds a new person to it, and reads them back to confirm.
- Create Group-Scoped Access Token creates a group and issues an access key limited to it.
- Configure Repository Replication creates a repository and schedules copies of it to another location.
- Checksum Search and Retrieve finds a file by its fingerprint and reads where it lives.
- AQL Find and Delete Artifact searches with Artifactory’s query language and removes the first match.
- Decommission Repository checks a repository’s settings, confirms it exists, then deletes it.
Getting started
Artifactory is a paid, hosted service: you call JFrog’s endpoint with your own credentials. Plans start with Pro at $50/ Month; see the pricing section on APIs.io for the details. Start with JFrog’s guide to authentication, then the Artifactory Query Language docs for searching what you have stored.
On APIs.io you can browse the Artifacts & Storage API, the Build Promotion API, the AQL Search API and the Replication API, or start from the JFrog Artifactory profile.
If your builds already land in a dozen places, pick one pipeline, point it at Artifactory, and let the API keep the record for you.
