Rigetti Computing authentication API
The authentication API from Rigetti Computing — 4 operation(s) for authentication.
Rigetti Computing authentication API is one of 11 APIs that Rigetti Computing publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.
This API exposes 4 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.0.2, at version 2020-07-31.
Requests are made against a single base URL, https://api.qcs.rigetti.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Rigetti Computing authentication API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (JWTBearer).
It accepts HTTP bearer tokens (JWT) (JWTBearerOptional).
JWTBearer— A JSON web token with sub or uid claim, as well as groups claim. If the token is absent, invalid or expired, the client will receive a 401 response. If the tok…JWTBearerOptional— Same as JWTBearer, but the Authorization header is optionally parsed. Clients will receive a 401 response if an invalid or expired token is provided. Otherwise…
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Error (4 properties), UserProfile (4 properties), User (4 properties), ValidationError (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Rigetti Computing 10
Other APIs Rigetti Computing publishes across the network.