Use Cases

Explore Longhorn use cases below.

DApps

Who are they?

Blockchain-based decentralized programs, tools or applications that require accessing, storing, or analyzing data from the blockchains.

How do they access blockchain data?

DApp developers have a choice to either

  • Run nodes
  • Build your own tools for processing blockchain transactions
  • Work with API services to access transactions from multiple blockchains

Who do they use to integrate the API?

A developer. No need for: a node specialist, an infrastructure engineer, nor the infrastructure itself. However, you can request additional blockchains, or altcoins, to be supported by Longhorn.

Which APIs would they use?

All Blockchains

Ethereum Specific

TestNet Specific

  • Create Signed Transaction (Coming 2019)

Other Tools

  • Webhooks (coming 2019)
  • Other APIs can be built upon request

Connecting digital wallets with API

Currently Supporting To Support Next
Bitcoin (BTC) Bitcoin Cash (BCH)
Ethereum (ETH) Bitcoin SV (BSV)
Litecoin (LTC) & Litecoin TestNet EOS (EOS)
Dash (DASH) Monero (XMR)
Dogecoin (DOGE) ZCash (ZEC)

Development Specs:

  • Unified API – JSON packages are defined in a common architecture allowing for seamless interaction with multiple blockchains; therefore, simplifying your code substantially.
  • Indexers – Longhorn Memory-mapped Database – A patent pending database technology to advance how blockchain transactions are stored and mathematically retrieved
  • Stability – Your applications will always be extremely responsive, stable, and reliable. Longhorn is designed to serve as a bridge between your application and the nodes. Because Longhorn does not slam the nodes with every transaction request, Longhorn is far more stable despite significant amounts of traffic.
  • Speed – Longhorn is 1000’s of times faster than Microsoft SQL and ~16 times faster than Microsoft Azure, allowing us to process and store every transaction since the creation of each blockchain to now – nearly instantaneously.
  • Scale – Because of all the reasons listed above, we’re able to easily scale. This means you can scale with rapid customer growth or data heavy features. Options for dedicated hardware and bare metal are available upon request. Additional altcoins or blockchains can also be supported upon request.

Digital Wallets

Who are they?

Single- or multi- cryptocurrency Hieratical Deterministic (HD) or Deterministic or classic wallets; hardware or software wallets.

How do they access blockchain data?

Wallet providers have a choice to either

  • Run nodes
  • Build your own tools for processing blockchain transactions
  • Work with API services to access transactions from multiple blockchains

Who do they use to integrate the API?

A developer. No need for: a node specialist, an infrastructure engineer, nor the infrastructure itself. However, you can request additional blockchains, or altcoins, to be supported by Longhorn.

Which APIs would they use?

All Blockchains

TestNet Specific

  • Create Signed Transaction (Coming 2019)

Other Tools

  • Webhooks (coming 2019)
  • Other APIs can be built upon request

Connecting digital wallets with API

Currently Supporting To Support Next
Bitcoin (BTC) Bitcoin Cash (BCH)
Ethereum (ETH) Bitcoin SV (BSV)
Litecoin (LTC) & Litecoin TestNet EOS (EOS)
Dash (DASH) Monero (XMR)
Dogecoin (DOGE) ZCash (ZEC)

Development Specs:

  • Unified API – JSON packages are defined in a common architecture allowing for seamless interaction with multiple blockchains; therefore, simplifying your code substantially.
  • Indexers – Longhorn Memory-mapped Database – A patent pending database technology to advance how blockchain transactions are stored and mathematically retrieved
  • Stability – Your applications will always be extremely responsive, stable, and reliable. Longhorn is designed to serve as a bridge between your application and the nodes. Because Longhorn does not slam the nodes with every transaction request, Longhorn is far more stable despite significant amounts of traffic.
  • Speed – Longhorn is 1000’s of times faster than Microsoft SQL and ~16 times faster than Microsoft Azure, allowing us to process and store every transaction since the creation of each blockchain to now – nearly instantaneously.
  • Scale – Because of all the reasons listed above, we’re able to easily scale. This means you can scale with rapid customer growth or data heavy features. Options for dedicated hardware and bare metal are available upon request. Additional altcoins or blockchains can also be supported upon request.

Accounting & Finance

Who are they?

Businesses offering accounting & finance applications for B2B or B2C using blockchain technology to replace traditional database

How do they access blockchain data?

Companies have a choice to either

  • Run nodes
  • Build your own tools for processing blockchain transactions
  • Work with API services to access transactions from multiple blockchains

Who do they use to integrate the API?

A developer. No need for: a node specialist, an infrastructure engineer, nor the infrastructure itself. However, you can request additional blockchains, or altcoins, to be supported by Longhorn.

Which APIs would they use?

All Blockchains

Ethereum Specific

Other Tools

  • Webhooks (coming 2019)
  • Other APIs can be built upon request

Connecting accounting & finance applications with API

Currently Supporting To Support Next
Bitcoin (BTC) Bitcoin Cash (BCH)
Ethereum (ETH) Bitcoin SV (BSV)
Litecoin (LTC) & Litecoin TestNet EOS (EOS)
Dash (DASH) Monero (XMR)
Dogecoin (DOGE) ZCash (ZEC)

Development Specs:

  • Unified API – JSON packages are defined in a common architecture allowing for seamless interaction with multiple blockchains; therefore, simplifying your code substantially.
  • Indexers – Longhorn Memory-mapped Database – A patent pending database technology to advance how blockchain transactions are stored and mathematically retrieved
  • Stability – Your applications will always be extremely responsive, stable, and reliable. Longhorn is designed to serve as a bridge between your application and the nodes. Because Longhorn does not slam the nodes with every transaction request, Longhorn is far more stable despite significant amounts of traffic.
  • Speed – Longhorn is 1000’s of times faster than Microsoft SQL and ~16 times faster than Microsoft Azure, allowing us to process and store every transaction since the creation of each blockchain to now – nearly instantaneously.
  • Scale – Because of all the reasons listed above, we’re able to easily scale. This means you can scale with rapid customer growth or data heavy features. Options for dedicated hardware and bare metal are available upon request. Additional altcoins or blockchains can also be supported upon request.

Crypto Payment Platforms

Who are they?

Crypto currency exchange platforms such as Kraken, Coinbase, and Binance

How do they access blockchain data?

Exchanges have a choice to either

  • Run nodes
  • Build your own tools for processing blockchain transactions
  • Work with API services to access transactions from multiple blockchains

Who do they use to integrate the API?

A developer. No need for: a node specialist, an infrastructure engineer, nor the infrastructure itself.

Which APIs would they use?

All Blockchains

TestNet Specific

  • Create Signed Transaction (Coming 2019)

Other Tools

  • Webhooks (coming 2019)
  • Other APIs can be built upon request

Connecting crypto trading platforms / exchanges with API

Currently Supporting To Support Next
Bitcoin (BTC) Bitcoin Cash (BCH)
Ethereum (ETH) Bitcoin SV (BSV)
Litecoin (LTC) & Litecoin TestNet EOS (EOS)
Dash (DASH) Monero (XMR)
Dogecoin (DOGE) ZCash (ZEC)

Development Specs:

  • Unified API – JSON packages are defined in a common architecture allowing for seamless interaction with multiple blockchains; therefore, simplifying your code substantially.
  • Indexers – Longhorn Memory-mapped Database – A patent pending database technology to advance how blockchain transactions are stored and mathematically retrieved
  • Stability – Your applications will always be extremely responsive, stable, and reliable. Longhorn is designed to serve as a bridge between your application and the nodes. Because Longhorn does not slam the nodes with every transaction request, Longhorn is far more stable despite significant amounts of traffic.
  • Speed – Longhorn is 1000’s of times faster than Microsoft SQL and ~16 times faster than Microsoft Azure, allowing us to process and store every transaction since the creation of each blockchain to now – nearly instantaneously.
  • Scale – Because of all the reasons listed above, we’re able to easily scale. This means you can scale with rapid customer growth or data heavy features. Options for dedicated hardware and bare metal are available upon request. Additional altcoins or blockchains can also be supported upon request.

Crypto Trading Platforms / Exchanges

Who are they?

Crypto currency exchange platforms such as Kraken, Coinbase, and Binance

How do they access blockchain data?

Exchanges have a choice to either

  • Run nodes
  • Build your own tools for processing blockchain transactions
  • Work with API services to access transactions from multiple blockchains

Who do they use to integrate the API?

A developer. No need for: a node specialist, an infrastructure engineer, nor the infrastructure itself.

Which APIs would they use?

All Blockchains

TestNet Specific

  • Create Signed Transactions (Coming 2019)

Other Tools

  • Webhooks (coming 2019)
  • Other APIs can be built upon request

Connecting crypto trading platforms / exchanges with API

Currently Supporting To Support Next
Bitcoin (BTC) Bitcoin Cash (BCH)
Ethereum (ETH) Bitcoin SV (BSV)
Litecoin (LTC) & Litecoin TestNet EOS (EOS)
Dash (DASH) Monero (XMR)
Dogecoin (DOGE) ZCash (ZEC)

Development Specs:

  • Unified API – JSON packages are defined in a common architecture allowing for seamless interaction with multiple blockchains; therefore, simplifying your code substantially.
  • Indexers – Longhorn Memory-mapped Database – A patent pending database technology to advance how blockchain transactions are stored and mathematically retrieved
  • Stability – Your applications will always be extremely responsive, stable, and reliable. Longhorn is designed to serve as a bridge between your application and the nodes. Because Longhorn does not slam the nodes with every transaction request, Longhorn is far more stable despite significant amounts of traffic.
  • Speed – Longhorn is 1000’s of times faster than Microsoft SQL and ~16 times faster than Microsoft Azure, allowing us to process and store every transaction since the creation of each blockchain to now – nearly instantaneously.
  • Scale – Because of all the reasons listed above, we’re able to easily scale. This means you can scale with rapid customer growth or data heavy features. Options for dedicated hardware and bare metal are available upon request. Additional altcoins or blockchains can also be supported upon request.

Data Aggregators

Who are they?

Blockchain data is financial data. Data aggregators provide analysis for detecting & investigating fraud, targeted marketing, identifying macro trends, etc., i.e. Reuters

How do they access blockchain data?

Companies have a choice to either

  • Run nodes
  • Build your own tools for processing blockchain transactions
  • Work with API services to access transactions from multiple blockchains

Who do they use to integrate the API?

A developer. No need for: a node specialist, an infrastructure engineer, nor the infrastructure itself. Alternatively, you can hire our team to develop a custom solution.

Which APIs would they use?

All Blockchains

Ethereum Specific

Other Tools

  • Webhooks (coming 2019)
  • Other APIs can be built upon request

Connecting data aggregators with API

Currently Supporting To Support Next
Bitcoin (BTC) Bitcoin Cash (BCH)
Ethereum (ETH) Bitcoin SV (BSV)
Litecoin (LTC) & Litecoin TestNet EOS (EOS)
Dash (DASH) Monero (XMR)
Dogecoin (DOGE) ZCash (ZEC)

Development Specs:

  • Unified API – JSON packages are defined in a common architecture allowing for seamless interaction with multiple blockchains; therefore, simplifying your code substantially.
  • Indexers – Longhorn Memory-mapped Database – A patent pending database technology to advance how blockchain transactions are stored and mathematically retrieved
  • Stability – Your applications will always be extremely responsive, stable, and reliable. Longhorn is designed to serve as a bridge between your application and the nodes. Because Longhorn does not slam the nodes with every transaction request, Longhorn is far more stable despite significant amounts of traffic.
  • Speed – Longhorn is 1000’s of times faster than Microsoft SQL and ~16 times faster than Microsoft Azure, allowing us to process and store every transaction since the creation of each blockchain to now – nearly instantaneously.
  • Scale – Because of all the reasons listed above, we’re able to easily scale. This means you can scale with rapid customer growth or data heavy features. Options for dedicated hardware and bare metal are available upon request. Additional altcoins or blockchains can also be supported upon request.

Documentation

Getting Started

Longhorn’s patent-pending Memory-mapped database technology make interacting with blockchains reliable and fast, in real-time. To get started, sign up for a Longhorn account.

BullPay provides a standards-based REST interface which enables application developers to interact in a powerful, yet simple way with their Longhorn account. Using the Longhorn API, clients can send and confirm transactions, view balances, retrieve real-time transactions, view historical ledger entries, and much more. Developers may call the API directly over HTTPS using the language of their choice.

API Pattern

All supported blockchains follow this pattern:

https://longhorn.bullpay.com/api/$METHOD/

API Summaries

All Blockchains

Ethereum Specific

Changelog and Errors

Our documentation is powered by Google Group. Be sure to subscribe to Longhorn’s mailing list to receive information on new additions and changes to Longhorn’s API and Block Explorer. If there’s an error or you’d like to suggest a change, please email us directly at longhorn@bullpay.com.

Errors

Error Code Meaning
200 – OK Everything worked as expected.
400 – Bad Request The request was unacceptable, often due to missing a required parameter.
401 – Unauthorized No valid API key provided.
402 – Request Failed The parameters were valid but the request failed.
404 – Not Found The requested resource doesn’t exist.
409 – Conflict The request conflicts with another request (perhaps due to using the same idempotent key).
500, 502, 503, 504 – Server Errors Something went wrong on Bullpay’s end. (These are rare.)

Try It

We have Swagger set up to interact with our APIs. Try it here.

Development

All Blockchains

Send Transaction

The Send Transaction Object

Example Request

curl -X POST -H Content-Type: application/json" -H "apiKey: {YOUR_API_KEY}" -d "{TRANSACTION_HASH}" https://longhorn.bullpay.com/api/Send/6

Example Response

"success"

Send a signed raw transaction for a particular gateway over the Longhorn network.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
transaction The signed raw transactions.

POST Transactions

Send transaction.

HTTP Request

POST
https://longhorn.bullpay.com/api/Send/{gatewayId}

Get Address Summary

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetAddressSummary/2/14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS

Example Response

{
    "recieved": 3352097371,
    "sent": 3115131880,
    "balance": 236965491,
    "totalTransactions": 37
}

The Get Address Summary Object

Get the summary of a wallet address for a particular blockchain.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
address The wallet address to locate.

Get Address Summary

Get the summary of a wallet address for a particular blockchain.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetAddressSummary/{gatewayId}/{address}

Get Transactions

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetTransactions/6/LfcUcxALy1gSeqZLrixAm4ETZbEWA7GLat/1/10

Example Response

{
    "address": LfcUcxALy1gSeqZLrixAm4ETZbEWA7GLat,
    "totalTransactions": 2,
    "totalSent": 5000000000,
    "totalRecieved": 5000000000,
    "balance": 0,
    "txs":[
        {
            "txid": 5c8f31da75ab5bff67e232f6bdeaa693eef9b2ff344a300dbce6def3c880b4e5,
            "acruedReceieved": 5000000000,
            "acruedSent": 5000000000,
            "balance": 0,
            "block": 22480,
            "transactionDate": "11/1/2011 1:59:50 AM",
            "confirmations": 1503170
        },
        {
            "txid": 1ea3f171d4b77016f7af96e2f43b7298529ef6f987a5f1c9fe560765f1565afd,
            "acruedReceieved": 5000000000,
            "acruedSent": 0,
            "balance": 5000000000,
            "block": 100,
            "transactionDate": "10/13/2011 3:06:06 AM",
            "confirmations": 1525550
        }
    ]
}

The Get Transactions Object

Get information about:

  • A wallet address summary of a gateway:
    • Total number of transactions
    • Total amounts sent and received
    • Current balance of all known transactions
  • Transactions:
    • Transaction ID
    • Running Input (received) – Total
    • Running Output (sent) – Total
    • Running Balance (Input (received) – Output (sent))
    • The block the transaction appeared in
    • Date/time the block is stamped with, provided by miners
    • The number of confirmations, which is the number of blocks since the first block the transaction was mined

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
address The wallet address to locate.
start* The address to start with.
count The wallet address to locate.

* The start cannot be 0. Records are stored in a 1-based array.

Get Transactions

Get transactions for a wallet address of a gateway. Results from memory pool will also be displayed. Memory pool transactions are transactions that have been submitted to the network but are not contained within a block yet.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetTransactions/{gatewayId}/{address}/{start}/{count}

Get Unspent Outputs

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetUnspentOutputs/2/14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS/1000

Example Response

[
    {
        "txid": 1d6580dcd979951bd600252b741c22a3ea8e605e43168f8452c68915c3ea2bf3,
        "address": 14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS,
        "outputIndex": 58,
        "value": 888,
        "scriptPubKey": OP_DUP OP_HASH160 27fb23e2cb26c1a3292073455db8f6fa19fc0edf OP_EQUALVERIFY OP_CHECKSIG
    },
    {
        "txid": ad2b58216d977597b357916f1ef0773864bee73f34c541f55c393b6598204bee,
        "address": 14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS,
        "outputIndex": 16,
        "value": 666,
        "scriptPubKey": OP_DUP OP_HASH160 27fb23e2cb26c1a3292073455db8f6fa19fc0edf OP_EQUALVERIFY OP_CHECKSIG
    }
]

The Get Unspent Outputs Object

Get unspent transactions for the specified address on a blockchain.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
address The wallet address to get unspent transactions for.

Get Unspent Outputs

Get unspent transactions for the specified address on a blockchain.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetUnspentOutputs/{gatewayId}/{address}/{amount}

Get Transaction

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetTransaction/6/1ea3f171d4b77016f7af96e2f43b7298529ef6f987a5f1c9fe560765f1565afd

Example Response

{
    "gatewayId": 6,
    "hash": "1ea3f171d4b77016f7af96e2f43b7298529ef6f987a5f1c9fe560765f1565afd",
    "total": "5000000000",
    "blockHeight": 100,
    "outputs":[
        {
        "address": "LfcUcxALy1gSeqZLrixAm4ETZbEWA7GLat",
        "amount": "5000000000",
        "script": "4104458bf7d944ce58c007d0f16fa54c0640694568954e162c06be0a0cba7275714b6672c589e7393fa48f8a5f6b6259061d394e9db005651d1bb28349d31339daa8ac",
        "index": 0,
        }
    ],
    "inputs":[
        {
        "script": "049e55964e010a",
        "previous_txid": "049e55964e010a",
        "index": 0,
        }
    ],
    "blockHash": "97ea5cb96baa9448d494eb083a7b1b6884e99a89522d89150e0b4378c742a6da",
    "raw": "01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff07049e55964e010affffffff0100f2052a01000000434104458bf7d944ce58c007d0f16fa54c0640694568954e162c06be0a0cba7275714b6672c589e7393fa48f8a5f6b6259061d394e9db005651d1bb28349d31339daa8ac00000000",
    "txdate": "10/13/2011 3:06:06 AM",
}

The Get Transaction Object

Get a transaction for a wallet address of a gateway.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
taxid The transaction ID to locate.

Get Transaction

Get transaction.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetTransaction/{gatewayId}/{txid}

Get Raw Transaction

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetRawTransaction/6/1ea3f171d4b77016f7af96e2f43b7298529ef6f987a5f1c9fe560765f1565afd

Example Response

"01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff07049e55964e010affffffff0100f2052a01000000434104458bf7d944ce58c007d0f16fa54c0640694568954e162c06be0a0cba7275714b6672c589e7393fa48f8a5f6b6259061d394e9db005651d1bb28349d31339daa8ac00000000"

The Get Raw Transaction Object

Get a raw transaction for a wallet address of a gateway.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
taxid The transaction ID to locate.

Get Raw Transaction

Get a raw transaction.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetRawTransaction/{gatewayId}/{txid}

Get Gateways

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59" 
https://longhorn.bullpay.com/api/GetGateways

Example Response

{
    "Bitcoin": 2,
    "Ethereum": 4,
    "Litecoin": 6,
    "Dash": 7,
    "Dogecoin": 8,
    "LitecoinTestnet": 43,
}

The Get Gateways Object

Get a list of all blockchain gateways.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.

Get Gateways

Get gateways.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetRawTransaction/{gatewayId}/{txid}

Block Height To Hash

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/BlockHeightToHash/6/100

Example Response

"97ea5cb96baa9448d494eb083a7b1b6884e99a89522d89150e0b4378c742a6da"

The Block Height To Hash Object

Convert a block height to a block hash.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
height The height to convert.

Block Height To Hash

Convert a block height to a block hash.

HTTP Request

GET
https://longhorn.bullpay.com/api/BlockHeightToHash/{gatewayId}/{height}

Block Hash To Height

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/BlockHashToHeight/6/97ea5cb96baa9448d494eb083a7b1b6884e99a89522d89150e0b4378c742a6da

Example Response

100

The Block Hash To Height Object

Convert a block hash to a block height.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
hash The hash to convert.

Block Hash To Height

Convert a block hash to a block height.

HTTP Request

GET
https://longhorn.bullpay.com/api/BlockHeightToHash/{gatewayId}/{hash}

Get Stats

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59" 
https://longhorn.bullpay.com/api/GetGateways

Example Response

{
    "gatewayId": 6,
    "height": 1531735,
    "blockhash": 22b3373254d2dae27f6541ad22f63963e2028e04dacbd52fd39657e64e04aca3,
    "previousBlockhash": 9a0215f1e22afc954932c0d5ab89a6103251fa41a1ecd32aed5922aaff760348,
    "totalTransactions": 29360362,
    "totalAddressesIndexed": 158202738,
    "version": "1.0 alpha"
}

The Get Stats Object

Get the indexers statistics for the supplied gateway.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.

Get Stats

Get the indexers statistics for the supplied gateway.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetStats/{gatewayId}

Ethereum Specific

Get Contracts

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetContracts/4/1/10

Example Response

{
    "contracts":[
        {
        "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
        "blockNumber": "0x61f2cb",
        "contractAddress": "0x00000000007f6202ba718df41ec639b32dd7fbcf",
        "cumulativeGasUsed": "0x5ab2d7",
        "from": "0x387788908f8380536385cebdead4280a3919d0de",
        "gasUsed": "0x507b1a",
        "logs":[
            {
            "address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
            "topics":[
                "0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925",
                "0x00000000000000000000000000000000007f6202ba718df41ec639b32dd7fbcf",
                "0x0000000000000000000000002240dab907db71e64d3e0dba4800c83b5c502d4e"
            ],
            "data": "0xff00000000000000000000000000000000000000000000000000000000000000",
            "blockNumber": "0x61f2cb",
            "transactionHash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef",
            "transactionIndex": "0xb",
            "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
            "logIndex": "0xa",
            "removed": false
            },
            {
            "address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
            "topics":[
                "0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925",
                "0x00000000000000000000000000000000007f6202ba718df41ec639b32dd7fbcf",
                "0x00000000000000000000000014fbca95be7e99c15cc2996c6c9d841e54b79425"
            ],
            "data": "0xff00000000000000000000000000000000000000000000000000000000000000",
            "blockNumber": "0x61f2cb",
            "transactionHash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef",
            "transactionIndex": "0xb",
            "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
            "logIndex": "0xb",
            "removed": false
            },
            {
            "address": "0x89d24a6b4ccb1b6faa2625fe562bdd9a23260359",
            "topics":[
                "0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925",
                "0x00000000000000000000000000000000007f6202ba718df41ec639b32dd7fbcf",
                "0x00000000000000000000000014fbca95be7e99c15cc2996c6c9d841e54b79425"
            ],
            "data": "0xff00000000000000000000000000000000000000000000000000000000000000",
            "blockNumber": "0x61f2cb",
            "transactionHash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef",
            "transactionIndex": "0xb",
            "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
            "logIndex": "0xc",
            "removed": false
            },
        ]},
    ],
    "totalRows": 2037948
}

The Get Contracts Object

List contracts on the Ethereum network.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
start* The address to start with.
count The wallet address to locate.

* The start cannot be 0. Records are stored in a 1-based array.

Get Contracts

Get contracts.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetContracts/{gatewayId}/{start}/{count}

Get Contract

Example Request

curl -X GET -H Content-Type: application/json" -H "apiKey: test_c21f4360-762f-47c1-8964-d0c2322f5d59"
https://longhorn.bullpay.com/api/GetContract/4/0x00000000007f6202ba718df41ec639b32dd7fbcf

Example Response

{
    "contract":[
        {
        "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
        "blockNumber": "0x61f2cb",
        "contractAddress": "0x00000000007f6202ba718df41ec639b32dd7fbcf",
        "cumulativeGasUsed": "0x5ab2d7",
        "from": "0x387788908f8380536385cebdead4280a3919d0de",
        "gasUsed": "0x507b1a",
        "logs":[
            {
            "address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
            "topics":[
                "0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925",
                "0x00000000000000000000000000000000007f6202ba718df41ec639b32dd7fbcf",
                "0x0000000000000000000000002240dab907db71e64d3e0dba4800c83b5c502d4e"
            ],
            "data": "0xff00000000000000000000000000000000000000000000000000000000000000",
            "blockNumber": "0x61f2cb",
            "transactionHash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef",
            "transactionIndex": "0xb",
            "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
            "logIndex": "0xa",
            "removed": false
            },
            {
            "address": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
            "topics":[
                "0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925",
                "0x00000000000000000000000000000000007f6202ba718df41ec639b32dd7fbcf",
                "0x00000000000000000000000014fbca95be7e99c15cc2996c6c9d841e54b79425"
            ],
            "data": "0xff00000000000000000000000000000000000000000000000000000000000000",
            "blockNumber": "0x61f2cb",
            "transactionHash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef",
            "transactionIndex": "0xb",
            "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47",
            "logIndex": "0xb",
            "removed": false
            },
        ],
        "logsBloom": "0x0000000000000000000000000000000000000000000000000000000000000000000...",
        "status": "0x1",
        "to": null,
        "transactionHash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef",
        "transactionIndex": "0xb"
        },
        "tx":
        {
        "blockHash": "0x613a6db7e0ec5c32920ef30ea239ddba34cb0c22a344b2c4c176ac11d0872c47...",
        "blockNumber": "0x61f2cb",
        "from": "0x387788908f8380536385cebdead4280a3919d0de",
        "gas": "0x53ec60",
        "gasPrice": "0x2cb417800",
        "hash": "0x8e6d53b645412953753961c5f9ffe51d63b28d386bd4ae9d79892e485efabcef...",
        "input": "0x6080604052660aa87bee538000624000005563095ea7b3600052732240dab907db71e64d",
        "nonce": "0x58",
        "to": null,
        "transactionIndex": "0xb",
        "value": "0x0",
        "v": "0x25",
        "r": "0x5ffc4da63f04cbd2efccd534a5cba30c73684fc925ecb3437b6b5e2b629acb8a",
        "s": "0x283ab7a6d1a69b80095723a4e60e9b61a3a1fa2ea72a11aafaebef2b6c9ea837"
        }
    ],
}

The Get Contract Object

Get an Ethereum contract.

Noteworthy Attributes

Attribute Description
apiKey This is your API Key.
gatewayId This gateway ID to be used for this call.
address The wallet address to locate.

Get Contract

Get contract.

HTTP Request

GET
https://longhorn.bullpay.com/api/GetContracts/{gatewayId}/{start}/{count}

Resources

Security & Performance

Our approach:

Security is top priority for us at BullPay. Our clients entrust sensitive data to our care and we keep it safe. We have taken security seriously from the beginning and the mission of keeping BullPay and the clients we service protected is the responsibility of our whole company.

Our promise:

Why take our word for it? We are OWASP ASVS Level 3 certified by Praetorian, an expert security firm. Achieving OWASP ASVS Level 3 (the highest category) provides assurance, verified by third party auditors, that BullPay has an effective security program ensuring your data is always protected. View our OWASP ASVS Level 3 certificate.

If you’re interested in working with BullPay and have more questions about our security we would love to share more. Just drop us a line!

Our infrastructure:

BullPay’s computing infrastructure is provided by OVH, a secure cloud services platform. OVH’s cloud infrastructure has been accredited under ISO 27001:2005. Its security, management, risk assessment norms and associated processes has been accredited under ISO 27002 and ISO 27005. OVH has obtained SOC 1 and 2 type II certifications for 3 data centers in France and 1 in Canada, proof of its secured Private Cloud solution. Furthermore, OVH is a PCI certified vendor and is committed to the core principles of GDPR.

We have committed to and gained OWASP Level 3 requirements, the latest Next Generation firewall and PCI Security best practices to ensure that our applications and data are protected and always accessible. Access to our infrastructure is tightly controlled and monitored. In addition to strong security controls, BullPay ensures that the data it collects remains available through full, daily backups, retained for 30 days and tested weekly.

Our applications:

We employ secure coding practices and ensure we’re protected against the OWASP ASVS Level 3. All of the BullPay applications and services undergo well-defined quality assurance / quality control protocols.

All user passwords are securely hashed; passwords are never stored in plain text. All data access is protected by a role-based access-control mechanism, which only lets users view data for which they have permission. It’s impossible for users to view data from organizations other than their own.

Our internal processes:

Only authorized employees have access to our production infrastructure, and passwords are strictly regulated. We limit access to customer data to the employees who need it to provide support and troubleshooting on our customer’s behalf. Accessing customer data is done solely on an as-needed basis, and only when approved by the customer (i.e. as part of a support request), or to provide support, maintenance and upgrades for custom code compatibility.

This site uses cookies

By continuing to use this site, you are agreeing to our use of cookies.
See Privacy Policy.

We are excited to announce a fresh new redesign of Google Trends!

We have added new features and simplified our navigation to make it easier to explore data based stories.