Check Source Health
const url = 'https://example.com/datasets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/source-health/';const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/datasets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/source-health/ \ --header 'Authorization: Bearer <token>'Contact this dataset’s origin and record what came back.
Owner-or-admin: this makes GeoLens issue an outbound request on the
caller’s behalf and writes to the dataset row. Readers get the stored
result from GET /datasets/{id} instead.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Responses
Section titled “ Responses ”Successful Response
Result of one on-demand origin probe.
The values align with VrtSourceHealth.status so clients can use one
legend for VRT members and standalone origins. stale applies only to
VRT members, while unknown represents health that has not been checked;
this endpoint always performs a probe and returns neither value.
object
Healthy — the origin answered and the resource is there. missing — the origin answered authoritatively that it is gone (404/410). inaccessible — GeoLens could not determine either way, which includes 401/403: access was lost, the data may be intact.
Example
{ "source_health": "healthy"}Bad request — invalid payload
Unauthorized — missing or invalid credentials
Forbidden — caller lacks write access
Not found
Conflict — resource state prevents the operation
Validation error
Too many requests — retry after the advertised interval
Headers
Section titled “ Headers ”Seconds until the request may be retried
Internal server error
Service unavailable — the database could not serve the request