No, none or self handled. It is an encoded Bearer token.
The in header you will put Authorization and Bearer : whateverererererere
The “whateverererererere” bit are the consumer key and secret messed about with …
- URL encode the consumer key and consumer secret according to RFC 1738. Note that at the time of writing, this will not actually change the consumer key and secret, but this step should still be performed in case the format of those values changes in the future.
- Concatenate the encoded consumer key, a colon character “:”, and the encoded consumer secret into a single string.
- Base64 encode the string from the previous step.
You don’t need to do this on Bubble, you can use online tools.