/l2beat/projects/activity

POST /api/l2beat/projects/activity

Price: 1 credit

Get the activity (UOPS/TPS) history and current stats for an L2BEAT scaling project

How to use it

Get the throughput activity of a single Ethereum layer-two scaling project tracked by L2BEAT — its user operations per second (UOPS) and transactions per second (TPS) over time. Returns current stats (past-day total, daily average, change, and all-time max with its timestamp) for both UOPS and TPS, plus a daily time series of operation and transaction counts ordered oldest-first.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Project slug or project URL (examples: "arbitrum", "base", "https://l2beat.com/scaling/projects/optimism"; minLength: 1)
• range string — Time window for the activity history (default: "30d"; one of: "30d", "90d", "180d", "1y", "max")
• count integer nullable — Return only the most recent N chart points (min: 1)

Response

• @type string (default: "L2beatProjectActivity")
• id string required
• uops object nullable
  • @type string (default: "L2beatActivityStat")
  • past_day_sum number nullable
  • avg_per_second number nullable
  • change number nullable
  • max_value number nullable
  • max_at integer nullable
• tps object nullable
  • @type string (default: "L2beatActivityStat")
  • past_day_sum number nullable
  • avg_per_second number nullable
  • change number nullable
  • max_value number nullable
  • max_at integer nullable
• chart array (default: [])
  • @type string (default: "L2beatActivityPoint")
  • timestamp integer required
  • count number nullable
  • uops_count number nullable
• synced_until integer 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 — 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.