/browserleaks/fingerprints/http2

POST /api/browserleaks/fingerprints/http2

Price: 1 credit

Report the HTTP/2 fingerprint a server observes on a connection opened from this API — the Akamai fingerprint, the connection settings, the stream priority and every request header in the order sent

How to use it

This describes the connection this call itself opens; there is no address or filter to aim it at something else, and it says nothing about your own client. The Akamai fingerprint is computed over the connection-level frames and the order of the pseudo-headers alone, so it holds still while the ordinary request headers change — read `headers` when what you need is what the server actually received.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)

Response

• @type string (default: "BrowserleaksHttp2Fingerprint")
• akamai_hash string required
• akamai_text string nullable
• user_agent string nullable
• frame_order array (default: [])
• connection_settings array (default: [])
  • @type string (default: "BrowserleaksHttp2Setting")
  • id integer required
  • name string required
  • value integer nullable
• window_size_increment integer nullable
• pseudo_header_order array (default: [])
• headers array (default: [])
  • @type string (default: "BrowserleaksHttp2Header")
  • name string required
  • value string nullable
• header_flags array (default: [])
• priority_weight integer nullable
• priority_stream_dependency integer nullable
• is_priority_exclusive boolean 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 — The entity was not found, or a precondition failed 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.