burstiq-lifegraph

Descriptor

Candidate descriptor · transport http

Tools

• getUserGroupById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get the user group in the secure data zone
• putUpdateUserGroup — Allowed user roles:
  
  • sdzAdmin
  • sdzGovernance
  
  
  put (update) a User group into the secure data zone
• deleteUserGroup — Allowed user roles:
  
  • sdzAdmin
  • sdzGovernance
  
  
  delete the user group in the secure data zone
• getUserWalletById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get the user's wallet in the secure data zone
• putUpdateUserWallet — Allowed user roles:
  
  • sdzAdmin
  • sdzUser
  
  
  put (update) the user's wallet into the secure data zone. these values will
• deleteUserWallet — Allowed user roles:
  
  • sdzAdmin
  
  
  delete the user's wallet in the secure data zone
• putUpdateUserTerms — Allowed user roles:
  
  • sdzUser
  
  
  put (update) the user's terms into the secure data zone
• getTermById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get a SDZ specific term (by Id)
• putTerms — Allowed user roles:
  
  • sdzAdmin
  
  
  Update a terms record for a specific SDZ
• putTermsActiveFlag — Allowed user roles:
  
  • sdzAdmin
  
  
  set a terms record to active (true) or inactive (false)
• getSystemWalletById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get the system's wallet in the secure data zone
• putUpdateSystemWallet — Allowed user roles:
  
  • sdzAdmin
  • sdzGovernance
  
  
  put (update) the system's wallet into the secure data zone
• deleteSystemWallet — Allowed user roles:
  
  • sdzAdmin
  • sdzGovernance
  
  
  delete the system's wallet in the secure data zone
• getQueryGlossaries — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query glossaries from the secure data zone
• putGlossary — Allowed user roles:
  
  • sdzAdmin
  
  
  DEPRECATED: Use /{id} endpoint instead. | Put (update or create) the Glossary in the secure d
• postGlossary — Allowed user roles:
  
  • sdzAdmin
  
  
  create a glossary term into the secure data zone
• getGlossary — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets a glossary by ID from the secure data zone; can be m
• putGlossary_1 — Allowed user roles:
  
  • sdzAdmin
  
  
  put (update) the Glossary in the secure data zone
• deleteGlossary — Allowed user roles:
  
  • sdzAdmin
  
  
  deletes a glossary by id from the secure data zone
• getEdgeById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get an edge. based on id
• putUpdateEdge — Allowed user roles:
  
  • sdzAdmin
  
  
  put (update) the edges in the secure data zone
• deleteEdgeById — Allowed user roles:
  
  • sdzAdmin
  
  
  delete an edge definition in the secure data zone, based on id
• getQueryDicts — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query dictionaries from the secure data zone
• putDict — Allowed user roles:
  
  • sdzAdmin
  
  
  DEPRECATED: Update with job instead. | Put (update) the dictionary in the secure data zone.
• postDict — Allowed user roles:
  
  • sdzAdmin
  
  
  DEPRECATED: Create with job instead. | Create a dictionary into the secure data zone.
  
• getIPById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get data pipeline in the secure data zone
• putPipeline — Allowed user roles:
  
  • sdzAdmin
  
  
  Update a data pipeline in the secure data zone (see POST for description of body)
• deleteById — Allowed user roles:
  
  • sdzAdmin
  
  
  get data pipeline in the secure data zone
• getJSTransformStepById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get JSTransformStep by id
• putJSTransformStep — Allowed user roles:
  
  • sdzAdmin
  
  
  Update a JsTransformStep
• deleteJSTransformStepById — Allowed user roles:
  
  • sdzAdmin
  
  
  Delete JSTransformStep by id
• getRuleSetStepId — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get RuleSetStep by id
• putRuleSetStep — Allowed user roles:
  
  • sdzAdmin
  
  
  Update a RuleSetStep
• deleteRuleSetStepById — Allowed user roles:
  
  • sdzAdmin
  
  
  Delete RuleSetStep by id
• getFieldMappingStepById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get FieldMappingSteps by id
• putFieldMappingStep — Allowed user roles:
  
  • sdzAdmin
  
  
  Update a new FieldMappingStep
• deleteFieldMappingStepById — Allowed user roles:
  
  • sdzAdmin
  
  
  Delete FieldMappingSteps by id
• getRuleById — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get Rule by id
• putRule — Allowed user roles:
  
  • sdzAdmin
  
  
  Update a Rule
• deleteRuleById — Allowed user roles:
  
  • sdzAdmin
  
  
  Delete Rule by id
• putRequeueJobs — Allowed user roles:
  
  • biqAdmin
  • sdzAdmin
  
  
  requeue jobs IF the job queue is empty but there are queued jobs in the SDZ
• putUpdateEdgeById — Allowed user roles:
  
  • sdzUser
  
  
  updates an edge with a from chain and edge ID; must be owner or limited owner
• putUpsertAsset — Allowed user roles:
  
  • sdzUser
  
  
  upsert asset by primary key
• postCreateAsset — Allowed user roles:
  
  • sdzUser
  
  
  create an asset in a chain
• patchAsset — Allowed user roles:
  
  • sdzUser
  
  
  patch specific elements of the asset by primary key (inline with other data)
• getSDO — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  get smart data object by sdo id; must be owner or limited owner
• putUpdateAsset — Allowed user roles:
  
  • sdzUser
  
  
  update elements of the asset by SDO id
• deleteSDO — Allowed user roles:
  
  • sdzUser
  
  
  get smart data object by sdo id; must be owner or limited owner
• putUpsertBlob — Allowed user roles:
  
  • sdzUser
  
  
  Upsert a blob, only works with scalar
• postBlob — Allowed user roles:
  
  • sdzUser
  
  
  adds a blob to an SDO by ID and its attribute
• deleteBlob — Allowed user roles:
  
  • sdzUser
  
  
  deletes a blob(s) from an SDO by attribute name
• getBlob — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  get blob data for an SDO specifically for an attribute and its hash
• putBlob — Allowed user roles:
  
  • sdzUser
  
  
  Replace a specific blob on an SDO by its ID, attribute, and hash of the blob to replace
• deleteBlobByHash — Allowed user roles:
  
  • sdzUser
  
  
  deletes a blob(s) from an SDO by attribute name and blob hash
• putVerificationInSDO — Allowed user roles:
  
  • sdzUser
  
  
  add verification data into the SDO; must be owner or limited owner
• putTransferSDO — Allowed user roles:
  
  • sdzUser
  
  
  transfer a smart data object by sdo id; must be owner or limited owner
• putRevertSDO — Allowed user roles:
  
  • sdzUser
  
  
  Revert an SDO by sdo id to the previous SDO. To revert an sdo, the following must be true:
• putUpdateSmartContract — Allowed user roles:
  
  • sdzUser
  
  
  update a smart contract
• putUpdateConsentContract — Allowed user roles:
  
  • sdzAdmin
  • sdzUser
  
  
  update a consent contract
• putUpsertBulkAssets — Allowed user roles:
  
  • sdzUser
  
  
  bulk upsert assets by primary key (order may not be followed); takes an array of [{data:{}, me
• putUpsertEdge — Allowed user roles:
  
  • sdzUser
  
  
  upsert an edge between 2 SDOs; must be owner or limited owner
• getQueryUserGroups — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query user groups from the secure data zone
• postCreateUserGroup — Allowed user roles:
  
  • sdzAdmin
  • sdzGovernance
  
  
  create a User group into the secure data zone
• getQueryUserWallets — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query user wallets from the secure data zone
• postUserWallet — Allowed user roles:
  
  • sdzAdmin
  
  
  Insert user's wallet into the secure data zone
• getTerms — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query terms from a SDZ
• postTerms — Allowed user roles:
  
  • sdzAdmin
  
  
  Create a sdz specific terms record
• getQuerySystemWallets — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query system wallets from the secure data zone
• postCreateSystemWallet — Allowed user roles:
  
  • sdzAdmin
  • sdzGovernance
  
  
  create a system's wallet into the secure data zone
• postGlossaryFile — Allowed user roles:
  
  • sdzAdmin
  
  
  loads a file of glossary items; field names in file must match Glossary structure; any field
• getQueryEdges — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query edges from the secure data zone
• postCreateEdge — Allowed user roles:
  
  • sdzAdmin
  
  
  post (insert) the edges into the secure data zone
• postPredictDict — Allowed user roles:
  
  • sdzAdmin
  
  
  uses a data file to predict a dictionary definition (uses Nostradamus
• getPipelines — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query data pipelines from the secure data zone
• postPipeline — Allowed user roles:
  
  • sdzAdmin
  
  
  Create a data pipeline in the secure data zone.
• postDataPipelineTrialRun — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  using datapipeline id, looks up the steps and executes a
• getQueryJSTransformSteps — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get JSTransformSteps by query
• postJSTransformStep — Allowed user roles:
  
  • sdzAdmin
  
  
  Create a new JsTransformStep
• postJsTransformStepTrialRun — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  using step id, looks up the step and executes a single st
• getQueryRuleSetSteps — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get RuleSetStep by query
• postStep — Allowed user roles:
  
  • sdzAdmin
  
  
  Create a new RuleSetStep
• postRuleSetStepTrialRun — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  using step id, looks up the step and executes a single st
• queryFieldMappingSteps — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get FieldMappingSteps by query
• postFieldMappingStep — Allowed user roles:
  
  • sdzAdmin
  
  
  Create a new FieldMappingStep
• postFieldMappingStepTrialRun — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  using step id, looks up the step and executes a single st
• getQueryRules — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Get Rules by query
• postRule — Allowed user roles:
  
  • sdzAdmin
  
  
  Create a new Rule
• postUploadFile — Allowed user roles:
  
  • sdzUser
  
  
  adds data from a file as assets into GraphChain as an async job
• postTruncateChain — Allowed user roles:
  
  • sdzAdmin
  
  
  truncate all data in a graph chain in the secure data zone; preserves chain, dictionary, edge
• postExecuteSmartContract — Allowed user roles:
  
  • sdzUser
  
  
  execute a smart contract, by address (sdo id) with arguments as named fields in the form; as a
• postExportFile — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  Exports data from a single chain and produces a JSON file, caller can requ
• postDropChain — Allowed user roles:
  
  • sdzAdmin
  
  
  drops chain, all data, and all edges to/from this chain
• postWipeSDZ — Allowed user roles:
  
  • sdzAdmin
  
  
  wipe all data, job infos, and blobs from the SDZ (NOT metadata)
• postResetSDZ — Allowed user roles:
  
  • sdzAdmin
  
  
  reset (wipe) all data and metadata; essentially reset the SDZ to look like its newly created
• postDownloadFile — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  queries data and produces a file; can be SFTP'ed or for downloaded as an a
• postDictionaryFile — Allowed user roles:
  
  • sdzAdmin
  
  
  load (upsert) a dictionary into the SDZ using 1) POST with JSON body with dictionary and emai
• postDbSchemaFile — Allowed user roles:
  
  • sdzAdmin
  
  
  loads a dbschema (.dbs) XML file into the secure data zone; if delete is true any dictionarie
• postCreateEdge_1 — Allowed user roles:
  
  • sdzUser
  
  
  create an edge between 2 SDOs; must be owner or limited owner; could return 200 empty response
• postCreateSmartContract — Allowed user roles:
  
  • sdzUser
  
  
  create a smart contract; request body must be
• postCreateConsentContract — Allowed user roles:
  
  • sdzAdmin
  • sdzUser
  
  
  create a consent contract
• postQuery — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  DEPRECATED Content-Type=application/json (09 MAY 24): Use ContentType=text
• postValidate — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  DEPRECATED Content-Type=application/json (09 MAY 24): Use ContentType=text
• postValidateGraph — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  DEPRECATED (use /query/validate): validate a given query for syntax, must
• postDevConversation — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  request conversational response to user's prompt; where t
• postCorpConversation — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  request conversational response to user's prompt; where t
• patchAssetWithPkFields — Allowed user roles:
  
  • sdzUser
  
  
  patch specific elements of the asset by primary key (using pkFields and pkPatchFields. NOTE:
• getProcess — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  OData v4 API
• getProcess_1 — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  OData v4 API
• getProcessBasic — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  OData v4 API for non-complex data
• getProcessBasic_1 — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  OData v4 API for non-complex data
• getSDZMetrics — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  full set of sdz metrics
• getQueryWallets — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query user OR system wallets from the secure data zone
• getHistory — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a userGroup
• getSearch — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms
• getUserGroupByName — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get the user group in the secure data zone
• getHistory_1 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a userWallet
• getUserWalletForLoggedInUser — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get the logged in user's wallet in the secure data zone
• getSearch_1 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for wallet, search terms applied to email only
• getUserWalletByEmail — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get user wallet from email
• getHistory_2 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a terms
• getSearch_2 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Search for terms record within a specific SDZ
• getHistory_3 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a systemWallet
• getUserMemberSystemWallets — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query system wallets from the secure data zone the the us
• getSearch_3 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms
• getSearchMetadata — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms across all the metadata; any of the term
• getHistory_4 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a glossary
• getSearch_4 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms
• exportGlossary — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Export glossaries as JSON
• getExport — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  exports metadata as XLSX file
• getHistory_5 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of an edge definition
• getEdge — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get an edge. based on from dictionary, to dictionary and
• getSearch_5 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms
• getDict — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets a dictionary by name from the secure data zone
• deleteDict — Allowed user roles:
  
  • sdzAdmin
  
  
  DEPRECATED: Use drop job instead. | BEWARE: Deletes a dictionary by name from the secure data
• getHistory_6 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a dictionary
• getSearch_6 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms
• getQueryDictsReferencable — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query dictionaries from the secure data zone that can be
• getHistory_7 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a dataPipeline
• getStepSummaries — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get step summary info for all steps in the secure data zo
• getHistory_8 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a jSTransformStep
• getHistory_9 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a ruleSetStep
• getHistory_10 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a fieldMappingStep
• getSearch_7 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  search for terms
• getHistory_11 — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  gets the history of a rule
• getQueryJobInfo — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Deprecated. Replace with combination of /api/jobs/query/s
• getJobInfo — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get job info for a specific job id
• deleteCancelJob — Allowed user roles:
  
  • sdzAdmin
  • sdzUser
  
  
  cancel a pending job
• getQueryJobInfoSummaries — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Query for a summary of job infos (See JobInfoSummary sche
• getDownloadFile — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  after the download job is completed, get the file (if not
• getEdgeById_1 — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  gets an edge with a from chain and edge ID
• getEdges — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  gets all outbound edges with a from SDO; must be owner or limited owner
• getVerifySignature — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  verify signature of smart data object by sdo id or hash
• getVerifyHash — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  verify hash of smart data object by sdo id or hash
• getSDOHistory — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  get smart data object history by sdo id; must be owner or limited owner
• getBlobInfo — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  get blob(s) info for an SDO; optionally can specify a blob attribute for f
• getQuerySmartContractReceipts — Allowed user roles:
  
  • sdzAdmin
  
  
  gets smart contract receipts, by where clause, orderBy clause, and limit/skip. these are opt
• getQuerySmartContractReceiptsSelf — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  gets smart contract receipts, by where clause, orderBy clause, and limit/s
• getQuerySmartContracts — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  query smart contracts by tql
• getQueryConsentContracts — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  query consent contracts by simple tql
• getQueryConsentContractReceipts — Allowed user roles:
  
  • sdzAdmin
  
  
  gets consent contract receipts, by where clause, orderBy clause, and limit/skip. these are o
• getQueryConsentContractReceiptsSelf — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  gets consent contract receipts, by where clause, orderBy clause, and limit
• getShortestPath — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  Finds the shortest path (0..1) or shortest paths (0..*) b
• getCheckSDZHealth — Requires:
  
  • Authenticated Token/JWT
  
  
  TBD
• getEdge_1 — Allowed user roles:
  
  • sdzReadOnly
  • sdzUser
  
  
  gets an edge between 2 SDOs; must be owner or limited owner
• deleteEdge — Allowed user roles:
  
  • sdzUser
  
  
  deletes an edge with all 5 identifiers; must be owner or limited owner
• getCustomer — Allowed user roles:
  
  • biqAdmin
  • customerOwner
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get the customer b
• getCustomerSDZNames — Requires:
  
  • Authenticated Token/JWT
  
  
  DEPRECATED: Use /{customerShortName}/available_sdzs instead. | Get secure data zones by
• getCustomerSDZsWithRealm — Requires:
  
  • Authenticated Token/JWT
  
  
  get secure data zones by based on customer short name
• getExportDbSchemaXml — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  export the SDZ metadata (dictionaries and edge defs) as D
• getConversationHistory — Allowed user roles:
  
  • sdzAdmin
  • sdzReadOnly
  • sdzUser
  
  
  get conversation history
• deleteEdgeById_1 — Allowed user roles:
  
  • sdzUser
  
  
  deletes an edge based on from chain and provided edge ID. Must be owner or limited owner