The Shell Card Management API provides secure and structured access to the Shell Card Platform, enabling integration with Shell’s internal systems for managing card-related resources.
This REST-based API uses the POST method for all operations—including retrieval, creation, update, and deletion of resources. It supports flexible search capabilities through JSON-encoded request bodies and returns JSON-formatted responses. Standard HTTP status codes are used to indicate the outcome of each request.
Authentication is handled via OAuth 2.0 using the Client Credentials flow. Access tokens must be included in the Authorization header of each request.
All resources are managed within the Shell Card Platform, which abstracts the complexity of backend systems. Some operations may be processed asynchronously, and clients should be prepared to handle delayed responses or polling mechanisms where applicable.
Go to the Shell Developer Portal: https://developer.shell.com
The generated code depends on a few Ruby gems. The references to these gems are added in the gemspec file. The easiest way to resolve the dependencies, build the gem and install it is through Rake:
- Install Rake if not already installed:
gem install rake - Install Bundler if not already installed:
gem install bundler - From terminal/cmd navigate to the root directory of the SDK.
- Invoke:
rake install
Alternatively, you can build and install the gem manually:
- From terminal/cmd navigate to the root directory of the SDK.
- Run the build command:
gem build shell_card_management_ap_is.gemspec - Run the install command:
gem install shell_card_management_ap_is-1.0.0.gem
The following section explains how to use the shell_card_management_ap_is ruby gem in a new Rails project using RubyMine™. The basic workflow presented here is also applicable if you prefer using a different editor or IDE.
Close any existing projects in RubyMine™ by selecting File -> Close Project. Next, click on Create New Project to create a new project from scratch.
Next, provide TestApp as the project name, choose Rails Application as the project type, and click OK.
In the next dialog make sure that the correct Ruby SDK is being used (>= 2.6 and <= 3.2) and click OK.
In order to use the shell_card_management_ap_is gem in the new project we must add a gem reference. Locate the Gemfile in the Project Explorer window under the TestApp project node. The file contains references to all gems being used in the project. Here, add the reference to the library gem by adding the following line: gem 'shell_card_management_ap_is', '1.0.0'
Once the TestApp project is created, a folder named controllers will be visible in the Project Explorer under the following path: TestApp > app > controllers. Right click on this folder and select New -> Run Rails Generator....
Selecting the said option will popup a small window where the generator names are displayed. Here, select the controller template.
Next, a popup window will ask you for a Controller name and included Actions. For controller name provide Hello and include an action named Index and click OK.
A new controller class named HelloController will be created in a file named hello_controller.rb containing a method named Index.
- Add the
require 'shell_card_management_ap_is'statement to require the gem in the controller file. - Add the
include ShellCardManagementApIsstatement to include the sdk module in the controller file. - In the
Indexmethod, add code for initialization and a sample for its usage.
You can explore the SDK interactively using IRB in two ways
Open your system terminal (Command Prompt, Git Bash or macOS Terminal) and type the following command to start the irb console.
irbNow you can load the SDK in the IRB
require 'shell_card_management_ap_is'
include ShellCardManagementApIsOpen your system terminal (Command Prompt, Git Bash or macOS Terminal) and navigate to the root folder of SDK.
cd path/to/shell_card_management_ap_is
Now you can start the preconfigured irb console by running the following command
ruby bin/consoleNote: This automatically loads the SDK from lib/
To run the tests, navigate to the root directory of the SDK in your terminal and execute the following command:
rake
Note: Documentation for the client can be found here.
The following parameters are configurable for the API Client:
| Parameter | Type | Description |
|---|---|---|
| environment | Environment |
The API environment. Default: Environment.SIT |
| connection | Faraday::Connection |
The Faraday connection object passed by the SDK user for making requests |
| adapter | Faraday::Adapter |
The Faraday adapter object passed by the SDK user for performing http requests |
| timeout | Float |
The value to use for connection timeout. Default: 60 |
| max_retries | Integer |
The number of times to retry an endpoint call if it fails. Default: 0 |
| retry_interval | Float |
Pause in seconds between retries. Default: 1 |
| backoff_factor | Float |
The amount to multiply each successive retry's interval amount by in order to provide backoff. Default: 2 |
| retry_statuses | Array |
A list of HTTP statuses to retry. Default: [408, 413, 429, 500, 502, 503, 504, 521, 522, 524, 408, 413, 429, 500, 502, 503, 504, 521, 522, 524] |
| retry_methods | Array |
A list of HTTP methods to retry. Default: %i[get put get put] |
| http_callback | HttpCallBack |
The Http CallBack allows defining callables for pre and post API calls. |
| proxy_settings | ProxySettings |
Optional proxy configuration to route HTTP requests through a proxy server. |
| client_credentials_auth_credentials | ClientCredentialsAuthCredentials |
The credential object for OAuth 2 Client Credentials Grant |
The API client can be initialized as follows:
require 'shell_card_management_ap_is'
include ShellCardManagementApIs
client = Client.new(
client_credentials_auth_credentials: ClientCredentialsAuthCredentials.new(
o_auth_client_id: 'OAuthClientId',
o_auth_client_secret: 'OAuthClientSecret'
),
environment: Environment::SIT
)require 'shell_card_management_ap_is'
include ShellCardManagementApIs
# Create client from environment
client = Client.from_envSee the Environment-Based Client Initialization section for details.
The SDK can be configured to use a different environment for making API calls. Available environments are:
| Name | Description |
|---|---|
| SIT | Default |
| PRODUCTION | - |
This API uses the following authentication schemes.