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

Physna Collections API

The Collections API from Physna — 13 operation(s) for collections.

Physna Collections API is one of 8 APIs that Physna publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Collection. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 16 operations across 13 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 2.0.1.

Requests are made against a single base URL, /v2.

16 operations 13 paths 28 schemas 2 DELETE6 GET2 PATCH5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.1
Base URL
https://api.physna.com/v2
Authentication
OAuth 2.0
Contact
Resource Areas
1

Authentication & Security 1

Physna Collections API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (okta) using the authorizationCode flow, exposing 3 scopes.

Paths & Operations 16

Across 13 paths, the API surfaces 16 operations — 2 DELETE, 6 GET, 2 PATCH, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Collections 16
POST
/collections
IN DEVELOPMENT
CreateCollection 2 params body → 200503
DELETE
/collections
IN DEVELOPMENT
BulkDeleteCollection 2 params → 200503
GET
/collections
IN DEVELOPMENT
GetCollectionsList 6 params → 200503
POST
/collections/create
IN DEVELOPMENT
BulkCreateCollection 1 param body → 200503
GET
/collections/collection/{name}
IN DEVELOPMENT
GetCollectionByName 2 params → 200503
GET
/collections/tags
IN DEVELOPMENT
GetCollectionTags 1 param → 200503
POST
/collections/{id}/add
IN DEVELOPMENT
AddToCollection 3 params → 200404503
POST
/collections/{id}/remove
IN DEVELOPMENT
RemoveFromCollection 3 params → 200404503
GET
/collections/{id}/content
IN DEVELOPMENT
GetCollectionContent 4 params → 200503
POST
/collections/{id}/reprocess
IN DEVELOPMENT
ReprocessCollection 2 params → 200503
PATCH
/collections/{id}/name
IN DEVELOPMENT
UpdateCollectionName 2 params body → 200503
PATCH
/collections/{id}/tag
IN DEVELOPMENT
UpdateCollectionTag 2 params body → 200503
GET
/collections/{id}/matches
GetCollectionMatches 5 params → 200503
GET
/collections/{id}
IN DEVELOPMENT
GetCollections 2 params → 200503
DELETE
/collections/{id}
IN DEVELOPMENT
DeleteCollections 2 params → 200503
PUT
/collections/{id}/metadata/{metadataKeyId}
UpsertCollectionMetadata 3 params body → 200

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Model (15 properties), CollectionWithMetadata (6 properties), GetCollectionMatchesResponseBody (5 properties), ModelGeometry (5 properties). Each schema is shown below with its type and property counts.

CreateCollectionResponseBody
object
2 properties 2 required
CollectionMatchResult
object
2 properties 1 required
GetCollectionTagsResponseBody
object
1 property 1 required
GetCollectionContentResponseBody
object
4 properties 4 required
GetCollectionsListResponseBody
object
4 properties 4 required
UpdateCollectionNameResponseBody
object
1 property 1 required
AddToCollectionResponseBody
CollectionMetadata
object
4 properties 4 required
UpdateCollectionTagResponseBody
object
1 property 1 required
UpdateCollectionTagRequestBody
object
1 property 1 required
FilterExpression
string
A string in the form ( ( ))[,FilterExpressions]. See the [API Reference](https://physna.github.io/public-api-guide/api-reference/filter-expressions) for more d…
MetadataFilterData
object
3 properties 3 required
CollectionWithMetadata
object
6 properties 1 required
Model
object
15 properties 10 required
GetCollectionResponseBody
ModelGeometry
object
Model geometry of ingested model, including the model's bounding box lengths, it's surface area, and volume.
5 properties 5 required
SingleMetadataResponse
object
1 property 1 required
DeleteCollectionsResponseBody
object
1 property 1 required
ErrorResponse
object
1 property 1 required
Label
object
4 properties 3 required
GetCollectionMatchesResponseBody
object
5 properties 5 required
Pick_Collection.id-or-name_
object
From T, pick a set of properties whose keys are in the union K
2 properties 1 required
BulkCreateCollectionResponseBody
object
1 property 1 required
Metadata
object
4 properties 4 required
UpdateCollectionNameRequestBody
object
1 property 1 required
ReprocessCollectionResponseBody
object
1 property 1 required
RemoveFromCollectionResponseBody
CollectionFilterData
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

physna-collections-api-openapi.yml Raw ↑

Other APIs Physna publishes across the network.

Physna ClientCredentials API
Physna Deprecated API
Physna Folders API
Physna Image Search API
Physna Metadata API
Physna Models API
Physna Users API
Where this information came from

This is an independent, third-party profile of Physna Collections 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.