Metadata API
Entities, fields, saved queries, screens, scripts, database connections, table and view definitions, environment diffs and releases.
- Service
- Metadata service
- Base path
https://your-metadata-host/api/v1- Authentication
- Bearer token and context headers.
The metadata service stores the definition of every application. Reads are cached per app and tenant. A tenant that subscribes to an app reads the app owner's definitions unless it has its own.
/api/v1/appobject/{appObjectName}Get an entity with its fields
Returns the entity definition. Use appObjectId from the response as the entity's identifier.
| Name | In | Required | Description |
|---|---|---|---|
appObjectName | path | Yes | The entity name, for example Vendor. |
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/appobject/{appObjectName}/relationsGet an entity with its relationships
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/appobject/flagsTurn entity features on or off
Features include tracking, search, sharing, versioning, comments, lifecycle, approvals, soft delete and layouts.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/metadata/schemaGet the whole application schema
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/query/{queryId}Get a saved query
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/queryGet a saved query by entity and name
| Name | In | Required | Description |
|---|---|---|---|
appObjectName | query | Yes | Entity name. |
queryName | query | Yes | Saved query name, for example List_Vendor. |
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/query/upsertCreate or update a saved query
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/query/cloneClone a saved query
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/screen/{screenId}Get a screen definition for the signed-in user
Components the user may not use are marked hidden or disabled before the definition is returned.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/screen/upsertCreate or update a screen
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/customscriptList scripts for an entity
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/customscript/bynameGet a script by name
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/application/upserttableCreate or extend a table
Plans the change against the live schema and only creates, adds or alters; it never drops. A dry run returns the SQL without running it. Register the table as an entity afterwards.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/application/upsertviewCreate or replace a view
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/application/registerappobjectsRegister tables and views as entities
Creates the entity, its fields, default queries and default role access for each compatible table. Tables need a GUID primary key.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/application/syncappfieldsRe-sync entity fields with the table
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/application/setupPrepare an environment database
Applies the platform schema to the environment's database, and in Development registers compatible existing tables.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/customappfields/bulkAdd custom fields without a schema change
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/connections/testTest an environment's database connection
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/connections/schema/validateCheck a database for compatible tables
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/release/diff/metadataCompare definitions between two environments
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/release/diff/dataCompare configuration data between two environments
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.
/api/v1/release/applyApply a release to the next environment
Applies the selected definitions, configuration data (in foreign-key order) and migration scripts, then pins the target environment to the release version. The same release cannot be applied twice.
The route is part of the service today. Its request and response schema will be published here; until then, use the OpenAPI document on your environment.