Rigetti Computing Authentication API
The authentication API from Rigetti Computing — 4 operation(s) for authentication.
The authentication API from Rigetti Computing — 4 operation(s) for authentication.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/rigetti-computing-authentication-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
x-logo: https://qcs.rigetti.com/static/img/rigetti-logo.svg
contact:
email: support@rigetti.com
url: https://rigetti.zendesk.com
title: Rigetti QCS Authentication API
version: 2020-07-31
description: '# Introduction
This is the documentation for the Rigetti QCS HTTP API.'
servers:
- description: Rigetti API
url: https://api.qcs.rigetti.com
tags:
- name: Authentication
x-displayName: Authentication
paths:
/v1/auth:emailPasswordResetToken:
post:
description: Send a password reset link to the provided email address, if that email matches a registered user.
operationId: AuthEmailPasswordResetToken
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AuthEmailPasswordResetTokenRequest'
responses:
'204':
description: Request completed successfully.
'422':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Request validation failed.
summary: Email Password Reset Token
tags:
- Authentication
/v1/auth:getUser:
get:
description: Retrieve the profile of the authenticated user.
operationId: AuthGetUser
parameters: []
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/User'
description: Request completed successfully.
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Request authentication failed.
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: The authenticated user could not be located within our records. Please contact support@rigetti.com if you reach this error.
security:
- JWTBearer: []
summary: Get User
tags:
- Authentication
/v1/auth:resetPassword:
parameters: []
post:
description: Reset the password using the user's existing password. Note, this is an authenticated route.
operationId: AuthResetPassword
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AuthResetPasswordRequest'
required: true
responses:
'204':
description: Password successfully reset.
'401':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Request authentication failed.
'422':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Request validation failed.
security:
- JWTBearer: []
summary: Reset Password
tags:
- Authentication
/v1/auth:resetPasswordWithToken:
parameters: []
post:
description: Complete the forgot password flow, resetting the new password in exchange for an emailed token.
operationId: AuthResetPasswordWithToken
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AuthResetPasswordWithTokenRequest'
required: true
responses:
'204':
description: Password successfully reset.
'404':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: No account exists for the requested email.
'422':
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
description: Request validation failed.
summary: Reset Password With Token
tags:
- Authentication
components:
schemas:
AuthResetPasswordWithTokenRequest:
description: Token may be requested with AuthEmailPasswordResetToken.
properties:
newPassword:
type: string
token:
type: string
required:
- token
- newPassword
type: object
AuthResetPasswordRequest:
properties:
newPassword:
type: string
oldPassword:
type: string
required:
- oldPassword
- newPassword
type: object
AuthEmailPasswordResetTokenRequest:
properties:
email:
type: string
required:
- email
type: object
Error:
properties:
code:
title: Code
type: string
message:
title: Message
type: string
requestId:
title: Request ID
type: string
validationErrors:
items:
$ref: '#/components/schemas/ValidationError'
title: Validation Errors
type: array
required:
- code
- message
- requestId
title: Error
type: object
UserProfile:
properties:
email:
type: string
firstName:
type: string
lastName:
type: string
organization:
type: string
required:
- email
- firstName
- lastName
- organization
type: object
User:
properties:
createdTime:
format: date-time
type: string
id:
type: integer
idpId:
type: string
profile:
$ref: '#/components/schemas/UserProfile'
required:
- id
- idpId
- createdTime
type: object
ValidationError:
properties:
in:
enum:
- header
- query
- path
- body
type: string
message:
title: Message
type: string
path:
items:
type: string
title: Path
type: array
required:
- in
- message
title: ValidationError
type: object
securitySchemes:
JWTBearer:
bearerFormat: JWT
description: 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 token is valid, the server uses the claims to authorize the request, which may result in a 403 response.
scheme: bearer
type: http
JWTBearerOptional:
bearerFormat: JWT
description: 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, the server authorizes the request against either the valid token claims or an unauthenticated user. In either case, the client may receive a 403 response.
scheme: bearer
type: http
x-tagGroups:
- name: Account Management
tags:
- account
- authentication
- name: QPU Access
tags:
- endpoints
- deployments
- engagements
- quantumProcessors
- reservations
- translation
- name: SDKs
tags:
- clientApplications
- name: Filtering and ordering
tags:
- filterParameter
- orderParameter
- name: Errors
tags:
- errors