# 128 Technology (Juniper Session Smart Networking)

> 128 Technology builds the Session Smart Networking platform: a software-defined, session-aware
> IP routing and network services stack built on Secure Vector Routing (SVR), a tunnel-free
> routing protocol. The Session Smart Router (SSR) carries the data and control plane; the
> Session Smart Conductor is the centralized management, policy and provisioning engine. Juniper
> Networks acquired the company in 2020, but the developer surface still lives under the
> 128 Technology identity — docs.128technology.com, github.com/128technology, and the
> @128technology npm scope.

Generated by API Evangelist from the company's public documentation and repositories on
2026-09-05. Not published by 128 Technology.

## How the API works

The SSR exposes a YANG-modeled configuration and state tree over three interfaces: a REST API
rooted at `/api/v1`, an equivalent GraphQL API, and NETCONF. All three are served by the
customer's OWN deployed router or conductor. There is no vendor-hosted API endpoint, no
developer signup, and no API key issuance — the base URL is the address of your instance.

- Authenticate: `POST https://<SSR address>/api/v1/login` with `{"username": "...", "password": "..."}`
- The response returns `{"token": "<RS256 JWT>"}`
- Every subsequent call carries `Authorization: Bearer <token>`
- Authorization is RBAC: the role's capabilities (`config-read`, `config-write`, `provisioning`)
  and its resource groups determine which routers, tenants and services the token can reach.

The interactive references are served from the instance itself and are NOT publicly reachable:
`https://<SSR address>/documentation/swagger` and `https://<SSR address>/documentation/graphql`.
No OpenAPI, GraphQL SDL or Postman collection is published at any public URL. To discover which
API a given operation uses, the vendor's own advice is to run the PCLI `trace` command.

## APIs

- [Session Smart Router REST and GraphQL API](https://docs.128technology.com/docs/intro_rest_graphql_apis): The northbound API of the SSR and Conductor. Base `https://{ssr-address}/api/v1`.

## Docs

- [SSN Documentation](https://docs.128technology.com/): The full product documentation site.
- [REST and GraphQL APIs](https://docs.128technology.com/docs/intro_rest_graphql_apis): Authentication, tokens, and where the built-in references live.
- [Session Smart Networking Platform](https://docs.128technology.com/docs/about_128t): What the platform is.
- [PCLI Command Reference](https://docs.128technology.com/docs/cli_reference): 320 commands, 192 of them `show`.
- [PCLI Statistics Reference](https://docs.128technology.com/docs/cli_stats_reference)
- [Configuration Basics](https://docs.128technology.com/docs/config_basics): Candidate configuration, commit, conflict handling.
- [Role-Based Access Control](https://docs.128technology.com/docs/config_RBAC): Capabilities, resource groups, roles.
- [Alarms and Events](https://docs.128technology.com/docs/events_overview): The event model, categories and severities.
- [SSR Monitoring Agent](https://docs.128technology.com/docs/concepts_monitoring): Telegraf-based push of metrics and events to Kafka, syslog or InfluxDB.
- [SSR Releases](https://docs.128technology.com/docs/about_releases): Versioning scheme, R1/R2/STS/LTS model, GA and EOL table.
- [Software Support Policy](https://docs.128technology.com/docs/about_support_policy)
- [Rollback and Reinstallation](https://docs.128technology.com/docs/intro_rollback)
- [Common Criteria and FIPS](https://docs.128technology.com/docs/cc_fips_intro): Certified platforms, FIPS mode, CAVP validations.
- [Security Hardening Guidelines](https://docs.128technology.com/docs/sec_hardening_guidelines)
- [SSR Knowledge Base](https://docs.128technology.com/kb)

## Releases and lifecycle

- [7.2 Release Notes](https://docs.128technology.com/docs/release_notes_128t_7.2) — current stream, LTS, 7.2.1-1r1 shipped 2026-07-14
- [7.1 Release Notes](https://docs.128technology.com/docs/release_notes_128t_7.1) — STS
- [7.0 Release Notes](https://docs.128technology.com/docs/release_notes_128t_7.0) — LTS
- [Session Smart Router Dates & Milestones](https://support.juniper.net/support/eol/software/ssr/) — EOL / EoE milestones

## Packages

The company publishes no REST or GraphQL client SDK. What it does publish are the YANG/NETCONF
building blocks of its own management surface. All are dormant; the newest release is from 2022.

- [@128technology/yinz](https://www.npmjs.com/package/@128technology/yinz) — 4.5.6, 2021-08-10
- [@128technology/yinz-json](https://www.npmjs.com/package/@128technology/yinz-json) — 6.1.0, 2022-09-02
- [@128technology/netconfetti](https://www.npmjs.com/package/@128technology/netconfetti) — 1.0.2, 2018-08-24, a JavaScript NETCONF client
- [@128technology/ply](https://www.npmjs.com/package/@128technology/ply) — 0.5.4, 2021-08-10
- [@128technology/ui](https://www.npmjs.com/package/@128technology/ui) — 0.10.3, 2021-10-26
- [yinsolidated](https://pypi.org/project/yinsolidated/) — 1.3.0, 2019-07-11 (PyPI)
- [GitHub organization](https://github.com/128technology) — 62 public repositories

## Repository artifacts

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/apis.yml)
- [Authentication](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/authentication/128-technology-authentication.yml)
- [Conventions](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/conventions/128-technology-conventions.yml)
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/lifecycle/128-technology-lifecycle.yml)
- [Changelog](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/changelog/128-technology-changelog.yml)
- [Conformance](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/conformance/128-technology-conformance.yml)
- [CLI](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/cli/128-technology-cli.yml)
- [Packages](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/packages/128-technology-packages.yml)
- [Event surface](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/asyncapi/128-technology-event-surface.yml)
- [Rate limits](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/rate-limits/128-technology-rate-limits.yml)
- [Plans and pricing](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/plans/128-technology-plans-pricing.yml)
- [Domain security](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/security/128-technology-domain-security.yml)
- [Well-known probe](https://raw.githubusercontent.com/api-evangelist/128-technology/refs/heads/main/well-known/128-technology-well-known.yml)

## Known gaps

- No OpenAPI, GraphQL SDL, AsyncAPI, Postman collection or JSON Schema is published at any
  public URL. The Swagger and GraphQL references exist but only on a deployed instance.
- No `/.well-known/` document on any host; `128technology.com` presents an invalid TLS
  certificate and answers 200 with Juniper marketing HTML for every path, including a control
  path that cannot exist.
- No idempotency mechanism, no published error reference, no published API rate limits, no
  status page, no A2A agent card, and no MCP server.
- No first-party client SDK for the REST or GraphQL surface in any language.