Jama Software

Jama Software is the maker of Jama Connect, a requirements management and live-traceability platform used by teams building complex products, systems, and software in regulated industries such as medical devices, automotive, aerospace and defense, semiconductor, and industrial. Jama Connect exposes a versioned REST API (v1) at https://{instance}.jamacloud.com/rest/v1/ covering items, projects, relationships, item types, baselines, test plans, test cycles, test runs, users, user groups, tags, attachments, and activities. The API supports HTTP Basic authentication and OAuth 2.0 client-credentials, ships official Python, Java, Node.js, and Ruby clients, and is documented through an interactive Swagger reference with a dated changelog and versioning policy.

Jama Software is listed with 1 API on the APIs.io network: Jama Connect REST API. Tagged areas include Company, Requirements Management, Application Lifecycle Management, Traceability, and Test Management.

The Jama Software catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Jama Software’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, signup flow, and 32 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

48.0/100 developing ▬ flat Agent 21/100 agent aware Front door AI 5/6 prominent Heartbeat 69/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 API 2 Agent Skills

Company Requirements ManagementApplication Lifecycle ManagementTraceability Test Management Product Development Systems Engineering REST API

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 48.0/100 · developing

Contract Quality 5.3 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 7.5 / 15

Operational Transparency 4.1 / 10

Contract Governance 3.0 / 9

Discoverability 5.6 / 8

Regulatory Posture 3.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/jama-software/"><img src="https://apis.io/badge/jama-software/card.svg" alt="Jama Software on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 28.0 — up to +18.0 composite points
Access Clarity scores 50.0 — up to +10.0 composite points
Contract Governance scores 33.3 — up to +8.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/jama-software/apis.yml: open an issue on github.com/api-evangelist/jama-software to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Jama Connect REST API

The Jama Connect REST API (v1) provides programmatic access to items, projects, relationships, item types, baselines, test plans, test cycles, test runs, users, user groups, tag...

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

manage-items

AGENT SKILL

trace-requirements

AGENT SKILL

Jama Software API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Jama Software Plans Pricing

0 plans

PLANS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Jama Software Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Jama Software Context

69 classes · 20 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Jama Software API Rules

12 rules · 11 errors 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetRestV1ItemsItemidResponse

1 properties

JSON SCHEMA

GetTestplansTestplanidTestgroupsResponse

2 properties

JSON SCHEMA

PatchRestV1TestrunsTestrunidRequest

3 properties

JSON SCHEMA

PostRestV1CommentsRequest

3 properties

JSON SCHEMA

PostTestplansRequest

2 properties

JSON SCHEMA

PutJamaRestV1ItemsItemidResponse

3 properties

JSON SCHEMA

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Jama Software Authentication

http/oauth2 · 2 schemes

SECURITY

Jama Software Domain Security

TLSv1.3 · DMARC

SECURITY

Jama Software Trust Center

SOC 2 Type 2, TISAX Level 2, TUV SUD (safety-related development validation), GDPR, NIST (security policy basis), OWASP (secure development practices)

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Lifecycle

Conventions

Conformance

ErrorCatalog

Scroll for all 8

Build 4

SDKs, sample code, and the tooling you integrate with

IntegrationEdges

IntegrationEdges

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 5

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Compliance

Authentication

DomainSecurity

Operate 5

Status, limits, changes, and where to get help

Support

HelpCenter

StatusPage

ChangeLog

Deprecation

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Newsroom

Newsroom

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Leadership

Leadership

Source (apis.yml)

aid: jama-software
name: Jama Software
description: Jama Software is the maker of Jama Connect, a requirements management and live-traceability platform used by
  teams building complex products, systems, and software in regulated industries such as medical devices, automotive, aerospace
  and defense, semiconductor, and industrial. Jama Connect exposes a versioned REST API (v1) at https://{instance}.jamacloud.com/rest/v1/
  covering items, projects, relationships, item types, baselines, test plans, test cycles, test runs, users, user groups,
  tags, attachments, and activities. The API supports HTTP Basic authentication and OAuth 2.0 client-credentials, ships official
  Python, Java, Node.js, and Ruby clients, and is documented through an interactive Swagger reference with a dated changelog
  and versioning policy.
url: https://raw.githubusercontent.com/api-evangelist/jama-software/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- insight-partners
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-20 (local-v5; was portfolio-lead)
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: low
  probe_state: unreadable
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.jamasoftware.com/wpg/media/sites/2/2026/01/cropped-jama-favicon-192x192.png
tags:
- Company
- Requirements Management
- Application Lifecycle Management
- Traceability
- Test Management
- Product Development
- Systems Engineering
- REST API
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/jama-software-plans-pricing.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Newsroom
  url: https://www.jamasoftware.com/media/2024/09/ice-tim-diagram.jpg
- type: Spectral
  url: rules/jama-software-rules.yml
- type: JSONLD
  url: json-ld/jama-software-context.jsonld
- type: Vocabulary
  url: vocabulary/jama-software-vocabulary.yml
- type: DataModel
  url: data-model/jama-software-data-model.yml
- type: TrustCenter
  url: security/jama-software-trust-center.yml
- type: Hosts
  url: hosts/jama-software-hosts.yml
- type: IntegrationEdges
  url: integrations/jama-software-integration-edges.yml
- type: Vendors
  url: vendors/jama-software-vendors.yml
- type: Leadership
  url: https://www.jamasoftware.com/company/leadership/
- type: Website
  url: https://www.jamasoftware.com/
- type: DeveloperPortal
  url: https://dev.jamasoftware.com/
- type: Documentation
  url: https://rest.jamasoftware.com/
- type: APIReference
  url: https://rest.jamasoftware.com/
- type: GettingStarted
  url: https://dev.jamasoftware.com/api/
- type: Blog
  url: https://www.jamasoftware.com/blog/
- type: Support
  url: https://help.jamasoftware.com/
- type: HelpCenter
  url: https://community.jamasoftware.com/
- type: Pricing
  url: https://www.jamasoftware.com/platform/pricing/
- type: SignUp
  url: https://www.jamasoftware.com/platform/jama-connect/trial/
- type: PrivacyPolicy
  url: https://www.jamasoftware.com/privacy/
- type: GitHubOrganization
  url: https://github.com/JamaSoftware
- type: StatusPage
  url: https://status.jamasoftware.com
- type: TrustCenter
  url: https://www.jamasoftware.com/trust/
- type: Compliance
  url: https://www.jamasoftware.com/trust/
- type: ChangeLog
  url: changelog/jama-software-changelog.yml
- type: Authentication
  url: authentication/jama-software-authentication.yml
- type: Packages
  url: packages/jama-software-packages.yml
- type: SDKs
  url: packages/jama-software-packages.yml
- type: LLMsTxt
  url: llms/jama-software-llms.txt
- type: Lifecycle
  url: lifecycle/jama-software-lifecycle.yml
- type: Deprecation
  url: lifecycle/jama-software-lifecycle.yml
- type: Conventions
  url: conventions/jama-software-conventions.yml
- type: Conformance
  url: conformance/jama-software-conformance.yml
- type: ErrorCatalog
  url: errors/jama-software-error-codes.yml
- type: WellKnown
  url: well-known/jama-software-well-known.yml
- type: DomainSecurity
  url: security/jama-software-domain-security.yml
apis:
- name: Jama Connect REST API
  description: The Jama Connect REST API (v1) provides programmatic access to items, projects, relationships, item types,
    baselines, test plans, test cycles, test runs, users, user groups, tags, attachments, comments, and activities in a Jama
    Connect instance. It is served per tenant at https://{instance}.jamacloud.com/rest/v1/ and supports HTTP Basic and OAuth
    2.0 client-credentials authentication.
  humanURL: https://rest.jamasoftware.com/
  baseURL: https://{tenant}.jamacloud.com/rest/v1
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/jama-software-openapi-generated.yml
    x-provenance: generated
  - type: Documentation
    url: https://rest.jamasoftware.com/
  - type: APIReference
    url: https://rest.jamasoftware.com/
  - type: GettingStarted
    url: https://dev.jamasoftware.com/api/
  - type: Authentication
    url: authentication/jama-software-authentication.yml
  - type: JSONSchema
    url: json-schema/jama-software-get-rest-v1-items-itemid-response-schema.json
  - type: JSONSchema
    url: json-schema/jama-software-patch-rest-v1-testruns-testrunid-request-schema.json
  - type: JSONSchema
    url: json-schema/jama-software-put-jama-rest-v1-items-itemid-response-schema.json
  - type: JSONSchema
    url: json-schema/jama-software-post-testplans-request-schema.json
  - type: JSONSchema
    url: json-schema/jama-software-post-rest-v1-comments-request-schema.json
  - type: JSONSchema
    url: json-schema/jama-software-get-testplans-testplanid-testgroups-response-schema.json
  aid: jama-software:jama-connect-rest-api
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  method: derived
  generated: '2026-10-20'
  generator: derive-coverage.py (pre-flight evidence)
  detail: the company publishes developer documentation but serves no machine-readable contract from it
  evidence:
  - url: https://www.jamasoftware.com/
    status: 200
x-enrichment:
  date: '2026-10-20'
  status: enriched
  artifacts_added: 14
  pass: local-v5

Jama Software API — frequently asked questions

Does Jama Software have an API?

Yes. APIs.io lists 1 API from Jama Software, including Jama Connect REST API.

Is there an OpenAPI specification for the Jama Software API?

Yes. APIs.io indexes 1 OpenAPI specification for Jama Software, each linked for download from this page.

How do I authenticate with the Jama Software API?

Jama Software uses bearer-token authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Jama Software Authentication.

Is the Jama Software API ready for AI agents?

Jama Software has a Kin Score of 48.0 out of 100 (developing) and an Agent Readiness score of 21.0 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/jama-software"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/jama-software/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/jama-software/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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