Skip to content

Latest commit

 

History

History
45 lines (28 loc) · 1.33 KB

2022-06-20.md

File metadata and controls

45 lines (28 loc) · 1.33 KB

Changes in WEB3 API responses for Jun 20, 2022

Products affected

  • SDK
  • API
  • Admin UI
  • Nodes

Is this a breaking change?

  • yes
  • no

Description of the change

New fields introduced

We currently return the field synced_at that represent when the metadata was updated or failed to be updated We introduced two new fields last_token_uri_sync and last_metadata_sync last_metadata_sync represent when the metadata for an NFT was updated last_token_uri_sync represent when the token_uri for an NFT was updated or failed to be updated

What exactly can break?

In one week from now, we will stop returning synced_at on our API.

How to ensure my app won't break?

Applications that depends on this field should start reading last_token_uri_sync and/or last_metadata_sync. last_metadata_sync is the closed to synced_at since both are updated when the metadata is saved

When will this change go live ?

2022-06-20

Link to Moralis Forum for discussions

https://forum.moralis.io/t/changes-in-web3-api-response-for-metadata-from-jun-20-2022/15084

We have staff monitoring forum 24/7 - while we don't monitor Github as much - so we need everyone to discuss in the forum

The API documentation

https://deep-index.moralis.io/api-docs/

The documentation will be updated to add those 2 new fields