Skip to content

Commit

Permalink
Merge pull request #63 from blockfrost/v0.1.16
Browse files Browse the repository at this point in the history
release: 0.1.15 -> 0.1.16
  • Loading branch information
mmahut authored May 25, 2021
2 parents ab9a78d + 5b38d29 commit 64334c5
Show file tree
Hide file tree
Showing 3 changed files with 21 additions and 9 deletions.
15 changes: 11 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,27 +5,35 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project will adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html) once it reaches maturity in v1.

## [] - Unreleased
## [0.1.16] - 2021-05-25

### Added

- `/accounts/{stake_address}/addresses/assets` endpoint to list all assets on addresses related to a given stake_address (account)
- `/epochs/latest/parameters` and `/blocks/latest/txs` endpoints to list the current information about latest epoch and block

### Changed

- implementation (increase allowed burst) of rate limiting and clarified documentation

### Fixed

- `onchain_metadata` in `/assets/{asset}/total` endpoint that could have been missing in some special cases
- `onchain_metadata` in `/assets/:asset` endpoint to return null on malformed data which do not follow https://github.com/cardano-foundation/CIPs/pull/85/files


## [0.1.15] - 2021-05-19

### Fixed

- `registration` and `retirement` arrays in `/pools/{pool_id}/` endpoint doesn't need to be `Nullable`


## [0.1.14] - 2021-05-19

### Fixed

- `amount` in `/accounts/{stake_address}/rewards`, `/accounts/{stake_address}/delegations` and `/accounts/{stake_address}/history` endpoints doesn't need to be `Nullable`


## [0.1.13] - 2021-05-06

### Fixed
Expand All @@ -43,7 +51,6 @@ and this project will adhere to [Semantic Versioning](https://semver.org/spec/v2
- all occurences of `epoch` to `active_epoch` in `/accounts/{stake_address}/history` endpoint
- required properties of multiple endpoints and error messages


## [0.1.11] - 2021-04-23

### Added
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@blockfrost/openapi",
"version": "0.1.15",
"version": "0.1.16",
"description": "OpenAPI specifications for blockfrost.io",
"repository": "git@github.com:blockfrost/openapi.git",
"author": "admin@blockfrost.io",
Expand Down
13 changes: 9 additions & 4 deletions swagger.yaml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
openapi: 3.0.0
info:
version: "0.1.15"
version: "0.1.16"
title: Blockfrost.io ~ API Documentation
x-logo:
url: https://staging.blockfrost.io/images/logo.svg
Expand Down Expand Up @@ -74,9 +74,14 @@ info:
```
## Limits
There are two types of limits we are enforcing. The first depends on your plan and is the number of request we allow per day. We defined
the day from midnight to midnight of UTC time. The second is rate limiting, where we limit an end user to 10 requests per second after a period
of 5 second burst. We believe this should be sufficient for most of the use cases. If it is not and you have a specific use case, please get in touch with us, and
There are two types of limits we are enforcing:
The first depends on your plan and is the number of request we allow per day. We defined the day from midnight to midnight of UTC time.
The second is rate limiting. We limit an end user, distinguished by IP address, to 10 requests per second. On top of that, we allow
each user to send burst of 500 requests, which cools off at rate of 10 requests per second. In essence, a user is allowed to make another
whole burst after (currently) 500/10 = 50 seconds. E.g. if a user attemtps to make a call 3 seconds after whole burst, 30 requests will be processed.
We believe this should be sufficient for most of the use cases. If it is not and you have a specific use case, please get in touch with us, and
we will make sure to take it into account as much as we can.
servers:
Expand Down

0 comments on commit 64334c5

Please sign in to comment.