How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
JFrog

JFrog Permissions API

Permission target management

Documentation Provider Profile APIs.io OpenAPI GitHub

JFrog Permissions API is one of 53 APIs that JFrog publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Permissions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, an API reference, and an engineering blog.

This API exposes 10 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.x.

Requests are made against 4 base URLs: https://{server}.jfrog.io/access, https://{host}/access, https://{server}.jfrog.io, https://{host}.

10 operations 4 paths 2 schemas 2 DELETE4 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.x
Base URL
https://myserver.jfrog.io/artifactory/api
Authentication
HTTP Bearer, HTTP Basic
Contact
JFrog
License
Proprietary
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

JFrog Permissions API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • bearerAuth — Access token authentication
  • basicAuth — Basic username/password authentication

Paths & Operations 10

Across 4 paths, the API surfaces 10 operations — 2 DELETE, 4 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Permissions 10

Permission target management

GET
/api/v2/permissions
JFrog List Permissions
listPermissions → 200
POST
/api/v2/permissions
JFrog Create Permission
createPermission body → 201400409
GET
/api/v2/permissions/{permissionName}
JFrog Get Permission
getPermission 1 param → 200404
PUT
/api/v2/permissions/{permissionName}
JFrog Update Permission
updatePermission 1 param body → 200404
DELETE
/api/v2/permissions/{permissionName}
JFrog Delete Permission
deletePermission 1 param → 204404
GET
/access/api/v2/permissions
JFrog List Permissions
listPermissions → 200
POST
/access/api/v2/permissions
JFrog Create Permission
createPermission body → 201
GET
/access/api/v2/permissions/{permissionName}
JFrog Get Permission
getPermission 1 param → 200
PUT
/access/api/v2/permissions/{permissionName}
JFrog Update Permission
updatePermission 1 param body → 200
DELETE
/access/api/v2/permissions/{permissionName}
JFrog Delete Permission
deletePermission 1 param → 204

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Permission_2 (2 properties), Permission (2 properties). Each schema is shown below with its type and property counts.

Permission
object
2 properties 1 required
Permission_2
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jfrog-permissions-api-openapi.yml Raw ↑

Other APIs JFrog publishes across the network.

JFrog Access Tokens API
AE Profile APIs.io
JFrog Artifacts & Storage API
AE Profile APIs.io
JFrog Audit API
AE Profile APIs.io
JFrog Builds API
AE Profile APIs.io
JFrog Commands API
AE Profile APIs.io
JFrog Components API
AE Profile APIs.io
JFrog Deployments API
AE Profile APIs.io
JFrog Device Groups API
AE Profile APIs.io
JFrog Devices API
AE Profile APIs.io
JFrog Distribution API
AE Profile APIs.io
JFrog Evidence API
AE Profile APIs.io
JFrog Execution API
AE Profile APIs.io
#Permissions
← Back to J APIs
API Details
ID
jfrog:jfrog-permissions-api
Base URL
https://myserver.jfrog.io/artifactory/api
Docs
https://jfrog.com/artifactory/
Provider
JFrog
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=jfrog-permissions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/jfrog-permissions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of JFrog Permissions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.