Version v0.46 of Metabase is no longer supported. Check out the docs for the current stable version, Metabase v0.63.
Sandbox GTAP
/api/mt/gtap endpoints, for CRUD operations and the like on GTAPs (Group Table Access Policies).
DELETE /api/mt/gtap/:id
Delete a GTAP entry.
PARAMS:
id
GET /api/mt/gtap/
Fetch a list of all GTAPs currently in use, or a single GTAP if both group_id and table_id are provided.
PARAMS:
-
group_idnullable integer greater than 0 -
table_idnullable integer greater than 0
GET /api/mt/gtap/:id
Fetch GTAP by id.
PARAMS:
id
POST /api/mt/gtap/
Create a new GTAP.
PARAMS:
-
table_idvalue must be an integer greater than zero. -
card_idvalue may be nil, or if non-nil, value must be an integer greater than zero. -
group_idvalue must be an integer greater than zero. -
attribute_remappings
POST /api/mt/gtap/validate
Validate a sandbox which may not have yet been saved. This runs the same validation that is performed when the sandbox is saved, but doesn’t actually save the sandbox.
PARAMS:
-
table_idinteger greater than 0 -
card_idnullable integer greater than 0
PUT /api/mt/gtap/:id
Update a GTAP entry. The only things you’re allowed to update for a GTAP are the Card being used (card_id) or the
paramter mappings; changing table_id or group_id would effectively be deleting this entry and creating a new
one. If that’s what you want to do, do so explicity with appropriate calls to the DELETE and POST endpoints.
PARAMS:
-
id -
card_idvalue may be nil, or if non-nil, value must be an integer greater than zero.
Read docs for other versions of Metabase.