Rigetti & Co clientApplications API
Check for the latest SDK versions.
Rigetti & Co clientApplications API is one of 9 APIs that Rigetti & Co publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include clientApplications. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 3 operations across 3 paths, and defines 8 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 & Co clientApplications 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 3
Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Check for the latest SDK versions.
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ClientApplication (6 properties), Error (4 properties), ClientApplicationsDownloadLink (3 properties), CheckClientApplicationResponse (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 & Co 8
Other APIs Rigetti & Co publishes across the network.