/messari/assets/events

POST /api/messari/assets/events

Price: 5 credits

Get notable events and key developments for a crypto asset

How to use it

Get the stream of notable events and key developments tagged to a crypto asset, by its slug or ticker symbol. Each item has the title, summary, source link, preview image, publication date, content and source type, the source (name, logo), and the tagged assets. Use it for an asset's due-diligence event timeline.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• asset string required — Asset slug or ticker symbol (examples: "bitcoin", "ethereum", "BTC"; minLength: 1)
• count integer required — Max number of events to return (min: 1)

Response

• @type string (default: "MessariFeedItem")
• id string required
• description string nullable
• url string nullable
• image string nullable
• published_at string nullable
• content_type string nullable
• source_type string nullable
• is_video boolean nullable
• is_price_analysis boolean nullable
• source object nullable
  • @type string (default: "MessariFeedSource")
  • id string nullable
  • name string nullable
  • image string nullable
• assets array (default: [])
  • @type string (default: "MessariAssetRef")
  • id string required
  • name string nullable
  • slug string nullable
  • symbol string nullable
  • image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Asset not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.