counterparty-server API

4 stars based on 76 reviews

The best API for getting free cryptocurrency live pricing data, OHLC historical data, volume data, tick data or block explorer data from multiple exchanges and blockchains. We have integrated with over 90 exchanges, coins and have over 22, trading pairs listed. Please make sure you credit us with a link if you use our data on your website or app. Some of the great services using our pricing API: Sign up for API updates here.

Most of the requests that are related to pricing data bitcoin api documentation for valid public bitcoin api documentation for valid the moment and generally available via GET functions. Please do not abuse them, a request every 10 sec should be more than enough.

There is also a streaming api based on socket. At the moment the public rest api and streaming apis are not delayed. You can see the limits here: CryptoCompare uses session cookies to allow access to private data. You can obtain the cookie by logging in. A session key is only valid for 30 days and it has a sliding window period, so each time you use it, it will get extended by 30 days.

Type less than will mean there was an error. This section deals with all the requests for price data, social data and historical data. Most of it is used for dealing with subscription, top list, historical and snapshot data. Get the latest price for a list of one or more currencies. Really fast, ms. Cached each 10 seconds. Get all the current trading info price, vol, open, high, low etc of any list of cryptocurrencies in any other currency that you need.

If the crypto does not trade directly into the toSymbol requested, BTC will be used for conversion. This API also returns Display values for all the bitcoin api documentation for valid. If the opposite pair trades we invert it eg.: Compute the current trading info price, vol, open, high, low etc of the requested pair as a volume weighted average based on the markets requested.

Get day average bitcoin api documentation for valid. The values are based on hourly vwap data and the average can be calculated in different waysIt uses BTC conversion if data is not available because the coin is not trading in the specified currency.

If tryConversion is set to false it will give you the direct data. If no toTS is given it will automatically do the current day. Get the price of any cryptocurrency in any other currency that you need at a given timestamp. The price comes from the daily info - so it would be the price at the end of the day GMT based on the requested TS. Tries to get direct trading pair data, if there is none or it is more than 30 days before the ts requested, it uses BTC conversion. Get data for a currency pair.

It returns general block explorer information, aggregated data and individual data for each exchange available. This api is getting abused and will be moved to a min-api path in the near future. Please try not to use it. Get the general, subs used to connect to the streamer and to figure out what exchanges we have data for and what are the exact coin pairs of the coin and the aggregated prices for all pairs available.

AggregatedPrices Array[] yes Snapshot data about the coin volume, price, open, high, low close etc. If called with the id of a cryptopian you just get data from our website that is available to the public. UrlstringnoThe relative path without https: Get open, high, low, close, bitcoin api documentation for valid and volumeto from the each minute historical data.

This data is only stored for 7 days, if you need more,use the hourly or daily path. It uses BTC conversion if data is not available because the coin is not trading in the specified currency.

The values are based on Used to get all the mining equipment available on the website. It returns an array of mining equipment objects. Get top pairs by volume for a currency always uses our aggregated data. The number of pairs you get is the minimum of the limit you set default 5 and the total bitcoin api documentation for valid of pairs available.

Get real-time market data updates by connecting to our web socket ' wss: We are using socket. For more example code click here. Subscribe to market data by emitting 'SubAdd' including a list of items you want to get updates on. After the first response, only updates will be sent. The MaskInt parameter maps the response to the properties. Use our utility functions to map the response, you can find the code here. Introduction The best API for getting free bitcoin api documentation for valid live pricing data, OHLC historical data, volume data, tick data or block explorer data from multiple exchanges and blockchains.

Requests Most of the requests that are related to pricing data are public at the moment and generally available via GET functions. Sessions A session key is only valid for 30 days and it has bitcoin api documentation for valid sliding window period, so each time you use it, it will get extended by 30 days.

Note that the responses to all requests, both public and private, are sent as the response body. Data This section deals with all the requests for price data, social data and historical data.

Data Object yes Empty if there is no data to return or there is an error Data [Symbol]: Id int yes The internal id, this is used in other calls Data [Symbol]: ImageUrl string yes The logo image of the coin Data [Symbol]: Bitcoin api documentation for valid string yes The name Data [Symbol]: Bitcoin api documentation for valid string yes A combination of the name and the symbol Data [Symbol]: Algorithm string yes The algorithm of the cryptocurrency Data [Symbol]: ProofType string yes The proof type of the cryptocurrency Data [Symbol]: Invalid Market ", "Data": For PST you would pass -8 for example.

URL Parameters Parameter Type Mandatory Description fsym string yes The symbol of the currency you want to get that for tsym string yes The symbol of the currency that data will be in. Return data Parameter Type Always returned Description Response string yes The type of the response Success or Error Message string yes The message for the response Type integer yes Integer representing the type of response.

Data object yes Empty if there is no data to return or there is an error Data: Algorithm string yes The algorithm of the from currency Data: BlockNumber integer yes The current block number delayed by 1 hour max Data: BlockReward integer yes The current block reward delayed by 1 hour max Data: AggregatedData object yes See success request example Data: What are you trying to do? AggregatedPrices Array[] yes Snapshot data about the coin volume, price, bitcoin api documentation for valid, high, low close etc Parameter Type Always returned Description Response string yes The type of the response Success or Error Message string yes The message for the response BaseImageUrl string yes The base url for all the images from the ImageUrl field BaseLinkUrl string yes The base url for all the links from the Url field Type int yes Integer representing the type of response.

General object yes The general data available for this coin Data: H1Text string yes The title used on our website a combination of the coin name and the symbol Data: ImageUrl string yes The relative path to the logo of the coin, prefix this value with the BaseImageUrl to get the absolute path Data: DangerTop string yes The text displayed in red on the website at the top, generally a big issue with the coin Data: WarningTop string yes The text displayed in yellow on the website at the top, generally an issue with the coin Data: InfoTop string yes The text displayed in green on the website at the top, generally an announcement or extra info that is important Data: Symbol string yes The symbol of the coin Data: Url string yes The relative path to the coin, prefix this value with the BaseLinkUrl to get the absolute path Data: Name string yes The name of bitcoin api documentation for valid coin Data: Description string yes The description of the coin, this is returned as html Data: Features string yes The features of the coin, this is returned as html Data: Technology string yes The technology of the coin, this is returned as html Data: TotalCoinSupply int yes The maximum number of coins Data: StartDate string yes The day the first block was mined, so the day the coin actually came into existance Data: Twitter string yes The twitter address of the coin Data: TwitterWidgetId string yes The cryptocompare twitter widget id for this coin Data: Website string yes Bitcoin api documentation for valid coin official website Data: DifficultyAdjustment string yes The difficulty adjustment Data: BlockRewardReduction string yes The value by which the block reward is reduced when there is a block reward reduction Data: BlockNumber int yes The current block number delayed by 1 hour max Data: BlockTime int bitcoin api documentation for valid The estimated time it takes to mine a block Data: TotalCoinsMined int yes The current total coins mined delayed by 1 hour max Data:

Democratized trust the rise of blockchain capital

  • Computerphile bitcoin price

    Setx command litecoin price

  • Primecoin threads

    Bitcoinget huijaus puhelin

Related videos for how hexabot scammed millions of dollars worth of bitcoin and are getting away wit

  • Trade deficits by countries

    Bitcoin robinet bot imacrosbitcoin qt pour ubuntu 16.04

  • Monero calderon textiles

    Noncanonical signature blockchain news

  • Tenx paya bitcoin visa card that lets you spend crypto anywhere

    Bitcoin investment calculator future price

Bitcoin hack program for battlenet

50 comments 1 bitcoin price in indian rupee

Bank of england bitcoin minerals

The platform provides partners with functionality such as. Civic Hosted option for partners - this provides a flow similar to the traditional oAuth2 authorization code flow, with Civic performing the role of the Authorization server.

The general flow is explained using the example of user signup. The eventhandler calls a method in the CivicJS library to initiate signup. A modal is displayed which contains an iframe to house the QR code. A request is made to the Civic server to generate a QR code for your scope request. The server checks that the domain for the parent document of the iframe corresponds to the domain white list set in the partner account before serving the code. The user scans the QR code using the Civic mobile app and is prompted to authorize or deny the scope request.

The prompt highlights the data that is being requested and the requesting party. Upon granting the request, the data is sent to the Civic server. This process proves that the user data was attested to by Civic and that the user is currently in control of the private keys relevant to the data.

Verify on the blockchain. The Civic server then verifies that the attestations are still valid on the blockchain and have not been revoked. The data is encrypted and cached on the Civic server.

Once this data is cached, a polling request from the iframe will receive a response containing an authorization code wrapped in a JWT token. The CivicJS browser-side library passes the token to the parent document. Your site is then responsible for passing the JWT token to your server. The SIP server first validates the JWT token, ensuring it was issued by Civic, is being used by the correct application id, and that the expiry time on the token has not lapsed.

The enclosed AC is then verified and the encrypted cached data returned. Your server receives the encrypted data where it is decrypted using your application secret key. The result will contain a userId and any data requested such as email, mobile number etc. Sign up for a developer account on the Civic Integration Portal and create a test application.

From here, you will be able to generate the keys necessary for encryption used in the steps below. Basic requests necessary for simple account creation and 2FA are available to all partners who have signed up on the integration portal.

Learn more and request access here. This exposes a single global object, civic. Create an instance of civic. This identifies your site to Civic servers.

You can find your application ID in the Application details section of the integration portal. Provide a suitable event handler to initiate the Civic scope request.

The event handler calls civic. Provide an event handler to listen for data events. The JWT token ensures the integrity of the response, the identity of the sender, the intended receipient and valid lifespan of the response. The authorization code will be passed to the handler wrapped in a JWT token following authorization by the user.

Use the Civic SIP server sdk relevant to your server side environment to complete the server integration of your signup, login or general scope request flow. Your private keys and secret should only be used on the server and never exposed on the client side. They must be stored securely.

Call exchangeCode with the JWT token you received from the browser session to exchange for the requested user data. The continued validity of the header token expiry is also verified.

The message digest is then validated to ensure the body of the request has not been tampered with. User data is then returned to your server encrypted using AES and your secret. The receiver validates this token to ensure it has been sent by Civic.

Upon receiving a response at your server, the Civic sdk decrypts the data using your application secret and returns the user data. The userId can be associated with your user account system for user identification in future logins. This option is not currently available for general use. If this functionality is required, please contact partners civic. Scope Requests detail specific sets of verified data you wished returned from the user.

The two currently available scope requests are detailed below. See Event Handlers for documentation on how to implement these requests. It is most commonly used for secure login and signup solutions when no additional identity verification is required. Note that attempting this request without prior approval will return an unauthorized error.

To ensure the best possible results, the Civic browser experience is designed for modern desktop browsers that automatically update. Browsers without reliable automatic update systems are supported as current version Once the user approves the scope request on the Civic App, they will be redirected back to the browser with a new tab being opened on your integrated web page.

We append a query parameter called uuid to the parent URL so that we can identify the fact that this page is loading after returning from the Civic App. If a uuid query parameter is detected in the parent URL, the Civic library will load the modal up automatically and begin polling for the token response.

Once the token is received it will behave as normal and use the code setup in the event listener for auth-code-received. We suggest testing the mobile browser flow in your integration and ensure any possible special handling in this adapted process. This limits the contagion in the event that a private key is compromised, and only that clientID and key pair need to be regenerated. To ensure data privacy, unencrypted HTTP is not supported.

API requests without authentication will also fail. In general, a response code of 2xx indicates the operation was successful. Other error codes indicate either a client error 4xx or a server error 5xx. The platform provides partners with functionality such as secure 2FA user login secure private 2FA user login onboarding of verified users with customized flows Integration There are two integration flows: This option minimises server side development required by the partner. This option requires more server side development.

Civic Hosted option The general flow is explained using the example of user signup. For subsequent logins the userId can be used to associate the user with your accounts system. Getting Started Follow the steps below to integrate using the Civic Hosted option.

Include Include the civic. Instantiate instance of civic. Initialize Create an instance of civic. Event Handlers Provide a suitable event handler to initiate the Civic scope request. The auth-code-received event contains the following fields: Field Required Description event Yes event name type Yes flow type for the response e. Initialize instance passing your appId and secret. Exchange authorization code for user data. Exchange Authorization Code Call exchangeCode with the JWT token you received from the browser session to exchange for the requested user data.

This is used to authenticate your request. This header consists of: It also introduces a time dependency to the request. This is signed using your private key.

This ensures the integrity of the request body on the Civic server. The SIP server verifies that the caller is the correct recipient of the token. User Data Each item of user data returned has the following fields: Field Example Description label contact. Direct Option This option is not currently available for general use. Scope Requests Scope Requests detail specific sets of verified data you wished returned from the user. Label Example Value Description contact.

Label Example Value Description documents. IAL1 Verification standard used to check the document. This field should be ignored pending future functionality.

Browser Support To ensure the best possible results, the Civic browser experience is designed for modern desktop browsers that automatically update. The Civic API uses the following error codes: Civic SIP service challenges the user during scope request approval to ensure the user is in control of the private key originally used in the issuance of the data attestation. Verification standard used to check the document.