Authentication
JWT bearer tokens, API keys (header and query forms), and OAuth/OIDC. Start here if your client is making its first request.
The GeoLens REST API exposes the full catalog, search, map, and standards endpoints. This reference is auto-generated from a committed OpenAPI snapshot of a running GeoLens instance. Every endpoint, parameter, and response schema is derived directly from the FastAPI application.
Authentication
JWT bearer tokens, API keys (header and query forms), and OAuth/OIDC. Start here if your client is making its first request.
OGC & Standards Endpoints
OGC API Common, Records, Features, STAC 1.0, and tile endpoints with QGIS, GDAL, and pystac-client examples.
Endpoints by Tag
Browse the full reference grouped by FastAPI tag. Each operation includes parameters, request body, and response schemas. The sidebar lists all 27 tag groups, and the index at the bottom of this page names every operation so you can search for one by method and path.
QGIS
Add a GeoLens dataset to QGIS over OGC API Features, push CQL2 filters down to the server, and paste vector-tile URLs directly.
ArcGIS Pro
Add GeoLens vector datasets to ArcGIS Pro over OGC API Features, private ones with an API key as the saved login, and rasters as XYZ tile layers or STAC items.
Client SDKs
Prefer typed code over raw HTTP? The Python and TypeScript SDKs are auto-generated from this same contract.
Ingest & jobs
Writing to the catalog: upload, preview, commit, then poll the job. Real endpoint paths and the 202-then-poll contract.
Errors & rate limits
The RFC 7807 body every failure returns, and what a 429 looks like when you have asked for too much too fast.
Runnable examples
Single-file pages and scripts that run against the public demo: MapLibre, Leaflet, OpenLayers, ArcGIS JS, QGIS, STAC, DuckDB, GeoPandas, the SDKs, the CLI, and MCP. CI replays them against the demo on every change.
Reading the catalog is one half of the API; the ingest lane is the other. The
write endpoints under /ingest require a credential carrying the upload
capability; GET /ingest/upload/config needs only an authenticated user, and
GET /jobs/{job_id} is limited to the job’s owner (or an admin). A read_only
API key authenticates GET, HEAD, and OPTIONS only, so it cannot drive this
sequence. Use a full key, a JWT, or from 1.27.0 a publish key, which can
upload, preview, commit and poll but can’t make a dataset public (see
Authentication). Paths below are relative to the API base,
http://localhost:8080/api on a default install.
1. Ask what the instance accepts. GET /ingest/upload/config returns
allowed_extensions, max_file_size_bytes, presigned_uploads, and
presigned_threshold_bytes. The extension list is an admin setting
(upload_allowed_extensions, Admin -> Storage); the shipped default is
.zip, .gpkg, .geojson, .json, .csv, .tif, .tiff, .xlsx, .xls, .parquet, .fgb, .kml, .kmz, .3tz, .laz.
Standalone .vrt uploads are rejected at every upload door — a VRT is assembled
from raster datasets already in the catalog, via POST /ingest/vrt/create. Create
and add-source answer 422 when the VRT would reach people who cannot read one
of its members, which the VRT’s owner does not also own.
2. Send the bytes. POST /ingest/upload as multipart/form-data with a
file part returns 201 and a job_id. Nothing is queued yet.
Add a kind field for the 3D types: tiles3d for a 3D Tiles .zip or .3tz
archive, pointcloud for a COPC .laz. Without it a .3tz or .laz is
refused, and a tileset .zip is read as ordinary geospatial data. Omit kind
for every other file. See 3D Tiles and point clouds.
On an instance backed by S3 storage (presigned_uploads: true in the config
response), the payload can skip the API entirely: POST /ingest/upload/presigned
with {"filename", "file_size", "content_type"} (plus kind for the 3D types) returns 201 with a job_id
and one or more presigned urls. PUT the bytes yourself — a single URL below
presigned_threshold_bytes, part_size-sized parts above it — then
POST /ingest/upload/presigned/{job_id}/complete, passing
{"parts": [{"etag", "part_number"}]} for the multipart case.
3. Preview. POST /ingest/preview/{job_id}, callable only while the job is
pending. Vector sources come back with columns, CRS, geometry type, feature
count, sample rows, and the layer list; rasters with band count, CRS,
resolution, and COG compliance. Add ?layer_name= to inspect one layer of a
multi-layer source.
4. Commit. POST /ingest/commit/{job_id} with a body of at least
{"title": "..."} returns 202 Accepted and queues the ingest task. For a
multi-layer source, POST /ingest/commit-fan-out/{job_id} turns each requested
layer into its own dataset — run the preview first, because the endpoint
validates every layer_name against the layer list the preview recorded.
5. Poll the job. GET /jobs/{job_id} reports status — one of pending,
running, complete, failed, cancelled, fanned_out — plus progress
(0 to 1), current_step, error_message, and dataset_id once the dataset
exists. cancelled means the job was cancelled with
POST /jobs/{job_id}/cancel, or it was an upload nobody committed or completed,
which the stale-job sweep settles as cancelled with the reason
upload_abandoned. failed means work was attempted and broke.
Already have the data in PostGIS? GET /ingest/discover/ lists tables that
aren’t in the catalog yet, and POST /ingest/register/ catalogs one in place
without moving any bytes. These two are admin-only: they need the
manage_settings permission rather than upload, so an editor gets 403.
Request and response schemas for all of these live in the generated reference: the ingest operations under the Datasets tag, the job endpoints under the Admin tag.
These forms still work. Each stays until at least 2027-02-05, then may be removed in a later release.
| Deprecated | Use instead |
|---|---|
The offset query parameter on GET /audit/datasets/{id}/column-ddl and GET /datasets/{id}/vrt/generations/, an alias of skip | skip |
The externalId query parameter on GET /collections/datasets/items | externalIds |
An API key in the ?api_key= query parameter; see API keys | The X-Api-Key header, or the password of an HTTP Basic login |
The PUBLIC_BASE_URL setting; see Configuration | PUBLIC_API_URL |
POST /query/ runs one SELECT through a read-only sandbox and returns
{columns, rows, row_count, truncated}. It is a POST that is semantically a
read, so a read_only API key is accepted; the caller must be authenticated
either way and hold the use_ai_chat permission, which editors and admins have
by default and viewers do not.
restrict_tables is required and non-empty. It names every data.* table the
statement may touch, without the data. prefix, and it can only narrow what
your credential already sees — it never widens it. A dataset’s table name is the
table_name field of GET /datasets/{dataset_id}.
curl -sS -X POST "$GEOLENS_URL/api/query/" \ -H "X-Api-Key: $GEOLENS_API_KEY" \ -H 'Content-Type: application/json' \ -d '{"sql": "SELECT name, pop_est FROM data.world_countries_natural_earth_1_50m LIMIT 5", "restrict_tables": ["world_countries_natural_earth_1_50m"], "row_limit": 5}'The sandbox refuses anything that is not a single SELECT, along with writes,
other schemas, and functions outside its allowlist; a refusal for a function
names it. Each query runs under a
5-second statement timeout and a row_limit of at most 1000 (default 100), and
one caller runs one query at a time. Rejections come back as 422 (invalid or
too expensive), 404 (a table you named that you cannot see — denial and
non-existence deliberately share one answer), or 429 (your previous query is
still running, or the instance is at its concurrency ceiling). The full budget —
the self-join cap, the blocked output-amplifying functions, the response-size
ceiling — is written out under
Using query, because the MCP server’s query
tool is the same endpoint.
Errors raised by the application answer as RFC 7807 problem details:
Content-Type: application/problem+json, with a four-field body.
{ "type": "about:blank", "title": "Not Found", "status": 404, "detail": "Dataset not found"}All four fields are always present. type is about:blank on every error —
GeoLens does not mint per-error type URIs, so branch on status, never on
type. title is a short label, normally the reason phrase for that status
(Validation Error on a 422). detail is normally a
string; a validation failure names the offending parameter
(query.limit: Input should be a valid integer), and a handful of endpoints put
an object or an array there instead, so parse it defensively rather than
assuming a string. A refused workflow transition, for one, answers 422 with an
object carrying code, message, current_stage, requested_stage and
allowed_stages.
The standards surface — /, /conformance, /collections*, /stac* — uses
the same envelope with one difference: OGC API Common requires malformed
parameters to be reported as 400, where the native routes report 422. Same
body, different number. A client that treats 422 as “I sent something bad”
should treat 400 the same way.
One failure skips the envelope. A request that matches no route at all, or uses
a method a matched path does not answer, is rejected by the framework before any
handler and comes back as plain application/json — {"detail": "Not Found"}
with a 404, {"detail": "Method Not Allowed"} with a 405.
Responses carry an X-Request-ID. A 500 body is deliberately generic — the
exception, the path, and the caller are written to the server log against that
id — so quote it when reporting one. It is not on the CORS expose list, so a
cross-origin browser client cannot read it; same-origin and server-side callers
can.
Limits are keyed on the client IP, except the SQL sandbox, which additionally
buckets per user, and the failed sign-in limit, which counts per account (with
a separate budget for each browser that has signed in to it before). The global,
semantic search and basemap limits are admin settings on the Network tab,
and the login limit is on the Authentication tab (LOGIN_RATE_LIMIT), so an
instance you do not run may be tuned differently. The SQL sandbox, filtered
feature page, token refresh, download token and admin limits and the
per-account failed sign-in limit are fixed. The values below are the shipped defaults.
| Limit | Default | Applies to |
|---|---|---|
| Global | 60/second | every route except the tile routes and the AI routes below |
| Login | 5/minute | POST /auth/login |
| Failed sign-ins per account | 10/hour | POST /auth/login, for a client the account does not know; a browser that has signed in before has its own budget, and API keys are not affected (see Sign-in throttling) |
| Semantic search | 30/minute | /search/datasets/, /search/facets/, /datasets/{id}/related/ |
| Basemap list | 120/minute | GET /settings/basemaps/ |
| SQL sandbox | 30/minute per user, 60/minute per IP | POST /query/ |
| Filtered feature pages | 10/second | GET /collections/{id}/items with a filter= parameter; unfiltered paging is exempt |
| Token refresh | 30/minute per session | POST /auth/refresh/ |
| Download tokens | 60/minute | POST /auth/download-token/{dataset_id} |
| Admin and key management | 30/minute | many admin and settings writes, and minting dataset keys |
The per-route limits apply on top of the global one, so a request to those routes counts against both. Tile routes are exempt from the global limit, and the AI generation and metadata routes have fixed limits of their own instead (10/minute and 20/minute).
These figures are per instance only where the instance is configured for it.
From 1.19.0 the counting is shared across API workers when REDIS_URL is set,
and per worker when it is not, so on a multi-worker instance without the store
each limit above except the failed sign-in limit is enforced once per worker
rather than once for the instance. The sign-in limit is counted in the database,
so it is shared across workers either way.
The same holds for as long as a configured store is unreachable. Read the table
as the operator’s intent rather than as something to calibrate a client
against, and back off on 429 either way.
Over any limit, global or per-route, you get a 429 in the usual problem+json
envelope, with a Retry-After header giving the limiter’s window in seconds:
HTTP/1.1 429 Too Many RequestsRetry-After: 60Content-Type: application/problem+jsonThe global window is one second, so Retry-After is 1 there and a caller that
hits it should pause about a second and resume. Read Retry-After and fall back
to your own delay when it is missing, with jitter so a fleet of clients does not
resynchronise.
Retry-After is named in Access-Control-Expose-Headers on both CORS policies
— the credentialed one and the credential-free one the anonymous public routes
get — so a browser client reads the retry window cross-origin instead of seeing
an opaque failure.
Two limits live outside the API, in the bundled frontend nginx, which is the
application edge in the standard deployment. It throttles raster tile requests
at /raster-tiles/... and /api/tiles/raster-proxy/... to 600/minute per IP
with a burst of 200, for anonymous and credentialed callers alike, and answers
429 with Retry-After: 2 and Access-Control-Allow-Origin: *. Behind that,
each API process admits only so many raster renders at once (sized by
TILE_POOL_MAX_SIZE), and a full budget also answers 429 with Retry-After.
It also limits vector and cluster tile
requests (/api/tiles/data.* and /api/tiles/clusters/data.*) to 5400/minute
with a burst of 720, and answers 429 with Retry-After: 2 and a CORS header.
That limit applies only when TRUSTED_PROXY_CIDRS is set. With it empty, the
default, the frontend’s entrypoint leaves the limit key blank, and nginx does not
count requests with an empty key.
Every operation in the snapshot, grouped and ordered the way the sidebar is — tag groups A to Z — with the operations inside each group sorted by path. Search finds this page by method, path, or summary; the generated operation pages themselves are not indexed.
GET /admin/ai-status/ — Get the AI feature statusPATCH /admin/ai-status/ — Turn AI features on or offGET /admin/api-keys/ — List all API keysPOST /admin/api-keys/ — Create an API key for a userDELETE /admin/api-keys/{key_id} — Revoke any API keyGET /admin/audit-logs/ — List audit log entriesGET /admin/audit-logs/export/{format} — Download audit recordsPOST /admin/backfill-embeddings/ — Queue an embedding backfillGET /admin/embedding-stats/ — Get embedding coverageGET /admin/groups/ — List sharing groupsPOST /admin/groups/ — Create a sharing groupDELETE /admin/groups/{group_id} — Delete a sharing groupGET /admin/groups/{group_id} — Get a sharing groupPATCH /admin/groups/{group_id} — Rename a sharing groupGET /admin/groups/{group_id}/members/ — List sharing group membersPOST /admin/groups/{group_id}/members/ — Add users to a sharing groupDELETE /admin/groups/{group_id}/members/{user_id} — Remove a user from a sharing groupGET /admin/infrastructure/ — Get infrastructure statusGET /admin/jobs/ — List all ingest jobsGET /admin/share-tokens/ — List share tokensDELETE /admin/share-tokens/{token_id} — Revoke a share tokenGET /admin/stats/ — Get catalog statisticsGET /admin/users/ — List usersPOST /admin/users/ — Create a userDELETE /admin/users/{user_id} — Delete a userGET /admin/users/{user_id} — Get a userPATCH /admin/users/{user_id} — Update a userPOST /admin/users/{user_id}/approve/ — Approve a pending userPOST /admin/users/{user_id}/deactivate/ — Deactivate a userPOST /admin/users/{user_id}/reject/ — Reject a pending userPOST /admin/users/{user_id}/reset-password/ — Reset a user's passwordGET /admin/users/export.csv — Export registered users as CSVGET /admin/users/names/ — List usernamesGET /capabilities/ — Get server capabilitiesGET /jobs/{job_id} — Get an ingest job's statusPOST /jobs/{job_id}/cancel — Cancel an ingest jobPOST /jobs/{job_id}/retry — Retry a failed ingest jobGET /jobs/by-dataset/{dataset_id} — Get a dataset's latest ingest jobPOST /jobs/cleanup/stale/ — Fail stale ingest jobsPOST /jobs/status/ — Get the status of several ingest jobsPUT /settings/ — Update settingsGET /settings/all/ — Get all settingsGET /settings/api-key-status/ — Get LLM provider key statusGET /settings/basemaps/ — Get basemapsGET /settings/branding/ — Get brandingGET /settings/config-mode/ — Get the configuration modePOST /settings/detect-embedding-dims/ — Detect embedding dimensionsGET /settings/edition/ — Get runtime capabilitiesGET /settings/enabled-plugins/ — Get enabled pluginsGET /settings/enterprise-tabs/ — List restricted settings tabsGET /settings/feature-flags/ — Get feature flagsGET /settings/map-defaults/ — Get map defaultsGET /settings/notifications/status/ — Get notification channel statusPOST /settings/notifications/test/ — Send a test notificationGET /settings/oauth-providers/ — List OAuth providersPOST /settings/oauth-providers/ — Create an OAuth providerDELETE /settings/oauth-providers/{provider_id} — Delete an OAuth providerPUT /settings/oauth-providers/{provider_id} — Update an OAuth providerPOST /settings/reset/ — Reset settings to defaultsGET /settings/tile-config/ — Get tile configurationGET /admin/embed-tokens/ — List embed tokensPOST /admin/embed-tokens/bulk-revoke/ — Revoke several embed tokensGET /audit/datasets/{dataset_id}/column-ddl — List a dataset's column change historyGET /auth/api-keys/ — List your API keysPOST /auth/api-keys/ — Create an API keyDELETE /auth/api-keys/{key_id} — Revoke an API keyPOST /auth/change-password/ — Change your passwordGET /auth/config/ — Get the public sign-in configurationPOST /auth/download-token/{dataset_id} — Create a download token for a datasetPOST /auth/login — Sign in with a username and passwordPOST /auth/logout/ — Sign out everywherePOST /auth/logout/session/ — Sign out of the current sessionGET /auth/me/ — Get the signed-in userGET /auth/me/permissions/ — Get the signed-in user's permissionsGET /auth/me/usage/ — Get the signed-in user's quota usageGET /auth/oauth/{provider_slug}/callback — Finish OAuth sign-inGET /auth/oauth/{provider_slug}/login — Start OAuth sign-inPOST /auth/oauth/exchange/ — Exchange a sign-in code for a sessionGET /auth/oauth/providers/ — List sign-in providersPOST /auth/refresh/ — Refresh the access tokenPOST /auth/register/ — Register an accountPOST /auth/resend-verification/ — Resend the verification emailPOST /auth/verify-email/ — Verify an email addressPOST /config-ops/dry-run/ — Preview a configuration importGET /config-ops/export/ — Export the configurationPOST /config-ops/import/ — Import a configurationPOST /config-ops/validate/ — Validate the configurationGET /catalog/collections/ — List collectionsPOST /catalog/collections/ — Create a collectionDELETE /catalog/collections/{collection_id} — Delete a collectionGET /catalog/collections/{collection_id} — Get a collectionPATCH /catalog/collections/{collection_id} — Update a collectionGET /catalog/collections/{collection_id}/datasets/ — List a collection's datasetsPOST /catalog/collections/{collection_id}/datasets/ — Add datasets to a collectionDELETE /catalog/collections/{collection_id}/datasets/{dataset_id} — Remove a dataset from a collectionGET /datasets/ — List datasetsDELETE /datasets/{dataset_id} — Delete a datasetGET /datasets/{dataset_id} — Get a datasetPATCH /datasets/{dataset_id} — Update dataset metadataGET /datasets/{dataset_id}/api-keys — List a dataset's API keysPOST /datasets/{dataset_id}/api-keys — Create a dataset API keyDELETE /datasets/{dataset_id}/api-keys/{key_id} — Revoke a dataset API keyGET /datasets/{dataset_id}/copc/{attempt_id}/{name}.copc.laz — Get a COPC point cloud fileGET /datasets/{dataset_id}/export — Export a datasetGET /datasets/{dataset_id}/history — List a dataset's audit historyGET /datasets/{dataset_id}/quicklook — Get a dataset quicklook imageGET /datasets/{dataset_id}/refresh-runs — List a dataset's refresh runsPUT /datasets/{dataset_id}/retention/ — Set a dataset's row retentionGET /datasets/{dataset_id}/tiles3d/{path} — Get a 3D Tiles filePOST /datasets/bulk-delete/ — Delete several datasetsPOST /datasets/create/ — Create an empty datasetPOST /ingest/commit-fan-out/{job_id} — Commit a staged file as one import per layerPOST /ingest/commit/{job_id} — Commit a staged file for importGET /ingest/discover/ — Discover unregistered PostGIS tablesPOST /ingest/manifest/apply — Apply an ingest manifestPOST /ingest/preview/{job_id} — Preview a staged filePOST /ingest/register/ — Register a PostGIS tablePOST /ingest/register/bulk/ — Register several PostGIS tablesPOST /ingest/upload — Upload a file for stagingGET /ingest/upload/config — Get the upload configurationPOST /ingest/upload/presigned — Request a presigned uploadPOST /ingest/upload/presigned/{job_id}/complete — Complete a presigned uploadPOST /ingest/upload/url — Import a file from a URLPOST /ingest/vrt/{dataset_id}/sources/ — Add a source to a VRT datasetDELETE /ingest/vrt/{dataset_id}/sources/{source_dataset_id}/ — Remove a source from a VRT datasetPOST /ingest/vrt/create — Create a VRT datasetPOST /services/arcgis/signin/ — Sign in to an ArcGIS portalGET /services/connectors/ — List connectorsPOST /services/connectors/{connector_name}/discover/ — Discover connector resourcesPOST /services/connectors/{connector_name}/ingest/ — Start a connector ingestPOST /services/databases/{connection}/imports/ — Import a table from a database connectionGET /services/databases/{connection}/tables/ — List a database connection's spatial tablesPOST /services/preview/ — Preview a remote service layerPOST /services/probe/ — Probe a remote service URLPOST /datasets/{dataset_id}/aggregate/ — Compute a dataset aggregatePOST /datasets/{dataset_id}/analysis/materialize/ — Save a spatial analysis as a datasetPOST /datasets/{dataset_id}/analysis/preview/ — Preview a spatial analysisGET /datasets/{dataset_id}/maps/ — List maps that use a datasetGET /datasets/{dataset_id}/related/ — List related datasetsGET /datasets/{dataset_id}/rows/ — List dataset rowsPATCH /datasets/{dataset_id}/status/ — Change a dataset's publication statusPATCH /datasets/{dataset_id}/target-status/ — Move a dataset to a target publication statusGET /datasets/{dataset_id}/validate/ — Get a dataset's validation statusGET /datasets/{dataset_id}/dcat-us/3.0/ — Get a DCAT-US 3 recordGET /datasets/{dataset_id}/dcat-us/3.0/validation/ — Validate a dataset as DCAT-US 3GET /datasets/{dataset_id}/dcat/ — Get a DCAT 3 recordGET /datasets/{dataset_id}/dcat/validation/ — Validate a dataset as DCAT 3GET /datasets/{dataset_id}/download/cog — Download a raster as a Cloud-Optimized GeoTIFFGET /datasets/{dataset_id}/geodcat-ap/ — Get a GeoDCAT-AP recordGET /datasets/{dataset_id}/geodcat-ap/validation/ — Validate a dataset as GeoDCAT-APGET /datasets/dcat-us/3.0/ — Get the DCAT-US 3 catalogGET /datasets/dcat-us/3.0/validation/ — Validate the DCAT-US 3 catalogGET /datasets/dcat/ — Get the DCAT 3 catalogGET /datasets/dcat/validation/ — Validate the DCAT 3 catalogGET /datasets/geodcat-ap/ — Get the GeoDCAT-AP catalogGET /datasets/geodcat-ap/validation/ — Validate the GeoDCAT-AP catalogGET /datasets/{dataset_id}/attributes/ — List a dataset's attributesGET /datasets/{dataset_id}/attributes/{attribute_id}/ — Get an attributePATCH /datasets/{dataset_id}/attributes/{attribute_id}/ — Update an attributePOST /datasets/{dataset_id}/attributes/{attribute_id}/reset/ — Reset an attribute to its detected valuesGET /datasets/{dataset_id}/columns/{column_name}/stats/ — Get a numeric column's statisticsGET /datasets/{dataset_id}/columns/{column_name}/values/ — List a column's distinct valuesGET /datasets/{dataset_id}/features/{gid}/related/{relationship_id}/ — List a feature's related recordsPUT /datasets/{dataset_id}/groups/ — Set the sharing groups for a datasetGET /datasets/{dataset_id}/relationships/ — List a dataset's relationshipsPOST /datasets/{dataset_id}/relationships/ — Create a dataset relationshipGET /datasets/{dataset_id}/versions/ — List a dataset's versionsDELETE /datasets/relationships/{relationship_id}/ — Delete a dataset relationshipDELETE /datasets/{dataset_id}/previous-version — Delete the previous versionPOST /datasets/{dataset_id}/previous-version/restore — Restore the previous versionDELETE /datasets/{dataset_id}/previous-versions/{version_number} — Delete a kept versionPOST /datasets/{dataset_id}/previous-versions/{version_number}/restore — Restore a kept versionPOST /datasets/{dataset_id}/refresh — Refresh a dataset from its sourcePOST /datasets/{dataset_id}/reupload — Stage a file to replace a dataset's dataPOST /datasets/{dataset_id}/reupload/{job_id}/commit — Commit a re-uploadPOST /datasets/{dataset_id}/reupload/{job_id}/preview — Preview a re-uploadPOST /datasets/{dataset_id}/reupload/presigned — Request a presigned re-uploadPOST /datasets/{dataset_id}/reupload/presigned/{job_id}/complete — Complete a presigned re-uploadPOST /datasets/{dataset_id}/reupload/service/preview — Preview a service layer for re-uploadPOST /datasets/{dataset_id}/source-health/ — Check a dataset's sourceGET /datasets/{dataset_id}/vrt-sources/ — List a VRT dataset's sourcesGET /datasets/{dataset_id}/vrt/generations/ — List a VRT dataset's generationsPOST /datasets/{dataset_id}/vrt/regenerate/ — Regenerate a VRT datasetGET /datasets/{dataset_id}/vrt/status/ — Get a VRT dataset's statusGET /maps/{map_id}/embed-tokens/ — List a map's embed tokensPOST /maps/{map_id}/embed-tokens/ — Create an embed tokenDELETE /maps/{map_id}/embed-tokens/{token_id}/ — Revoke an embed tokenPATCH /maps/{map_id}/embed-tokens/{token_id}/ — Update an embed tokenGET /datasets/{dataset_id}/features.geojson — Get features as GeoJSON with Z coordinatesGET /datasets/{dataset_id}/features/ — List featuresPOST /datasets/{dataset_id}/features/ — Create a featureDELETE /datasets/{dataset_id}/features/{gid} — Delete a featureGET /datasets/{dataset_id}/features/{gid} — Get a featurePATCH /datasets/{dataset_id}/features/{gid} — Update a featurePUT /datasets/{dataset_id}/features/{gid} — Replace a featurePOST /datasets/{dataset_id}/features/delete/ — Delete several featuresPOST /datasets/{dataset_id}/features/dry-run/ — Check a feature create without savingGET /groups/mine/ — List the sharing groups you can share withGET /health — Check service healthGET /ai/availability/ — Check whether AI chat is availablePOST /ai/chat/ — Edit a map with AI chatPOST /ai/chat/dataset/stream/ — Ask AI about a datasetPOST /ai/chat/stream/ — Edit a map with AI chat as a streamPOST /ai/generate-map/ — Generate a map from a promptPOST /ai/generate-map/stream/ — Generate a map from a prompt as a streamPOST /ai/metadata/keywords/ — Suggest dataset keywords with AIPOST /ai/metadata/lineage/ — Draft dataset lineage with AIPOST /ai/metadata/quality-statement/ — Draft a dataset quality statement with AIPOST /ai/metadata/summary/ — Draft a dataset summary with AIPOST /layers/ — Create an empty layerPOST /layers/{dataset_id}/columns/ — Add a columnDELETE /layers/{dataset_id}/columns/{column_name} — Drop a columnPATCH /layers/{dataset_id}/columns/{column_name}/name — Rename a columnGET /layers/{dataset_id}/columns/{column_name}/references — Count maps that reference a columnPATCH /layers/{dataset_id}/columns/{column_name}/type — Change a column's typeGET /maps/ — List mapsPOST /maps/ — Create a mapDELETE /maps/{map_id} — Delete a mapGET /maps/{map_id} — Get a mapPATCH /maps/{map_id} — Transfer a map to another ownerPUT /maps/{map_id} — Update a mapGET /maps/{map_id}/access/ — Get the caller's access to a mapPOST /maps/{map_id}/duplicate/ — Duplicate a mapPUT /maps/{map_id}/groups/ — Set the sharing groups for a mapGET /maps/{map_id}/history — List a map's edit historyPATCH /maps/{map_id}/layers — Change a map's layersPOST /maps/{map_id}/layers — Add a layer to a mapDELETE /maps/{map_id}/layers/{layer_id} — Remove a layer from a mapPOST /maps/{map_id}/layers/bulk-delete — Remove several layers from a mapGET /maps/{map_id}/og-image/ — Get a map social card imagePUT /maps/{map_id}/og-image/ — Upload a map social card imageDELETE /maps/{map_id}/share/ — Revoke a map share tokenGET /maps/{map_id}/share/ — Get a map's share tokenPATCH /maps/{map_id}/share/ — Update a map share tokenPOST /maps/{map_id}/share/ — Create a map share tokenGET /maps/{map_id}/stories/ — List stories that use a mapGET /maps/{map_id}/style.json — Export a map as a MapLibre styleGET /maps/{map_id}/thumbnail/ — Get a map thumbnailPUT /maps/{map_id}/thumbnail/ — Upload a map thumbnailGET /maps/{map_id}/visibility-check/ — Check which layers a map's audience cannot seeGET /maps/icons — List map iconsPOST /maps/icons — Upload a map iconGET /maps/icons/{icon_id}/asset — Get a map icon imagePOST /maps/import — Import a MapLibre style as a mapPOST /maps/import/arcgis-webmap/ — Import an ArcGIS web mapGET /maps/shared/{token} — Get a shared mapGET /maps/sprites/geolens-prefixed.json — Get the GeoLens sprite index with prefixed namesGET /maps/sprites/geolens-prefixed.png — Get the GeoLens sprite sheet for the prefixed indexGET /maps/sprites/geolens.json — Get the GeoLens sprite indexGET /maps/sprites/geolens.png — Get the GeoLens sprite sheetGET / — Get the OGC API landing pageGET /collections — List OGC collectionsGET /collections/{dataset_id} — Get a dataset's OGC feature collectionGET /collections/{dataset_id}/items — List OGC featuresGET /collections/{dataset_id}/items/{feature_id} — Get an OGC featureGET /collections/{dataset_id}/queryables — Get a feature collection's queryablesGET /collections/datasets — Get the datasets collectionGET /collections/datasets/items — List catalog recordsGET /collections/datasets/items/{record_id} — Get a catalog recordGET /collections/datasets/queryables — Get the datasets collection queryablesGET /collections/datasets/schema — Get the catalog record schemaGET /collections/datasets/sortables — Get the datasets collection sortablesGET /conformance — Get the OGC conformance declarationPOST /query/ — Run a read-only SQL queryGET /records/{record_id}/contacts/ — List a record's contactsPOST /records/{record_id}/contacts/ — Add a record contactDELETE /records/{record_id}/contacts/{contact_id}/ — Delete a record contactPATCH /records/{record_id}/contacts/{contact_id}/ — Update a record contactGET /records/{record_id}/distributions/ — List a record's distributionsPOST /records/{record_id}/distributions/ — Add a record distributionDELETE /records/{record_id}/distributions/{distribution_id}/ — Delete a record distributionPATCH /records/{record_id}/distributions/{distribution_id}/ — Update a record distributionGET /records/{record_id}/keywords/ — List a record's keywordsPOST /records/{record_id}/keywords/ — Add a record keywordDELETE /records/{record_id}/keywords/{keyword_id}/ — Delete a record keywordGET /records/{record_id}/translations/ — List a record's translationsDELETE /records/{record_id}/translations/{language}/ — Delete a record translationPUT /records/{record_id}/translations/{language}/ — Set a record translationGET /search/datasets/ — Search datasetsGET /search/facets/ — Get search facet countsGET /search/saved/ — List saved searchesPOST /search/saved/ — Save a searchDELETE /search/saved/{search_id} — Delete a saved searchGET /search/saved/{search_id} — Get a saved searchGET /stac/ — Get the STAC landing pageGET /stac/collections — List STAC collectionsGET /stac/collections/{collection_id} — Get a STAC collectionGET /stac/collections/{collection_id}/items — List STAC items in a collectionGET /stac/collections/{collection_id}/items/{item_id} — Get a STAC item in a collectionGET /stac/conformance — Get the STAC conformance classesGET /stac/items/{item_id} — Get a STAC itemGET /stac/search — Search STAC items with GETPOST /stac/search — Search STAC items with POSTPOST /services/stac/asset-sizes — Look up STAC asset sizesPOST /services/stac/collections — List collections in a STAC APIPOST /services/stac/connect — Connect to a STAC APIPOST /services/stac/import — Import STAC items as datasetsPOST /services/stac/search — Search items in a STAC APIGET /stories/ — List storiesPOST /stories/ — Create a storyDELETE /stories/{story_id} — Delete a storyGET /stories/{story_id} — Get a storyPATCH /stories/{story_id} — Update a storyPOST /stories/{story_id}/assets — Upload a story imageGET /stories/{story_id}/assets/{asset_id} — Get a story imagePOST /stories/{story_id}/discard — Discard a story draftGET /stories/{story_id}/draft — Get a story draftPUT /stories/{story_id}/draft — Save a story draftPOST /stories/{story_id}/duplicate — Duplicate a storyPUT /stories/{story_id}/groups/ — Set the sharing groups for a storyPOST /stories/{story_id}/publish — Publish a storyGET /stories/frame-hosts/ — List hosts a story may embedGET /tiles/{table_path}/{z}/{x}/{y}.pbf — Get a vector tileGET /tiles/clusters/{table_path}/{z}/{x}/{y}.pbf — Get a clustered vector tileGET /tiles/raster-proxy/{dataset_id}/{z}/{x}/{y}.{fmt} — Get a raster tileGET /tiles/token/{dataset_id}/ — Create a tile tokenPOST /tiles/tokens/ — Create tile tokens for several datasets