Rocketadmin

Delete row (CRUD) via DELETE /table/crud/{connectionId}. DESTRUCTIVE AND IRREVERSIBLE: permanently delete one row addressed by `primaryKey` and return ONLY the row as it was. The lean counterpart to the delete-row tool, and just as final: Rocketadmin has no recycle bin. Confirm by re-reading -- an absent row answers 400 "Row with this primary key not found", not 404. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Delete row via DELETE /table/row/{connectionId}. DESTRUCTIVE AND IRREVERSIBLE: permanently delete one row from the customer's own database, addressed by `primaryKey`. Answers 200 with the row as it was, which is the only copy you will get -- Rocketadmin has no recycle bin and nothing here restores a deleted row. Confirm a deletion by re-reading: an absent row answers 400 "Row with this primary key not found", not 404. A row other tables reference by foreign key may fail to delete, or may cascade, according to the database's own constraints. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Check API key via GET /check/apikey. Confirm this connection's Rocketadmin API key is still valid. Answers {"result": true, "message": "Api key is valid"} for a live key. This is the cheapest way to tell a revoked key from a genuine failure elsewhere: a rejected key answers 404 with the body "No authorization keys found", which is the SAME STATUS an unrouted path answers -- read the message, not the status. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

List tables via GET /connection/tables/{connectionId}. List the tables and views in one connected database, each with the permissions this credential has on it (read, add, edit, delete) and its display name. Start here: every row and structure tool needs a `tableName` from this list. Set `hidden` to include tables the connection's owner has hidden from the dashboard. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

List tables (v2) via GET /connection/tables/v2/{connectionId}. List the tables in one connected database, wrapped in a `tables` object rather than returned as a bare array. Same content as the v1 tool, newer envelope -- prefer this one in new work; the v1 spelling is kept because Rocketadmin still serves it. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

List database connections via GET /connections. List the databases this Rocketadmin account has connected, with each connection's id, title, engine type, host, port, database name and access level. THE CONNECTION ID THIS RETURNS IS WHAT EVERY OTHER TOOL NEEDS: it is a short opaque string such as "S2ds5cFA", not a UUID. Agentic Fabriq removes each connection's `signing_key` from this result before you see it -- that value signs Rocketadmin's own embedded-view URLs and is credential material, not data. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Read row (CRUD) via GET /table/crud/{connectionId}. Read one row addressed by `primaryKey` and return ONLY the row -- no structure, no foreign keys, no widgets. The lean counterpart to the get-row tool; prefer it when you want the data rather than the table's description. An absent row answers 400 "Row with this primary key not found". Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Get row by primary key via GET /table/row/{connectionId}. Read one row addressed by its primary key, returned with the table's structure, foreign keys and widget configuration around it. Pass `primaryKey` as a JSON object of the table's primary-key columns, for example {"id": 36}; the table-structure tool's `primaryColumns` names them. For just the row and nothing else, use the CRUD read tool. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

List table rows via GET /table/rows/{connectionId}. Read a page of rows from one table, with the table's structure, primary columns, foreign keys and pagination alongside them. Page with `page` and `perPage` and narrow with `search`, which matches the columns the connection's owner marked searchable. For filtering by column value use the body-filter tool instead. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Get table structure via GET /table/structure/{connectionId}. Describe one table's columns -- name, data type, default, nullability, auto-increment, maximum length -- plus its `primaryColumns`, its foreign keys and the table's configured settings. READ THIS BEFORE ADDRESSING A SINGLE ROW: `primaryColumns` names the columns the `primaryKey` argument of the row tools must carry. Served from Rocketadmin's cache. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Get table structure (uncached) via GET /table/structure/no-cache/{connectionId}. The same table description read straight from the database rather than from Rocketadmin's cache. Use it after the schema has been altered, when the cached tool still reports the old columns. Slower; otherwise identical. Reads only; changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Create row (CRUD) via POST /table/crud/{connectionId}. Insert one row and return ONLY the created row, including its generated primary key. The lean counterpart to the add-row tool. THIS WRITES TO THE CUSTOMER'S OWN DATABASE, with no sandbox between this tool and it. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Find rows (CRUD) via POST /table/crud/rows/{connectionId}. Read rows filtered by column value and return ONLY `rows` and `pagination`. The lean counterpart to the find-rows tool; same `filters` body. A POST because the criteria are a document: it reads only and changes nothing. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Export table as CSV via POST /table/csv/export/{connectionId}. Export rows from a table as CSV text, filtered by the same `filters` body the find tools take and narrowed by `page`, `perPage` and `search` -- all four of which Rocketadmin marks REQUIRED on this route, so send them even when exporting everything. Answers CSV with a header row, declared as application/octet-stream; Agentic Fabriq returns it as text. Reads only; changes nothing in the database. Mind the size: an unfiltered export of a large table is a large response. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Import CSV into table via POST /table/csv/import/{connectionId}. Insert rows into a table from a CSV file, uploaded as multipart form data under the field name `file` with a header row naming the columns. THIS WRITES MANY ROWS AT ONCE to the customer's own database and there is no dry run: a malformed file is discovered by its effect. UNVERIFIED END-TO-END: Rocketadmin refuses CSV import on DEMO/TEST connections (400 "CSV import is disabled for test connections"), and both connections available for verification were test connections, so the upload shape was confirmed but a successful import was not. If this answers that message, the connection is a test connection and the file is not the problem. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Add row via POST /table/row/{connectionId}. Insert one row into a table. The body is the row itself -- an object of column -> value -- and columns the database fills (auto-increment keys, defaults, timestamps) should be omitted. Answers 201 with the created row, including the generated primary key, which is the value to keep for later reads and updates. THIS WRITES TO THE CUSTOMER'S OWN DATABASE: Rocketadmin is a window onto a real production database, and there is no sandbox between this tool and it. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Find table rows via POST /table/rows/find/{connectionId}. Read rows from one table filtered by column value. The body carries `filters`, an object of column -> operator -> value, for example {"filters": {"country": {"eq": "US"}, "age": {"gt": 18}}}. THIS IS A POST BECAUSE THE CRITERIA ARE A DOCUMENT, NOT BECAUSE IT WRITES: it reads only and changes nothing. Page with `page` and `perPage`; set `_uncached` to bypass Rocketadmin's cache. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Update row (CRUD) via PUT /table/crud/{connectionId}. Update one row addressed by `primaryKey`, sending only the columns to change, and return ONLY the updated row. The lean counterpart to the update-row tool. THIS WRITES TO THE CUSTOMER'S OWN DATABASE, with no sandbox between this tool and it. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Update row via PUT /table/row/{connectionId}. Update one row addressed by `primaryKey`, sending ONLY the columns to change -- this is a partial update and omitted columns are left alone. Answers with the updated row plus the table's structure. THIS WRITES TO THE CUSTOMER'S OWN DATABASE, with no sandbox between this tool and it; read the row first if you need to be able to put it back. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Delete rows in bulk via PUT /table/rows/delete/{connectionId}. DESTRUCTIVE AND IRREVERSIBLE: permanently delete several rows from the customer's own database. The body is an ARRAY of primary-key objects, for example [{"id": 38}, {"id": 39}] -- Rocketadmin's own spec types this as an array of strings, which is wrong; measured, it is an array of objects. A request naming no row is refused here rather than sent, because what Rocketadmin does with an empty array against a whole table is not documented. Answers `true` without a per-row result, so confirm by re-reading. Nothing restores a deleted row. NOTE THE VERB: this is a PUT on Rocketadmin's API, and it deletes. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.

Update rows in bulk via PUT /table/rows/update/{connectionId}. Update several rows at once to the SAME new values. The body carries `primaryKeys`, an array of primary-key objects, and `newValues`, the columns to set on every one of them -- for example {"primaryKeys": [{"id": 38}, {"id": 39}], "newValues": {"city": "Berlin"}}. Answers {"success": true} WITHOUT saying how many rows matched, so confirm by re-reading rather than by the status. THIS WRITES TO THE CUSTOMER'S OWN DATABASE, with no sandbox between this tool and it. A Rocketadmin API key carries its owner's full permissions over every database that account has connected -- Rocketadmin publishes no scope vocabulary and nothing is ticked when a key is minted -- so the narrowing is which actions this connection may call.