Skip to main content
Before you can make authentication requests, you’ll need an OAuth2 Client. It is the entity that identifies you, as a third-party developer, between Ruba and the end user. You can manage them from your User Settings Here are the required fields:
  • Application Name: the name of the application shown to end users.
  • Client Type: the type of client you are creating. Read more
  • Redirect URIs: for security, you must declare your application URL where users are sent after granting access to their data.
    When setting up your OAuth client, you must use an https:// URL for security reasons. We block http:// URLs, except when the hostname is localhost. This exception lets you use http://localhost for easy testing in development mode.
  • Scopes: the list of scopes your app will be able to request. To improve privacy and security, select only the scopes you actually need for your application.
  • Homepage URL: the URL of your application. It is shown to end users on the authorization page.
Optionally, you can also add a logo, terms of service, and privacy policy URL. They are all shown to end users on the authorization page. Once your client is created, you receive a Client ID and a Client Secret. You’ll need these values to make authentication requests. These values are extremely sensitive and must be kept secret. They enable authentication requests on Ruba!