/l2beat/da/projects

POST /api/l2beat/da/projects

Price: 10 credits

Get an L2BEAT data availability layer by slug

How to use it

Get details of a data availability (DA) layer tracked by L2BEAT by its slug (e.g. 'ethereum', 'celestia', 'avail', 'eigenda'). Returns the layer name, kind (public blockchain or custom), economic security, value secured, DA risk assessment, and the DA bridges it offers with their risks and the scaling projects that use them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Data availability layer slug or URL (examples: "ethereum", "celestia", "avail", "eigenda"; minLength: 1)

Response

• @type string (default: "L2beatDaProject")
• id string required
• name string required
• name_second_line string nullable
• alias string nullable
• image string nullable
• kind string nullable
• economic_security number nullable
• challenge_mechanism string nullable
• tvs_latest number nullable
• tvs_seven_days_ago number nullable
• risks array (default: [])
  • @type string (default: "L2beatDaRisk")
  • name string required
  • value string nullable
  • sentiment string nullable
  • description string nullable
• bridges array (default: [])
  • @type string (default: "L2beatDaBridge")
  • name string required
  • alias string nullable
  • tvs_latest number nullable
  • tvs_seven_days_ago number nullable
  • risks array (default: [])
    • @type string (default: "L2beatDaRisk")
    • name string required
    • value string nullable
    • sentiment string nullable
    • description string nullable
  • used_in array (default: [])

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 — Data availability layer 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.