/l2beat/projects/liveness

POST /api/l2beat/projects/liveness

Price: 10 credits

Get L2BEAT liveness intervals (tx data, proof, state updates) and anomalies per scaling project

How to use it

Get the liveness of Ethereum layer-two scaling projects tracked by L2BEAT — how regularly each project posts transaction data, validity proofs, and state updates to Ethereum L1. Returns the average, minimum, and maximum interval in seconds for the chosen window, plus recent anomalies (unusual gaps in submission). Omit 'project' for all projects, or pass a slug for a single project.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string nullable — Project slug to return liveness for one project; omit for all (examples: "arbitrum")
• count integer required — Max number of projects to return (min: 1)
• range string — Aggregation window for the interval averages (default: "30d"; one of: "30d", "90d", "max")

Response

• @type string (default: "L2beatProjectLiveness")
• id string required
• name string required
• alias string nullable
• proof_system string nullable
• category string nullable
• is_synced boolean (default: false)
• tx_data object nullable
  • @type string (default: "L2beatLivenessInterval")
  • average_seconds integer nullable
  • minimum_seconds integer nullable
  • maximum_seconds integer nullable
  • warning string nullable
• proof_submissions object nullable
  • @type string (default: "L2beatLivenessInterval")
  • average_seconds integer nullable
  • minimum_seconds integer nullable
  • maximum_seconds integer nullable
  • warning string nullable
• state_updates object nullable
  • @type string (default: "L2beatLivenessInterval")
  • average_seconds integer nullable
  • minimum_seconds integer nullable
  • maximum_seconds integer nullable
  • warning string nullable
• anomalies array (default: [])
  • @type string (default: "L2beatLivenessAnomaly")
  • start integer required
  • end integer nullable
  • duration_seconds integer nullable
  • status string nullable
  • subtype string nullable
  • avg_interval integer nullable
  • is_approved boolean (default: false)

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 — Project 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.