Class AsyncRawSchemasClient

java.lang.Object
ai.vectros.resources.schemas.AsyncRawSchemasClient

public class AsyncRawSchemasClient extends Object
  • Field Details

  • Constructor Details

    • AsyncRawSchemasClient

      public AsyncRawSchemasClient(ClientOptions clientOptions)
  • Method Details

    • listSchemas

      Returns a paginated list of the record schemas defined in your account. Filter by userId or orgId to scope to an owner, by surface to list the types bindable to one surface, or by recordType to resolve the single schema for a type directly. Filtering by an identity surface (user, org, or client) lists your account-wide identity schemas regardless of the calling context; filtering by record or document lists within the calling context. Requires the schemas:r scope.
    • listSchemas

      public CompletableFuture<VectrosApiHttpResponse<SchemaPage>> listSchemas(RequestOptions requestOptions)
      Returns a paginated list of the record schemas defined in your account. Filter by userId or orgId to scope to an owner, by surface to list the types bindable to one surface, or by recordType to resolve the single schema for a type directly. Filtering by an identity surface (user, org, or client) lists your account-wide identity schemas regardless of the calling context; filtering by record or document lists within the calling context. Requires the schemas:r scope.
    • listSchemas

      Returns a paginated list of the record schemas defined in your account. Filter by userId or orgId to scope to an owner, by surface to list the types bindable to one surface, or by recordType to resolve the single schema for a type directly. Filtering by an identity surface (user, org, or client) lists your account-wide identity schemas regardless of the calling context; filtering by record or document lists within the calling context. Requires the schemas:r scope.
    • listSchemas

      public CompletableFuture<VectrosApiHttpResponse<SchemaPage>> listSchemas(ListSchemasRequest request, RequestOptions requestOptions)
      Returns a paginated list of the record schemas defined in your account. Filter by userId or orgId to scope to an owner, by surface to list the types bindable to one surface, or by recordType to resolve the single schema for a type directly. Filtering by an identity surface (user, org, or client) lists your account-wide identity schemas regardless of the calling context; filtering by record or document lists within the calling context. Requires the schemas:r scope.
    • createSchema

      Defines a new record type with optional field definitions, validation rules, and lookup indexes. Idempotent by typeName within the same ownership scope: re-creating an existing typeName returns the existing schema rather than failing. The response's created field (and the HTTP status — 201 when created, 200 when an existing schema was returned) tells the two apart. To reconcile an existing schema to the submitted shape instead of returning it unchanged, set ?upsert=true (this also requires the schemas:w scope; only legal schema changes are applied — migration-locked changes are rejected). Requires the schemas:w scope.
    • createSchema

      Defines a new record type with optional field definitions, validation rules, and lookup indexes. Idempotent by typeName within the same ownership scope: re-creating an existing typeName returns the existing schema rather than failing. The response's created field (and the HTTP status — 201 when created, 200 when an existing schema was returned) tells the two apart. To reconcile an existing schema to the submitted shape instead of returning it unchanged, set ?upsert=true (this also requires the schemas:w scope; only legal schema changes are applied — migration-locked changes are rejected). Requires the schemas:w scope.
    • createSchema

      Defines a new record type with optional field definitions, validation rules, and lookup indexes. Idempotent by typeName within the same ownership scope: re-creating an existing typeName returns the existing schema rather than failing. The response's created field (and the HTTP status — 201 when created, 200 when an existing schema was returned) tells the two apart. To reconcile an existing schema to the submitted shape instead of returning it unchanged, set ?upsert=true (this also requires the schemas:w scope; only legal schema changes are applied — migration-locked changes are rejected). Requires the schemas:w scope.
    • createSchema

      Defines a new record type with optional field definitions, validation rules, and lookup indexes. Idempotent by typeName within the same ownership scope: re-creating an existing typeName returns the existing schema rather than failing. The response's created field (and the HTTP status — 201 when created, 200 when an existing schema was returned) tells the two apart. To reconcile an existing schema to the submitted shape instead of returning it unchanged, set ?upsert=true (this also requires the schemas:w scope; only legal schema changes are applied — migration-locked changes are rejected). Requires the schemas:w scope.
    • getSchema

      Retrieves a single record schema by its id. Requires the schemas:r scope.
    • getSchema

      Retrieves a single record schema by its id. Requires the schemas:r scope.
    • getSchema

      Retrieves a single record schema by its id. Requires the schemas:r scope.
    • getSchema

      Retrieves a single record schema by its id. Requires the schemas:r scope.
    • updateSchema

      Updates a record schema. Fields you omit are preserved; typeName is immutable and cannot be changed. Collection fields (fields, lookupFields, renderHints, capabilities) are replaced in full when supplied. Requires the schemas:w scope.
    • updateSchema

      Updates a record schema. Fields you omit are preserved; typeName is immutable and cannot be changed. Collection fields (fields, lookupFields, renderHints, capabilities) are replaced in full when supplied. Requires the schemas:w scope.
    • deleteSchema

      Permanently deletes a record schema. The request is refused with 409 if records of this type still exist — delete those records first, since every record must reference a live schema. Requires the schemas:w scope.
    • deleteSchema

      public CompletableFuture<VectrosApiHttpResponse<Void>> deleteSchema(String id, RequestOptions requestOptions)
      Permanently deletes a record schema. The request is refused with 409 if records of this type still exist — delete those records first, since every record must reference a live schema. Requires the schemas:w scope.
    • deleteSchema

      Permanently deletes a record schema. The request is refused with 409 if records of this type still exist — delete those records first, since every record must reference a live schema. Requires the schemas:w scope.
    • deleteSchema

      public CompletableFuture<VectrosApiHttpResponse<Void>> deleteSchema(String id, DeleteSchemaRequest request, RequestOptions requestOptions)
      Permanently deletes a record schema. The request is refused with 409 if records of this type still exist — delete those records first, since every record must reference a live schema. Requires the schemas:w scope.
    • getSchemaVersions

      Returns the audit trail of changes to a record schema, newest first (create, update, and delete). Schema version history is always recorded — there is no per-schema toggle to disable it. Requires the schemas:r scope.
    • getSchemaVersions

      public CompletableFuture<VectrosApiHttpResponse<ModelDataVersionPage>> getSchemaVersions(String id, RequestOptions requestOptions)
      Returns the audit trail of changes to a record schema, newest first (create, update, and delete). Schema version history is always recorded — there is no per-schema toggle to disable it. Requires the schemas:r scope.
    • getSchemaVersions

      Returns the audit trail of changes to a record schema, newest first (create, update, and delete). Schema version history is always recorded — there is no per-schema toggle to disable it. Requires the schemas:r scope.
    • getSchemaVersions

      Returns the audit trail of changes to a record schema, newest first (create, update, and delete). Schema version history is always recorded — there is no per-schema toggle to disable it. Requires the schemas:r scope.