Populate and Publish DB2 Table APIs

In DB2 → Schemas, expand a schema and select Populate APIs.

1. Optionally enable Publish immediately after save.
2. Select tables and API operations: Get by PK, List, Create, Update, Delete, and Count.
3. Confirm the primary key. Tables without a key cannot be selected until one is specified.
4. Review the table × operation endpoint count and select Add.

The dialog reports success or failure for each table, so successful definitions are retained even if others fail. A DB2 catalog must exist; CoreIQ includes one by default.

Open Catalog → DB2 to filter definitions and publish, unpublish, or delete table APIs.

Published collection path: /api/v1/{catalogId}/{endpointName}/{schema}/{table}.

• List is QUERY on the collection (OpenAPI 3.2). With Generate an OpenAPI 3.0-compatible spec, the spec advertises GET …/list instead; the router serves GET …/list either way.
• Count is GET …/count.
• Create is POST on the collection.
• Get, Update, and Delete use a /{pkValue} path segment on DB2.