/ Labs

Developers / Public API future

Developers

The SRC technical platform does not yet exhibit a public API. This page sets the standard, status and limits of what can be integrated when the ecosystem grows.

BlackSignal Labs Universal Search

Architecture

Planned technical layers

Content GraphDivisions, Projects, Products, Collections, Colleges, Arts, People, and Related Archive Records.

SRC IDUnified account for notifications, orders, collection, vord, ukt, libt, object uk, ibt, events and services connected.

Store ServicesCatalogue, inventory, orders, checkout, php, returns, folios and object passports.

SearchUniversal search with pages, divisions, projects, products, Journal, Archive and related terms.

AdminBack office for content, catalog, orders, events, opportunities, users, permissions and metrics.

API Reference Preview

Planned public contracts

The first few days already exist as public statics. The rest document the model expected and should not be treated as productive API until you connect backend, authentication, pledge-ChC, monitoring, terms of use and security review.

GET /status.json

Public footpath with visible services, production n. 1 00, operating limits and trusted links.

Active static feed

GET /healthz

Health aliases to verify that the public package responds and distinguish unconnected integrations.

Active static feed

GET /v1/registry

Public identifiers for divisions, projects, collections, products and the file record.

Public preview

GET /v1/projects

Project Registry with status, division, relationships, and related public routes.

Public preview

GET /v1/store/objects

Public catalogue, object cl, commercial status, collection, drop and links to product.

Commerce gated

POST /v1/signals/preferences

Communication preferences by category, with explicit consent and independent low.

Auth required later

GET /v1/account/notifications

Future authenticated inbox for portfolios, drops, events, support, openviews and system warnings.

Auth required later

POST /v1/talent/intake

Technical, creative and editorial profiles for the Microsoft Microsoft and Open The IC.

Access controlled

Public standards

Conditions before opening integrations

Privacy

Minimum Access Necessary by Division. An integration should not inherit data that it does not need.

Security

Strong authentication, role-based permissions, audit and separation of public, operational and sensitive data.

Estabilidad

Versioned, Tablelog, Use Limits, Clear Errors and Stable Routes for Public Entities.

Accessibility

Visual development must respect keyboard, contrast, < > >Foist, semantic structure and mobile performance.

Developer Access Draft

Prepares a technical application

The draft is saved only in this browser until you mail it. It does not replace a system in the 'Balkets' or create credentials.

Developer routes

What's available now

System StatusPublic status of Store, Labs, Archive, Contact and visible services. Consult.

Status FeedsStructured State and Public Health Reading in status.json, health.json and /Healthz.

ChangelogRegistering public changes on site, Store, Archive and SRC Network. View.

RegistryCodes and public relations for projects, products, collections and passports. Open.

Universal SearchPublic index of pages, products, projects, articles and archive. Search.

Technical inquiriesProposals, integrations or technical support should be entered by the local draft of this page or by Contact with Technology / Support type.