Forum Discussion

StephenPowell's avatar
StephenPowell
Qrew Member
2 months ago
Solved

OAuth 2.0

I am attempting to have a third party web service initiate a webhook. In order to do this, I need to provide that service authorization to Quickbase via Oauth 2. Here are the fields it is requesting....

URL

Token URL

Client ID

Client Secret Key

Scopes (Optional)

I have tried all sorts of different configurations of information to try and get this to work but have failed so far. Any help would be greatly appreciated. 

  • While a lot of services require all of that Quickbase does not.

    If you wanted to send the data from the other service into Pipelines (trigged when the other service sends a payload) use the "Webhooks" channel.

    It will run based on the permissions of the Pipeline owner.

    If you are not using Pipelines and are directly sending data to Quickbase via API, each API will have different requirements for a user or app token that is included as part of the URL or headers. So no Client ID, Secret Key, or Scopes.

    Here is more info on the APIs.

    JSON RESTful APIs

    HTTP APIs

    -Sharon

  • While a lot of services require all of that Quickbase does not.

    If you wanted to send the data from the other service into Pipelines (trigged when the other service sends a payload) use the "Webhooks" channel.

    It will run based on the permissions of the Pipeline owner.

    If you are not using Pipelines and are directly sending data to Quickbase via API, each API will have different requirements for a user or app token that is included as part of the URL or headers. So no Client ID, Secret Key, or Scopes.

    Here is more info on the APIs.

    JSON RESTful APIs

    HTTP APIs

    -Sharon