Skip to main content
All CollectionsChangelog
New disable_total flag for faster response times (1st Feb 2023)
New disable_total flag for faster response times (1st Feb 2023)
Jonathan Blackburn avatar
Written by Jonathan Blackburn
Updated over a year ago

In order to vastly improve the response times on a number of endpoints (by up to x10!), we are planning to phase out support for total within our API responses.

A new flag called disable_total exists on the below endpoints which defaults to false. When users set this to true, the total count from the response will return as null, and the endpoint’s response time is greatly improved. We strongly recommend to begin using this flag.

Planned Change

From February 1st 2023 the default value of disable_total will be set to true, and unless you specify disable_total=false, the total value will be returned as null.

Endpoints

Examples on how to set disable_total to true or false:

This request sets disable_total to true

curl --request GET \
--url 'https://deep-index.moralis.io/api/v2/nft/CONTRACT_ADDRESS/transfers?chain=bsc&format=decimal&disable_total=true' \
--header 'accept: application/json' \
--header 'X-API-Key: API_KEY_HERE'

The requests sets disable_total to false

curl --request GET \
--url 'https://deep-index.moralis.io/api/v2/nft/CONTRACT_ADDRESS/transfers?chain=bsc&format=decimal&disable_total=false' \
--header 'accept: application/json' \
--header 'X-API-Key: API_KEY_HERE'

Did this answer your question?