Bitpagos Authentication

generated: '2026-09-28'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.ripio.com/crypto-as-a-service/widget/get-started/authentication.md
sources:
- https://docs.ripio.com/crypto-as-a-service/widget/get-started/authentication.md
- https://docs.ripio.com/ramps-api/widget/get-started/authentication.md
- https://docs.ripio.com/ramps-api/authentication/acquire-access-token.md
- https://apidocs.ripio.com/static/api/authentication
description: Authentication methods for Bitpagos (Ripio) services
schemes:
- type: other
  name: Session code request
  evidence: Your server calls `POST /auth` and receives a `session_code`.
  location: body
  how_to_obtain: Send a POST request to https://b2b-crypto-widget-api.sandbox.ripio.com/api/v1/auth with JSON body containing `client_id`, `client_secret`
    and `external_ref`.
- type: other
  name: On‑Ramp widget token request
  evidence: This service provides an access JWT token for the user to use the On Ramp Widget.
  location: body
  how_to_obtain: POST to https://b2b-widget-onramp-api.ripio.com/api/v1/auth (or sandbox URL) with form‑urlencoded fields `username` (client_id:external_ref[:address])
    and `password` (client_secret).
- type: oauth2
  name: Ramp API OAuth2 client credentials
  evidence: Every call to the API has to be authenticated with an OAuth2 Token.
  token_url: https://skala-sandbox.ripio.com/oauth2/token/
  how_to_obtain: Send a POST request to the token endpoint with Basic Authorization header (Base64‑encoded `client_id:client_secret`) and form
    field `grant_type=client_credentials`.
- type: apiKey
  name: API Token header
  evidence: Header Description Authorization The API key as a string.
  location: header
  header: Authorization
  how_to_obtain: Create API credentials in the Ripio portal to obtain an API Token, then include it in the `Authorization` header of private requests.
docs: https://docs.ripio.com/crypto-as-a-service/widget/get-started/authentication.md