Skip to content
getgeolens.com
GeoLens DocsEarly release

Bulk Register Tables

POST
/ingest/register/bulk/
 
curl --request POST \
  --url https://example.com/api/ingest/register/bulk/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "tables": [ { "table_name": "example", "title": "example", "summary": "example", "visibility": "private" } ] }'

Bulk-register multiple existing PostGIS tables as datasets.

Each table is registered independently — one failure does not block others. Tables are processed in parallel via asyncio.gather with a fresh session per task, which keeps transaction isolation while removing the sequential per-table latency (PERF-3).

Authorizations

Section titled “Authorizations ”

Request Body required

Section titled “Request Body required ”
Media type application/json
BulkRegisterRequest
object
tables
required
Tables

List of tables to register as datasets in a single request.

Array<object>
BulkRegisterItem
object
table_name
required
Table Name

PostgreSQL table name to register.

string
<= 63 characters
title
required
Title

Human-readable dataset title.

string
<= 500 characters
summary
Any of:
string
<= 5000 characters
visibility
Visibility

Dataset visibility level.

string
default: private
Allowed values: private restricted internal public

Responses

Section titled “ Responses ”

201

Section titled “201 ”

Successful Response

Media type application/json
BulkRegisterResponse
object
results
required
Results

Per-table registration results, in the same order as the request.

Array<object>
BulkRegisterResult
object
table_name
required
Table Name

Source table that was processed.

string
status
required
Status

Per-row outcome: ‘success’, ‘skipped’, or ‘error’.

string
dataset_id
Any of:
string format: uuid
title
Any of:
string
error
Any of:
string
Example generated
{
  "results": [
    {
      "table_name": "example",
      "status": "example",
      "dataset_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
      "title": "example",
      "error": "example"
    }
  ]
}

400

Section titled “400 ”

Bad request — invalid payload

401

Section titled “401 ”

Unauthorized — missing or invalid credentials

403

Section titled “403 ”

Forbidden — caller lacks write access

404

Section titled “404 ”

Not found

409

Section titled “409 ”

Conflict — resource state prevents the operation

422

Section titled “422 ”

Validation error

500

Section titled “500 ”

Internal server error