Guavy API

Guavy API Documentation

Introduction

Welcome to the Guavy API documentation. This guide provides all the information you need to integrate our services into your applications.

Overview

Whether you’re building trading bots, conducting in-depth market research, or developing financial applications, the Guavy API equips you with the essential insights needed to stay ahead in the fast-paced world of cryptocurrency.

To use the Guavy API, you need a Guavy account. What you can do with the API depends on what level of Guavy plan you have. Once you have an account and are logged in, you can get an API key and begin making calls to the API.

You need an API key to access the Guavy API. If you don't have one yet, you can request API key.

Using the Guavy API

You can also use the Guavy API to handle data in different ways for different purposes. If you are syncing a large amount of data with Guavy, you can use batches to avoid hitting the API request limits.

For building applications that let other users access Guavy data you will need a reseller license.

If you're developing an app for iOS or Android, then a mobile-focused subset of the Guavy API's functionality, can be licensed separately. This allows you to build mobile applications that can access Guavy data without needing a full reseller license.

API structure

The Guavy API generally follows REST conventions, with some deviations.

  • All responses are wrapped in a top-level object.
  • Responses return either `Success` or `Error`.
  • Errors include a message field with details about the error.
  • All responses use the generic JSON content type.
  • Responses use the generic JSON content type.

We use the API Specification to describe each endpoint. The API self-description also contains type information to help you error-check your requests.

The root url for customized API documentation is https://<dc>/api/v3/openapi.json. The <dc> part of the URL corresponds to the custom data center for your account. The base API specification is available at https://api.guavy.com/api/v3/openapi.json.

However, if you are using the Guavy API in our multi-tenanted data center then all API endpoints for your account are available relative to https://api.guavy.com.

Note: You will see the <dc> placeholder or an actual data center subdomain in examples throughout this documentation. Either way, make sure to replace it in your code with the data center subdomain for your account, or your request may generate an error.

Connecting to the API

You can authenticate requests using either your API key or an OAuth access token, depending on your use case. You should use an API key if you're writing code that tightly couples your application data.

The example below demonstrates how to make an authenticated API request using cURL. All Guavy API endpoints require authentication via a Bearer token, which should be included in the Authorization header. This token identifies your account and determines your access level to various endpoints.

To use this example:

  1. Replace YOUR-GUAVY-ACCESS-TOKEN with your personal API key from the Guavy dashboard
  2. The URL includes the specific endpoint path shown in the documentation
  3. All requests use HTTPS for secure data transmission
curl --request GET \

--url 'https://api.guavy.com/api/v3/endpoint' \
--header 'Authorization: Bearer YOUR-GUAVY-ACCESS-TOKEN' \
--header 'Content-Type: application/json'

This request format works across all modern HTTP clients, including Python requests, JavaScript fetch, and other programming language libraries.

API Limits

The Guavy API has a limit of 10 simultaneous connections. You'll receive a 429 error if you reach the limit. At exceptionally high volumes, you may receive an HTTP 429 or 403 without a JSON body.

We recommend that you cache frequently accessed values that do not change often in your application's data store. This will prevent your application from bumping up against the throttling limitations and will likely provide faster access to that data.

Account Limits

Your Guavy account will typically have a licensed limit of at least 100,000 API calls per month. In addition, there is a limit of 100,000 API calls per day. If you reach these limits, you will receive a 429 error.

Connection Timeouts

The Guavy API has a 120-second timeout on API calls. You may see this type of timeout after you've made a network socket connection and are already sending and receiving data.

Response times are dependent on the complexity of your request and the general load across Guavy. Some endpoints in the the Guavy API return values that are large and slow to calculate.

Was this helpful?