Nivoda Authentication

generated: '2026-07-20'
method: searched
source: https://bitbucket.org/nivoda/nivoda-api/src/main/
docs: https://bitbucket.org/nivoda/nivoda-api/src/main/
summary:
  types: [bearer]
  token_acquisition: graphql-login-mutation
  credentials: nivoda-platform-username-password
  token_header: Authorization Bearer
notes: >-
  The Nivoda GraphQL API is not OpenAPI/OAuth-based. A client first runs the
  `authenticate` query with `username_and_password(username, password)` (the same
  credentials used to log in to the Nivoda platform) which returns a session
  `token`. That token is then sent as an `Authorization: Bearer <token>` header
  on all subsequent query/mutation requests. In the GraphiQL explorer the token
  is supplied by wrapping the operation in `as(token: $token) { ... }`. The
  GraphiQL explorer page itself is additionally gated by HTTP Basic auth
  (nivoda-api-docs / nivoda-graphiql) documented publicly for browsing. Staging
  credentials are shared on request; production login is activated by a Nivoda
  account manager after signing the Nivoda Feed Agreement.
schemes:
- name: BearerToken
  type: http
  scheme: bearer
  in: header
  header: Authorization
  obtained_via: 'authenticate.username_and_password(username, password) { token }'
  endpoint: https://integrations.nivoda.net/api/diamonds
  sources: [examples/orders/nodejs-orders.js, examples/holds/nodejs-holds.js, examples/search/graphql-search.gql]
- name: GraphiQLBasicAuth
  type: http
  scheme: basic
  in: header
  applies_to: https://integrations.nivoda.net/api/diamonds-graphiql
  note: Public browse-only credentials for the GraphiQL explorer UI.
  sources: [README.md]