Modify RESTClient post() to add CB-2FA-Token for SIWC transaction endpoints #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the April 2nd expansion of the CDP api keys to support SIWC urls, there is extra support needed for the
/v2/accounts/:account_id/transactions
endpoints. This appears to be a holdover from the OAuth2 support, and may actually be an error in the API. If not, support is needed for thetransactions
endpoints. Specifically, posts this endpoint requires theCB-2FA-Token
header. This PR adds acb_2fa_token
argument to theRESTClient
constructor to facilitate that.Example
Changes
CB-2FA-TOKEN
header whencb_2fa_token
is found in instanceCB_2FA_TOKEN_ENV_KEY
constantcb_2fa_token
to APIBase constructorcb_2fa_token
to RESTClient constructor