## Learn from BitShares Documentation website - How it works.


![bts-collection3.png](https://steemitimages.com/DQmP8SvBn4WiV6wH3MgxBkrPFLk9crQbCeadnPh4PYQs1y1/bts-collection3.png)

---

<br/>

I created a simply listed BitShares APIs Method Names.  There are many Method names. You might find some useful method names you are looking for.    I added the links to the information pages. Please go and read the details.  Also, I added BitSharea API related information that would be helpful to understand how it works.


-----

<br/>


# BitShares -  APIs

## [API Guide](http://docs.bitshares.eu/api/index.html)


### APIs categories
* **Blockchain API** -- It is used to query blockchain data (account, assets, trading history, etc.) Besides data stores in the blockchain itself (blocks, transactions, etc. ..), higher level objects (such as accounts, balances, etc. …) can be retrieved through the full node’s database.
* **Wallet API** -- It has your private keys loaded and is required when interacting with the blockchain with new transactions.


### API Calls
* All API calls are formatted in JSON and return JSON only. 
* The set of available calls depends on whether you connected to a full node (witness_node) or the wallet (CLI-wallet). Both support RPC-JSON.   
* The full node also supports the websocket (statefull) protocol with notifications.
* The full node offers a set of API(s), of which only the database calls are available via RPC. Calls that are restricted by default (i.e. `network_node_api`) or have been restricted by configuration are not accessible via RPC because a statefull protocol (websocket) is required for login.
* The [CLI- wallet](http://docs.bitshares.eu/integration/apps/cliwallet.html) can open a RPC port so that you can interface your application with it. You have the choices of 
     - websocket RPC via the `-r `parameter, and 
     - HTTP RPC via the `-H` parameter.

### Call methods
* [Remote Procedure Calls](http://docs.bitshares.eu/api/rpc.html) -- In Graphene, RPC calls are **state-less** and accessible via regular JSON formated RPC-HTTP-calls.
* [Websocket Calls](http://docs.bitshares.eu/api/websocket.html) -- In Graphene, Websocket calls are **stateful** and accessible via regular JSON formated websocket connection. 


### API Access Restrictions
Access to some APIs may be **restricted** and requires login with username and passphrase.  [More details...](http://docs.bitshares.eu/api/access.html)

### Network and Wallet Configuration  - [Network Setups](http://docs.bitshares.eu/integration/network-setup.html)
* [General Network and Wallet Configuration](http://docs.bitshares.eu/integration/tutorials/general-network-setup.html)
* [Secure Network and Wallet Configuration](http://docs.bitshares.eu/integration/tutorials/secure-network-setup.html)


-----

----

<br /> 

## [Blockchain APIs](http://docs.bitshares.eu/api/blockchain-api.html)

* [Database API](http://docs.bitshares.eu/api/database.html)
* [Account History API](http://docs.bitshares.eu/api/history.html)
* [Crypto API](http://docs.bitshares.eu/api/crypto.html)
* [Network Broadcast API](http://docs.bitshares.eu/api/network_broadcast.html)
* [Network Nodes API](http://docs.bitshares.eu/api/network_node.html)




![Blockchain-APIs-Names1_Page_1.png](https://steemitimages.com/DQmPRK7XmJm6tRmY6MbnuGXUaeayuqdfQEtjJgCPKnmFnoR/Blockchain-APIs-Names1_Page_1.png)

![Blockchain-APIs-Names1_Page_2.png](https://steemitimages.com/DQmRn1DcCNnLfS4vohxRDBiVScVXEr4o76AigZ3Ly7dAnef/Blockchain-APIs-Names1_Page_2.png)


![Blockchain-APIs-Names2.png](https://steemitimages.com/DQmPp1TSSNH6hyr3YPTZMs7ZQ67jGyzYZWpYEsL1yL2m36w/Blockchain-APIs-Names2.png)

-----

<br />

## [Wallet API Calls](http://docs.bitshares.eu/api/wallet-api.html)

In order to interact the wallet, you need to run the [CLI Wallet](http://docs.bitshares.eu/integration/apps/cliwallet.html). The CLI Wallet has the private keys and signing capabilities.  It *requires* a running full node (*witness node*)  (not necessarily locally) and connects to it. 



![WalletCalls-APIs-Names_Page_1.png](https://steemitimages.com/DQmdC9hZMWDnLTPzHtm9SY697zie3qZg9XnNBFPVgcZMRYP/WalletCalls-APIs-Names_Page_1.png)


![WalletCalls-APIs-Names_Page_2.png](https://steemitimages.com/DQmcprHKQSdtxDseGpkWEoEhreHggyKUH6Wex7GT9qwBh2p/WalletCalls-APIs-Names_Page_2.png)


<br />

## Blockchain Objects and their Identifiers

In the protocol space, there are raw objects such as, accounts, assets, committee members as well as orders, proposals and balances. The implementation space is used to gain access to higher abstraction layers for instance content of the current database state (these include, current global blockchain properties, dynamic asset data, transaction histories as well as account statistics and budget records).

### [Objects and IDs](http://docs.bitshares.eu/development/blockchain/objects.html)


<br />

----

Hope you could find some useful information for your BitShares project!

(do no vote. if you like it, please just share.)    Thank you.