BRIACOIN API
Webmasters
Documentation on the use of the service, basic queries, server responses and how to start using.
DOCUMENTATION
Automatic payment acceptance on sites.
Use of the payment service occurs through POST requests On the secure communication channel with the node:

https://api.briacoin.com/api/
All incoming and outgoing requests contain JSON strings.

Authorization of most requests occurs through the mechanism Google 2FA , libraries for its use exist for such languages programming like: PHP, Node.JS, Ruby, Python and others.

Account registration


Request to the server:

{
"method": "createaccount",
"backurl": "https://myshop.com/accept.php"
}
"Createaccount" is the method for registering a new account (user) in payment system;
"Backurl" - the URL to which the merchant will report a successful payment POST request *.

* Please note - your server should use Only valid certificates!

Server Response:

{
"result": {
"status": "ok",
"userid": 1,
"secret": "qta3whcytmysb2tq",
"balance": 0.0,
"backurl": "https://myshop.com/accept.php",
"timestamp": 1493195829
}
}
"userid" - the assigned ID for the new account, will be used in For authorization;
"secret" is a hash string for generating the Google 2FA key.

Account updates (changes)


Request to the server:

{
"method": "updateaccount",
"backurl": "https://newshop.net/payok/",
"userid": 1,
"key": "490321"
}
"updateaccount" is the method for registering a new account (user) in payment system;
"Backurl" - the URL to which the merchant will report a successful payment POST request;
"userid" - the account ID for which the data is changing;
"key" is the generated Google 2FA key.

Server Response:

{
"result": {
"status": "ok",
"userid": 1,
"backurl": "http://newshop.net/payok/",
"timestamp": 1493197926
}
}
"userid" - Account ID,
"Backurl" - the URL to which the merchant will report a successful payment POST request.

Checking account balance


Request a server:

{
"method": "getaccountbalance",
"userid": 1,
"key": "832712"
}
"balance" - method of requesting account balance;
"Userid" - Account ID whose balance is requested;
"key" is the generated Google 2FA key.

Server Response:

{
"result": {
"status": "ok",
"userid": 1,
"balance": 0.0,
"timestamp": 1493198052
}
}
"Userid" - Account ID of the requested account;
"balance" is the current balance.

Create an order


Request a server:

{
"method": "createorder",
"amount": 12.50,
"userid": 1,
"key": "209843"
}
"Order" - the method of creating a new order;
"Amount" - the amount to be paid for this order;
"key" is the generated Google 2FA key.

Server Response:

{
"result": {
"status": "ok",
"userid": 1,
"orderid": 1,
"wallet": «Bdr6RFA2GXhjFAPDmV3WHP7za5BHPYMKjT",
"amount": 12.5,
"timestamp": 1493195900
}
}
"userid" - account ID (the owner of the order, payment on the order is received on account balance)
"orderid" - ordinal order ID;
"wallet" - a coin purse for the transfer of coins for payment of an order;
"amount" is the amount to be paid for this order.

Check order status


Request a server:

{
"method": "getorderstatus",
"orderid": 1,
"userid": 1,
"key": "398402"
}
"Orderstatus" - the method of requesting the order status;
"Orderid" - the order number of the payment order;
"Userid" - the ID of your user from whom the order was placed;
"key" is the generated Google 2FA key.

Server Response:

{
"result": {
"status": "ok",
"userid": 1,
"orderid": 1,
"wallet": «Bdr6RFA2GXhjFAPDmV3WHP7za5BHPYMKjT",
"amount": 10.0,
"paid": 0.0,
"orderstatus": "new",
"timestamp": 1493200005
}
}
"Userid" - the ID of your user from whom the order was placed;
"Orderid" - the order number of the payment order;
"Wallet" - a purse for the transfer of coins (this is in case, if forgotten)
"Amount" - the amount to be paid for this order;
"Paid" - received coins for this order;

"orderstatus" - order status:

   The order status can have three basic statuses:
     "new" - new (unpaid);
     "part" - Not fully paid (in part);
     "close" - paid and closed (funds transferred to the account balance).

Transfer of coins (inference)


Request a server:

{
"method": "transfertoaddress",
"userid": 1,
"wallet": «BN9VuoMSk3LfVdars9PUntmv8r5ckHKnUZ",
"amount": 3.234,
"key": "398402"
}
"Transfertoaddress" - method of transferring coins from the account balance;
"Userid" - account ID from the balance of which the funds are transferred;
"Wallet" - a coin for which coins will be withdrawn

"Amount" - the amount of transfer (output)
"key" is the generated Google 2FA key.

Server Response:

{
"result": {
"status": "ok",
"userid": 2,
"txid": "7b76bf262f89be0dc9d17cd5d28d8fc155a1a3de57023b2ba1eeaf4b1ac7faeb",
"timestamp": 1493225903
}
}
"Userid" - account ID from the balance of which the funds are transferred;
"txid" is the hash of the transaction.

POST request to successful payment URL


On the successful payment URL, the merchant sends the following data:

{
:userid => 1,
:orderid => 23,
:amount => 2.0,
:key => "022637",
:timestamp => 1493228072
}
": Userid" - Account ID in the merchant system;
": Orderid" - order ID in the merchant system;
": Amount" - the cost of the order, upon payment;
": Key" - the generated reverse key by the Google 2FA server.

Error processing


Example of a server response when an error occurs:

{
"result": {
"status": "error",
"data": "Authorization filed!",
"timestamp": 1493195969
}
}
"error" - error return method;
"data" - the error description.

Main advantages of the service
Advantages and highlights of the exchange and payment service on the basis of the BriaCoin crypto currency.

Innovative technologies. We follow the development of IT technologies and apply only the most relevant and modern programming techniques in our developments.

High speed of network operation. Quick confirmation of translations. You need 3 network confirmations to credit funds to your balance. The network operates in real time. In most cases, 3-10 confirmations take less than 1 minute.

Reliability and safety. When working with the APIs of the service, Google's 2FA technologies and a secure communication channel using the HTTPS protocol are used.
Explorer blocks and transactions network BriaCoin:
BRIACOIN
P2P CRYPTO CURRENCY NETWORK
Crypto-currency: BriaCoin [BRIA]
Founder: BRIASTORM tm
Year of Foundation: 07.12.2016
The maximum number of coins: 3,000,000 BRIA
Coins generation Algorithm: PoS
Algorithm of encryption, processing of transactions
and partial generation: Scrypt
POW Premine: 1 %
Generating block: 1 min.
Annual return: from 3 %
Minimum fee P2P transactions: 0.0001 BRIA
High anonymity
Additional "stealth" addressing
Platform smart contracts
Pleasant and convenient interface
When developing the user interface, such technologies as Bootstrap, HTML5, CSS3 and jQuery were used. You can use your personal cabinet on any device. The work does not bring difficulties and inconvenience. In each section there is a help panel, and in the most difficult situations you can create a request to the technical support.

API DOCUMENTATION IN PDF FORMAT




PDF | API DOCUMENTATION




Here you can download the documentation and presentation on the BriaCoin API.

DOWNLOAD BRIACOIN WALLET


Version 0.7.5 dated 7/02/2018


Virus scan
MD5: B6E8B248E124B9797F3EC1DF9B3799DD

Soon a stable version of the wallet for UNIX/LINUX will be released!




Exchange of cryptocurrency


Ore.Bz trading pairs BRIA/USD | BRIA/BTC | BRIA/ETH | BRIA/GBC

Ealtyn.io trading pairs BRIA/USD | BRIA/BTC | BRIA/ETH | BRIA/ALT BRIA/GBC

BTC-Alpha.com trading pairs BRIA/USD | BRIA/BTC | BRIA/ETH


Exchange offices


Web wallet - Ex.BriaCoin.com
Automatic purchase / sale of Briacoin for Advcash (Bitcoin, Payeer, Exmo).
Web-purse for storing coins. Instant automated input and output Briacoin.
To enroll or send coins, you need 10 network confirmations.


Price and Market Data


Blockchain Stats

CryptoCurrency Market Capitalizations



Media & social networks


Тwitter Skype Chat Telegram BriaStorm .NET