Rocket Fuel
Rocket Fuel is a blockchain-based payment platform that provides the easiest way to pay with cryptocurrency and bank transfers, enabling businesses to accept digital payments and traditional banking methods seamlessly.

Power end-to-end data operations for your Rocket Fuel API with Nexla. Our bi-directional Rocket Fuel connector is purpose-built for Rocket Fuel, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Rocket Fuel or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Rocket Fuel workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a Rocket Fuel credential, you need to obtain your Username (or API Key) and Password from your Rocket Fuel account. Rocket Fuel uses Token Authentication, which requires authenticating with your username and password to obtain an access token that is then used for all API requests.
To obtain your Rocket Fuel API credentials, follow these steps:
-
Sign in to your Rocket Fuel account using your administrator credentials.
-
Navigate to your account settings or API management section in the Rocket Fuel interface.
-
Look for the API or API Keys section in your account settings, or navigate to Settings > API or Developers > API Keys.
-
If you don't have API credentials yet, look for the option to generate or view your Username (or API Key) and Password.
-
Click Generate API Key or Create API Key to create new API credentials.
-
Configure your API credential settings:
- Enter a name for the credentials (e.g., "Nexla Integration")
- Review and select the permissions or scopes for the credentials (if applicable)
-
Click Generate or Create to create the API credentials.
-
Your Username (or API Key) will be displayed immediately after creation. Copy the Username.
-
Your Password will be displayed immediately after creation. Copy the Password immediately, as it may not be accessible again after you navigate away from the page.
-
Store both credentials securely, as you will need them to configure your Nexla credential. The Username and Password are sensitive information and should be kept confidential.
The Username and Password are used to authenticate with the Rocket Fuel API authentication endpoint (/api/auth/signin) to obtain an access token. The access token is then sent in the Authorization header with the Bearer prefix for all subsequent API requests to the Rocket Fuel API. The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Rocket Fuel account settings and generate new ones. For detailed information about Rocket Fuel authentication, API access, and available endpoints, refer to the Rocket Fuel API documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| Username Or API Key | Yes | No | Your username or personal API Key |
| Password | Yes | Yes | Your password. |
Create a credential in Nexla
- To create a new Rocket Fuel credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Rocket Fuel

- Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Rocket Fuel uses Token Authentication for all API requests. Your Username (or API Key) and Password are used to authenticate with the Rocket Fuel API authentication endpoint to obtain an access token, which is then used for all subsequent API requests.
-
Enter your Rocket Fuel Username (or API Key) in the Username Or API Key field. This is the Username or API Key you obtained from your Rocket Fuel account settings (API or API Keys section). The Username is used along with the Password to authenticate with the Rocket Fuel API authentication endpoint and obtain an access token.
-
Enter your Rocket Fuel Password in the Password field. This is the Password you obtained from your Rocket Fuel account settings. The Password is used along with the Username to authenticate with the Rocket Fuel API authentication endpoint and obtain an access token. The Password is sensitive information and must be kept confidential.
Your Rocket Fuel API credentials can be found in your Rocket Fuel account settings under the API or API Keys section. The Username (or API Key) and Password are used to authenticate with the Rocket Fuel API authentication endpoint (
/api/auth/signin) to obtain an access token. The access token is then automatically sent in theAuthorization: Bearer {token}header for all subsequent API requests to the Rocket Fuel API.The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Rocket Fuel account settings and generate new ones. The Username and Password provide access to your Rocket Fuel account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.
For detailed information about Rocket Fuel authentication, API access, and available endpoints, see the Rocket Fuel API documentation.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Rocket Fuel connector tile, then select the credential that will be used to connect to your Rocket Fuel account, and click Next; or, create a new Rocket Fuel credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Rocket Fuel endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be fetched and displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Rocket Fuel data sources can also be manually configured to ingest data from any valid Rocket Fuel API endpoint, including endpoints not covered by the pre-built templates or apply further customizations. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Rocket Fuel API typically uses the GET method (e.g., https://app.rocketfuelblockchain.com/api/banks/my, https://app.rocketfuelblockchain.com/api/currencies). For the Response Data Path, use $.result.banks[*] to extract all banks from the result, $.result[*] to extract all items from the result array, or $ to extract the entire response for single-record endpoints, depending on your endpoint.
Once all of the relevant settings have been configured, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.