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

Siemens PLM Test Records API

The Test Records API from Siemens PLM — 4 operation(s) for test records.

Siemens PLM Test Records API is one of 51 APIs that Siemens PLM publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Test Records. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, authentication docs, and a changelog.

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

Requests are made against a single base URL, https://example.com/polarion/rest/v1.

10 operations 4 paths 12 schemas 2 DELETE4 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://developer.siemens.com
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

Siemens PLM Test Records API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 10

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

Test Records 10
GET
/projects/{projectId}/testruns/{testRunId}/testrecords
Returns a list of Test Records.
getTestRecords 10 params → 2004004014034044064XX-5XX500
PATCH
/projects/{projectId}/testruns/{testRunId}/testrecords
Updates a list of Test Records.
patchTestRecords 2 params body → 204400401403404409413415
POST
/projects/{projectId}/testruns/{testRunId}/testrecords
Creates a list of Test Records.
postTestRecords 2 params body → 201400401403404406409413
DELETE
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}
Deletes the specified Test Record.
deleteTestRecord 5 params → 2044004014034044094XX-5XX500
GET
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}
Returns the specified Test Record.
getTestRecord 8 params → 2004004014034044064XX-5XX500
PATCH
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}
Updates the specified Test Record.
patchTestRecord 5 params body → 204400401403404409413415
GET
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}/testparameters
Returns a list of Test Parameters for the specified Test Record.
getTestRecordTestParameters 10 params → 2004004014034044064XX-5XX500
POST
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}/testparameters
Creates a list of Test Parameters for the specified Test Record.
postTestRecordTestParameters 5 params body → 201400401403404406409413
DELETE
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}/testparameters/{testParamId}
Deletes the specified Test Parameter for the specified Test Record.
deleteTestRecordTestParameter 6 params → 2044004014034044094XX-5XX500
GET
/projects/{projectId}/testruns/{testRunId}/testrecords/{testCaseProjectId}/{testCaseId}/{iteration}/testparameters/{testParamId}
Returns the specified Test Parameter for the specified Test Record.
getTestRecordTestParameter 9 params → 2004004014034044064XX-5XX500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are sparseFields (45 properties), testrecordsListGetResponse (4 properties), testparametersListGetResponse (4 properties), testparametersSingleGetResponse (3 properties). Each schema is shown below with its type and property counts.

testrecordsListPostRequest
object
1 property
errors
object
1 property
sparseFields
object
45 properties
testparametersListPostResponse
object
1 property
testparametersListGetResponse
object
4 properties
testrecordsListPostResponse
object
1 property
testrecordsListGetResponse
object
4 properties
testrecordsSingleGetResponse
object
3 properties
testparametersSingleGetResponse
object
3 properties
testrecordsSinglePatchRequest
object
1 property
testrecordsListPatchRequest
object
1 property
testparametersListPostRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

siemens-plm-test-records-api-openapi.yml Raw ↑

Other APIs Siemens PLM publishes across the network.

Insights Hub and Industrial IoT APIs
SiGREEN API
Siemens PLM Account API
Siemens PLM Administration API
Siemens PLM Basic API
Siemens PLM Collections API
Siemens PLM Custom Fields API
Siemens PLM Customer Information: API Key API
Siemens PLM Document Attachments API
Siemens PLM Document Comments API
Siemens PLM Document Parts API
Siemens PLM Documents API
Where this information came from

This is an independent, third-party profile of Siemens PLM Test Records 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.