Bringin APIs

Credential isolation

# Bringin APIs Bringin APIs enable you to make Bitcoin on and off-ramp services available for your European customers. We provide a simple yet best-in-class crypto on and off-ramp solution with SEPA instant support at the best rates in the market. ## Use Cases ### 1. Offramp to bank directly This option is ideal if you want users to add a "Sell to bank" button - allowing users to offramp their Bitcoin to Euros in their bank without any issues. A set of APIs to create an offramp order to convert incoming Bitcoin deposits into Euros into Bringin's IBAN for users to withdraw anytime. **For this use case, you only need to focus on the User Onboarding and Offramp sections.** #### Key Features: - Create an offramp order by providing IP, amount, beneficiary details. API returns a Bitcoin Address and a lightning invoice - Once we receive Bitcoin to the provided address or invoice, we swap BTC to Euros at market rate - You initiate a bank transfer to users bank ### 2. Offramp to Bringin (2 days integration) Connect to the Bringin account to offer Bringin vIBAN and debit cards. Please contact us at support@bringin.xyz for detailed documentation and integration support for this option. ## Authentication While the APIs are available to the public to build with, we provide an `api-key` and `api-secret` for each company to make secure API calls. ### Request Headers All API requests must be accompanied by the following headers: | Header Parameter | Description | |------------------|-------------| | `api-key` | Contact us at info@bringin.xyz to obtain API key | | `Authorization` | A signature generated using the API Secret. Contact us at info@bringin.xyz to obtain the API secret. More information is below on generating a signature | | `Content-Type` | `application/json` | ### Environments The sandbox and production environments mirror each other, except for the base URL and your API keys. Please contact us at info@bringin.xyz to elevate your application to production. ### Request Signature Calculation You can calculate the value of the `Authorization` header by creating a SHA256HMAC digest of your request body, signed with your `API Secret`, in the following manner: #### Step 1: Get current UNIX timestamp ```javascript const time = Date.now().toString(); ``` #### Step 2: Stringify request body ```javascript const bodyString = JSON.stringify(body); // For a GET request, please use an empty body such as: // const bodyString = JSON.stringify({}); ``` #### Step 3: Calculate MD5 digest of request body Calculate the hex encoded MD5 digest of your request body exactly as it will be sent. For GET requests, please include an empty body `'{}'` that evaluates to an MD5 of `99914b932bd37a50b983c5e7c90ae93b`. ```javascript const requestContentHexString = CryptoJS.MD5(bodyString).toString(CryptoJS.enc.Hex); // For a GET request, the bodyString above for example would just be '{}' // and the calculated MD5 is 99914b932bd37a50b983c5e7c90ae93b ``` #### Step 4: Concatenate signature components ```javascript const signatureRawData = time + 'POST' + '/card/create' + requestContentHexString; ``` #### Step 5: Create SHA256 HMAC digest Use your API Secret to create a SHA256 HMAC digest in hex: ```javascript const apiSecret = ''; const requestSignatureHexString = CryptoJS.HmacSHA256(signatureRawData, apiSecret).toString(CryptoJS.enc.Hex); ``` #### Step 6: Create authorization header Finally, create your authorization header as follows, using the verb `'HMAC '` concatenated with the timestamp and the `requestSignatureHexString`, separated by a `:` ```javascript const authorizationHeader = 'HMAC ' + time + ':' + requestSignatureHexString; ``` ### Complete Example ```javascript import crypto from 'crypto'; const hmac = crypto.createHmac('sha256', ''); const time = Date.now().toString(); hmac.update(time); hmac.update('POST'); hmac.update('/ping'); const contentHash = crypto.createHash('md5'); contentHash.update(JSON.stringify({ "dummy": 1, "data": 2 })); hmac.update(contentHash.digest('hex')); console.log(`HMAC ${time}:${hmac.digest('hex')}`); ``` apiKey, bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'connect user to bringin or onboard new users') and Jentic returns the matching # Bringin APIs Bringin APIs enable you to make Bitcoin on and off-ramp services available for your European customers. We provide a simple yet best-in-class crypto on and off-ramp solution with SEPA instant support at the best rates in the market. ## Use Cases ### 1. Offramp to bank directly This option is ideal if you want users to add a "Sell to bank" button - allowing users to offramp their Bitcoin to Euros in their bank without any issues. A set of APIs to create an offramp order to convert incoming Bitcoin deposits into Euros into Bringin's IBAN for users to withdraw anytime. **For this use case, you only need to focus on the User Onboarding and Offramp sections.** #### Key Features: - Create an offramp order by providing IP, amount, beneficiary details. API returns a Bitcoin Address and a lightning invoice - Once we receive Bitcoin to the provided address or invoice, we swap BTC to Euros at market rate - You initiate a bank transfer to users bank ### 2. Offramp to Bringin (2 days integration) Connect to the Bringin account to offer Bringin vIBAN and debit cards. Please contact us at support@bringin.xyz for detailed documentation and integration support for this option. ## Authentication While the APIs are available to the public to build with, we provide an `api-key` and `api-secret` for each company to make secure API calls. ### Request Headers All API requests must be accompanied by the following headers: | Header Parameter | Description | |------------------|-------------| | `api-key` | Contact us at info@bringin.xyz to obtain API key | | `Authorization` | A signature generated using the API Secret. Contact us at info@bringin.xyz to obtain the API secret. More information is below on generating a signature | | `Content-Type` | `application/json` | ### Environments The sandbox and production environments mirror each other, except for the base URL and your API keys. Please contact us at info@bringin.xyz to elevate your application to production. ### Request Signature Calculation You can calculate the value of the `Authorization` header by creating a SHA256HMAC digest of your request body, signed with your `API Secret`, in the following manner: #### Step 1: Get current UNIX timestamp ```javascript const time = Date.now().toString(); ``` #### Step 2: Stringify request body ```javascript const bodyString = JSON.stringify(body); // For a GET request, please use an empty body such as: // const bodyString = JSON.stringify({}); ``` #### Step 3: Calculate MD5 digest of request body Calculate the hex encoded MD5 digest of your request body exactly as it will be sent. For GET requests, please include an empty body `'{}'` that evaluates to an MD5 of `99914b932bd37a50b983c5e7c90ae93b`. ```javascript const requestContentHexString = CryptoJS.MD5(bodyString).toString(CryptoJS.enc.Hex); // For a GET request, the bodyString above for example would just be '{}' // and the calculated MD5 is 99914b932bd37a50b983c5e7c90ae93b ``` #### Step 4: Concatenate signature components ```javascript const signatureRawData = time + 'POST' + '/card/create' + requestContentHexString; ``` #### Step 5: Create SHA256 HMAC digest Use your API Secret to create a SHA256 HMAC digest in hex: ```javascript const apiSecret = ''; const requestSignatureHexString = CryptoJS.HmacSHA256(signatureRawData, apiSecret).toString(CryptoJS.enc.Hex); ``` #### Step 6: Create authorization header Finally, create your authorization header as follows, using the verb `'HMAC '` concatenated with the timestamp and the `requestSignatureHexString`, separated by a `:` ```javascript const authorizationHeader = 'HMAC ' + time + ':' + requestSignatureHexString; ``` ### Complete Example ```javascript import crypto from 'crypto'; const hmac = crypto.createHmac('sha256', ''); const time = Date.now().toString(); hmac.update(time); hmac.update('POST'); hmac.update('/ping'); const contentHash = crypto.createHash('md5'); contentHash.update(JSON.stringify({ "dummy": 1, "data": 2 })); hmac.update(contentHash.digest('hex')); console.log(`HMAC ${time}:${hmac.digest('hex')}`); ``` operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct # Bringin APIs Bringin APIs enable you to make Bitcoin on and off-ramp services available for your European customers. We provide a simple yet best-in-class crypto on and off-ramp solution with SEPA instant support at the best rates in the market. ## Use Cases ### 1. Offramp to bank directly This option is ideal if you want users to add a "Sell to bank" button - allowing users to offramp their Bitcoin to Euros in their bank without any issues. A set of APIs to create an offramp order to convert incoming Bitcoin deposits into Euros into Bringin's IBAN for users to withdraw anytime. **For this use case, you only need to focus on the User Onboarding and Offramp sections.** #### Key Features: - Create an offramp order by providing IP, amount, beneficiary details. API returns a Bitcoin Address and a lightning invoice - Once we receive Bitcoin to the provided address or invoice, we swap BTC to Euros at market rate - You initiate a bank transfer to users bank ### 2. Offramp to Bringin (2 days integration) Connect to the Bringin account to offer Bringin vIBAN and debit cards. Please contact us at support@bringin.xyz for detailed documentation and integration support for this option. ## Authentication While the APIs are available to the public to build with, we provide an `api-key` and `api-secret` for each company to make secure API calls. ### Request Headers All API requests must be accompanied by the following headers: | Header Parameter | Description | |------------------|-------------| | `api-key` | Contact us at info@bringin.xyz to obtain API key | | `Authorization` | A signature generated using the API Secret. Contact us at info@bringin.xyz to obtain the API secret. More information is below on generating a signature | | `Content-Type` | `application/json` | ### Environments The sandbox and production environments mirror each other, except for the base URL and your API keys. Please contact us at info@bringin.xyz to elevate your application to production. ### Request Signature Calculation You can calculate the value of the `Authorization` header by creating a SHA256HMAC digest of your request body, signed with your `API Secret`, in the following manner: #### Step 1: Get current UNIX timestamp ```javascript const time = Date.now().toString(); ``` #### Step 2: Stringify request body ```javascript const bodyString = JSON.stringify(body); // For a GET request, please use an empty body such as: // const bodyString = JSON.stringify({}); ``` #### Step 3: Calculate MD5 digest of request body Calculate the hex encoded MD5 digest of your request body exactly as it will be sent. For GET requests, please include an empty body `'{}'` that evaluates to an MD5 of `99914b932bd37a50b983c5e7c90ae93b`. ```javascript const requestContentHexString = CryptoJS.MD5(bodyString).toString(CryptoJS.enc.Hex); // For a GET request, the bodyString above for example would just be '{}' // and the calculated MD5 is 99914b932bd37a50b983c5e7c90ae93b ``` #### Step 4: Concatenate signature components ```javascript const signatureRawData = time + 'POST' + '/card/create' + requestContentHexString; ``` #### Step 5: Create SHA256 HMAC digest Use your API Secret to create a SHA256 HMAC digest in hex: ```javascript const apiSecret = ''; const requestSignatureHexString = CryptoJS.HmacSHA256(signatureRawData, apiSecret).toString(CryptoJS.enc.Hex); ``` #### Step 6: Create authorization header Finally, create your authorization header as follows, using the verb `'HMAC '` concatenated with the timestamp and the `requestSignatureHexString`, separated by a `:` ```javascript const authorizationHeader = 'HMAC ' + time + ':' + requestSignatureHexString; ``` ### Complete Example ```javascript import crypto from 'crypto'; const hmac = crypto.createHmac('sha256', ''); const time = Date.now().toString(); hmac.update(time); hmac.update('POST'); hmac.update('/ping'); const contentHash = crypto.createHash('md5'); contentHash.update(JSON.stringify({ "dummy": 1, "data": 2 })); hmac.update(contentHash.digest('hex')); console.log(`HMAC ${time}:${hmac.digest('hex')}`); ``` integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.