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

Pryon User Defined Metadata API

The UserDefinedMetadata API from Pryon — 9 operation(s) for userdefinedmetadata.

Pryon User Defined Metadata API is one of 24 APIs that Pryon publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include UserDefinedMetadata. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 11 operations across 9 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, /.

11 operations 9 paths 16 schemas 2 DELETE5 GET2 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.pryon.net
Resource Areas
1

Paths & Operations 11

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

UserDefinedMetadata 11
GET
/api/knowledge/v1alpha1/collections/{collection_id}/user-defined-metadata-fields
List User-Defined Metadata Fields
UserDefinedMetadata_ListUserDefinedMetadataFields 3 params → 200default
DELETE
/api/knowledge/v1alpha1/collections/{collection_id}/user-defined-metadata-fields/{user_defined_metadata_field_id}
Delete User-Defined Metadata Fields
UserDefinedMetadata_DeleteUserDefinedMetadataField 2 params → 200default
GET
/api/knowledge/v1alpha1/collections/{collection_id}/user-defined-metadata-fields/{user_defined_metadata_field_id}
Get User-Defined Metadata Fields
UserDefinedMetadata_GetUserDefinedMetadataField 2 params → 200default
GET
/api/knowledge/v1alpha1/collections/{collection_id}/user-defined-metadata-fields/{user_defined_metadata_field_id}/values
List User-Defined Metadata Field Values
UserDefinedMetadata_ListUserDefinedMetadataFieldValues 4 params → 200default
DELETE
/api/knowledge/v1alpha1/collections/{collection_id}/user-defined-metadata-fields/{user_defined_metadata_field_id}/values/{user_defined_metadata_field_value_id}
Delete User-Defined Metadata Field Values
UserDefinedMetadata_DeleteUserDefinedMetadataFieldValue 3 params → 200default
GET
/api/knowledge/v1alpha1/collections/{collection_id}/user-defined-metadata-fields/{user_defined_metadata_field_id}/values/{user_defined_metadata_field_value_id}
Get User-Defined Metadata Field Values
UserDefinedMetadata_GetUserDefinedMetadataFieldValue 3 params → 200default
POST
/api/knowledge/v1alpha1/collections/{data.collection_id}/user-defined-metadata-fields
Create User-Defined Metadata Fields
UserDefinedMetadata_CreateUserDefinedMetadataField 1 param body → 200default
PATCH
/api/knowledge/v1alpha1/collections/{data.collection_id}/user-defined-metadata-fields/{data.user_defined_metadata_field_id}
Update User-Defined Metadata Fields
UserDefinedMetadata_UpdateUserDefinedMetadataField 2 params body → 200default
POST
/api/knowledge/v1alpha1/collections/{data.collection_id}/user-defined-metadata-fields/{data.user_defined_metadata_field_id}/values
Create User-Defined Metadata Field Values
User_defined_metadata_create_user_defined_metadata_field_values 2 params body → 200default
PATCH
/api/knowledge/v1alpha1/collections/{data.collection_id}/user-defined-metadata-fields/{data.user_defined_metadata_field_id}/values/{data.user_defined_metadata_field_value_id}
Update User-Defined Metadata Field Values
UserDefinedMetadata_UpdateUserDefinedMetadataFieldValue 3 params body → 200default
GET
/api/knowledge/v1alpha1/metadata-fields/{metadata_field_id}/collections
List Org IDs using Metadata Field
UserDefinedMetadata_ListCollectionsByMetadataField 3 params → 200default

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are UserDefinedMetadataFieldValue (6 properties), UserDefinedMetadataField (5 properties), ListCollectionsByMetadataFieldResponse (5 properties), ListUserDefinedMetadataFieldsResponse (4 properties). Each schema is shown below with its type and property counts.

UserDefinedMetadataFieldValue
object
6 properties
GoogleProtobufValue
Represents a dynamically typed value which can be either null, a number, a string, a boolean, a recursive struct value, or a list of values.
Status
object
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](h…
3 properties
ListUserDefinedMetadataFieldValuesResponse
object
4 properties
GoogleProtobufAny
object
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
1 property
GetUserDefinedMetadataFieldValueResponse
object
2 properties
UserDefinedMetadataField
object
5 properties
ListUserDefinedMetadataFieldsResponse
object
4 properties
UpdateUserDefinedMetadataFieldRequest
object
2 properties
ListCollectionsByMetadataFieldResponse
object
5 properties
CreateUserDefinedMetadataFieldRequest
object
User-Defined Metadata Fields
1 property
CreateUserDefinedMetadataFieldValuesRequest
object
1 property
UpdateUserDefinedMetadataFieldValueRequest
object
2 properties
GetUserDefinedMetadataFieldResponse
object
2 properties
ResourceMetadata
object
4 properties
CollectionMetadata
object
Metadata that will be returned with each collection-level GET
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pryon-userdefinedmetadata-api-openapi.yml Raw ↑

Other APIs Pryon publishes across the network.

Pryon Analytics API
Pryon Connector Service External API
Pryon Content Service API
Pryon Content Service API
Pryon Exchange API
Pryon Exchange Event API
Pryon Feedback API
Pryon Generative API
Pryon Generative Exchange API
Pryon Generative Feedback API
Pryon Generative Retrieval API
Pryon Generative Retrieval Feedback API
Where this information came from

This is an independent, third-party profile of Pryon User Defined Metadata 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.