Apps

Make a per-user table shared again

Removes the per-user marking: the app can use the table with plain SQL again, and nothing keeps users' rows apart any more. The rows stay.

delete/apps/{id}/tables/{table}/owner

Request

  • Base URL: https://api.hypamoon.com/api/v1
  • URL: https://api.hypamoon.com/api/v1/apps/{id}/tables/{table}/owner
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL https://app.hypamoon.com/oauth/authorize, token URL https://api.hypamoon.com/oauth/token, scopes: sites:write)

Path parameters

idstring uuid required

The id of the app.

tablestring required

The name of a table in the app's database.

Response

The app.

idstring uuid required
namestring required
site_idstring uuid required
urlstring required

The site; the app answers on url + /api.

api_urlstring required

Where the app's /api starts.

mode'live' | 'test' required
status'active' | 'offline' required

offline: Hypamoon took the site offline; the app does not run.

versioninteger required

The version that runs now.

allowed_hostsstring[] required
secretsstring[] required
keptstring[]

Only in the answer to a deploy of an existing app: the settings that were left out and kept from the running version, like "allowed_hosts (20)", "vars (2)", "database", "auth".

warningsstring[]

Only in the answer to a deploy: advice about the app's data, never a block. For example that export and delete per user won't cover the data (no table marked with set_table_owner_column), or tables that look like backups or copies. Tell the user in plain words and offer to fix it.

created_atstring required
updated_atstring required

Changes

No recorded changes to this operation across all 1 revision of this API.