Skip to content

Commit

Permalink
Merge pull request #12 from chargebee/release/0.0.4
Browse files Browse the repository at this point in the history
Release/0.0.4
  • Loading branch information
cb-suryak authored Dec 29, 2023
2 parents 2278404 + 0b21dd9 commit 1e99823
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 4 deletions.
4 changes: 2 additions & 2 deletions gradle.properties
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
sonar_project_key=chargebee_cb-provider-spi
build_project_name=cb-provider-spi
build_group=org.chargebee.spi
build_version=0.0.1
build_version=0.0.4
# Artifactory config to be controlled at build time by CI/CD
artifactory_build_url=https://artifactory.url/maven/build
artifactory_publish_url=https://artifactory.url/maven/publish
artifactory_publish_url=https://artifactory.url/maven/publish
3 changes: 1 addition & 2 deletions spec/spi/openapi_trn.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ info:
- Translates API requests (as defined in this document) from Chargebee to the request format specified by the Service Provider's API.
- Translates API responses from the Service Provider APIs to the format understood by Chargebee (as defined in this document).
### Authorization
Chargebee uses HTTP header-based authorization for all the API endpoints associated with Service Adapter. We dynamically pass this authorization key in the HTTP header. The parameter that holds this key is found in the JSON object `api_configuration` required for configuring your onboarding on Chargebee's marketplace. In the `api_configuration` object, our [Taxes Service Adapter SPI](https://chargebee.atlassian.net/l/cp/ca5aZ1mA) checks the authorization key parameter from `credential_configuration.id` and creates the HTTP header-based input query parameter for authorization. The `credential_configuration` is an array of objects with an `id` attribute, and the value of `id` is the parameter containing the authorization key.
Chargebee uses HTTP header-based authorization for all the API endpoints associated with Service Adapter. We dynamically pass this authorization key in the HTTP header. The parameter that holds this key is found in the JSON object `api_configuration` quired for configuring your onboarding on Chargebee's marketplace. In the `api_configuration` object, our [Taxes Service Adapter SPI](https://chargebee.atlassian.net/l/cp/ca5aZ1mA) checks the authorization key parameter from `credential_configuration.id` and creates the HTTP header-based input query parameter for authorization. The `credential_configuration` is an array of objects with an `id` attribute, and the value of `id` is the parameter containing the authorization key.
Following are the JSON snippets for your reference.
Expand Down Expand Up @@ -276,7 +276,6 @@ components:
type: object
description: Contains the required properties for tax registration number validation response
required:
- requestId
- trn
- country
properties:
Expand Down

0 comments on commit 1e99823

Please sign in to comment.