Skip to main content
This section documents Phosra’s own Parental Controls product — the families, children, policies, and enforcement API that Phosra has built on the platform. It is one product built on top of the OCSS-conformant control plane, not the control plane itself. If you are building a third-party tool, agent, or enforcement partner integration, start with the Developer Platform instead.
The Phosra API provides 66 endpoints organized into the following groups. All endpoints use the base URL https://prodapi.phosra.com/api/v1 (or https://phosra-api-sandbox-production.up.railway.app/api/v1 for the hosted sandbox). Every group below links to a live, per-endpoint reference.

​
Endpoint Groups

Authentication

Authenticate with a WorkOS token or a developer API key. 2 endpoints

Families

Create and manage family groups and their members. 8 endpoints

Children

Add children to families, manage profiles, and get age ratings. 6 endpoints

Policies

Create, activate, pause, and auto-generate safety policies. 8 endpoints

Rules

Manage individual rules across the 123 OCSS safety categories (the closed OCSS v4 vocabulary). 5 endpoints

Enforcement

Push policies to platforms and track enforcement jobs. 5 endpoints

Platforms

Browse and filter supported integration platforms. 6 endpoints

Compliance

Connect, verify, and manage platform connections. 5 endpoints

Webhooks

Register webhook endpoints for real-time event notifications. 7 endpoints

Standards

Browse and adopt community safety standards. 5 endpoints

Ratings

Content rating systems (MPAA, ESRB, PEGI, CSM, TVPG) and age lookups. 5 endpoints

Devices

Register Apple devices and manage on-device enforcement. 4 endpoints

​
Authentication

Most endpoints require authentication via Bearer token or API key. See the Authentication guide for details. Public endpoints (platforms, ratings, standards) are marked with security: [] in the OpenAPI spec.

​
Response Format

All responses return JSON. Successful responses return the resource directly. Error responses follow the format: 
{
  "error": "error_code",
  "message": "Human-readable description"
}
See the Errors page for details on status codes and error handling.

​
OpenAPI Spec

The machine-readable specification is served live from the Go API, versioned with the binary:

OpenAPI JSON

https://prodapi.phosra.com/openapi.json — canonical spec, import into any OpenAPI 3.1 tool.

OpenAPI YAML

https://prodapi.phosra.com/openapi.yaml — same spec, YAML form.

Postman / Insomnia collection

A ready-to-run collection (93 requests, 20 folders) pre-wired to the hosted sandbox — download, import, and press Send.

llms.txt

llms.txt and llms-full.txt for LLM-friendly consumption.
The sandbox serves the identical spec at https://phosra-api-sandbox-production.up.railway.app/openapi.json. The in-repo copy at /openapi.yaml is kept in sync and is suitable for local mint dev rendering.