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

Osano Subject Rights Portal API

The subjectRightsPortal API from Osano — 2 operation(s) for subjectrightsportal.

Osano Subject Rights Portal API is one of 17 APIs that Osano publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and SDKs.

This API exposes 3 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.osano.com.

3 operations 2 paths 6 schemas 1 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.osano.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Osano Subject Rights Portal API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-osano-api-key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 3

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

subjectRightsPortal 3
GET
/v1/subject-rights/requests/{requestId}/portal-messages
Get Portal Messages
getPortalMessages 4 params → 200400404
POST
/v1/subject-rights/requests/{requestId}/portal-messages
Create Portal Message
postPortalMessage 1 param body → 204400
PATCH
/v1/subject-rights/requests/{requestId}/portal-messages/{messageId}
Update Portal Message
patchPortalMessage 2 params body → 200400404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PortalMessagesList (6 properties), PortalMessagesResponse (2 properties), PatchPortalMessagesResponse (2 properties), PortalMessage (1 property). Each schema is shown below with its type and property counts.

PatchPortalMessagesResponse
object
2 properties 2 required
PortalMessagesList
object
6 properties 5 required
ErrorResponse
object
1 property
PatchPortalMessage
object
1 property 1 required
PortalMessagesResponse
object
2 properties 1 required
PortalMessage
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

osano-subjectrightsportal-api-openapi.yml Raw ↑

Other APIs Osano publishes across the network.

Osano CMP JavaScript API
Osano Cmp API
Osano Cmp Rules API
Osano Collections API
Osano Config API
Osano Connectors API
Osano Consent Profiles API
Osano Consents API
Osano Customer Insights API
Osano Data Discovery API
Osano Dsar API
Osano Dsar Action Items API
Where this information came from

This is an independent, third-party profile of Osano Subject Rights Portal 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.