Generated from the official OpenAPI specification (Stardog HTTP API v12.0.3). This is the full endpoint reference the agent answers from; the interactive spec lives at https://stardog-union.github.io/http-docs/.
Server aliveness check
Determine whether the server is running
Responses:
200: Server is runningCreate cache
Create a new cached dataset from a virtual graph
Request body: application/json
Responses:
200: Operation successfulGet cached graphs
Responses:
200: Operation successfulRefresh cache
Parameters:
name (path) (required): The name of the cacheResponses:
200: Operation successfulGet cache status
Retrieve the status of one or more cached graphs or queries
Request body: application/json
Responses:
200: Operation successfulList cache targets
Responses:
200: List of cache targetsAdd cache target
Request body: application/json
Responses:
201: Cache target addedRemove cache target
Remove a cache target and destroy its contents
Parameters:
name (path) (required): The name of the targetResponses:
200: Target removedOrphan cache target
Orphan a cache target but do not destroy the contents
Parameters:
name (path) (required): The name of the targetResponses:
200: Target orphanedDrop cache
Parameters:
name (path) (required): The name of the cacheResponses:
200: Cache droppedGet credentials list
Returns a list of stored credentials
Responses:
200: Operation successfulStores username and password data
Stores username and password data and returns an associated access key
Request body: application/json
Responses:
201: Access keyRemove credentials from catalog
Removes the credentials for the specified key
Parameters:
key (path) (required): The credential keyResponses:
204: Credential successfully removedValidates cron string
Checks if the string is a valid Quartz cron schedule. Returns true if valid and false if it is not valid.
Responses:
200: Validation ResultReturns the next scheduled date
Returns the next date the cron schedule would fire a job.
Responses:
200: Next DateProvides a cron summary
Returns a text explanation of the cron string.
Responses:
200: Cron SummaryRuns the specified job
Triggers the scheduled job to run immediately
Request body: application/json
Responses:
204: Job SubmittedReloads metadata from a provider
Drops and reloads the metadata for the specified provider
Request body: application/json
Responses:
204: Virtual graph importedDrops and reloads the built-in model for the catalog
Drops and reloads the built-in model for the catalog
Responses:
200: Model reloadedKnowledge Catalog status
Returns status information about the catalog, metadata providers and scheduled jobs
Responses:
200: Knowledge Catalog status dataList checkpoints
Parameters:
db (None):Responses:
200:404: Database does not existCreate checkpoint
Parameters:
db (None):Responses:
200:400:404: Database does not existRestore checkpoints
Parameters:
db (None):checkpoint (path) (required): the name of the checkpointResponses:
200:400:404: Database does not existGet cluster info
Responses:
200: Operation successful404: Not part of a clusterCoordinator check
Determine if a specific cluster node is the cluster coordinator
Responses:
200: Node is coordinator503: Node is not coordinatorGet cluster diagnostics report
Responses:
200: Cluster diagnostics report zip createdStop read only mode
Responses:
200: Read only mode stoppedStart read only mode
Responses:
200: Read only mode startedRead replica check
Determine if a specific standby node is read replica
Responses:
200: Node is read replica400: Node is not a read replicaRepair ZK transaction IDs if they don't match all Stardog nodes. All Stardog nodes must agree.
Responses:
200: ZooKeeper repairedAttempt to sync a standby or read replica node with the cluster
Responses:
200: A sync attempt for a standby or read replica node has been initiatedGet standby pause status
Get the pause status of a standby node
Responses:
200: Operation successful400: Node is not a standby nodePause/Unpause standby node
Parameters:
pause (query) (required):Responses:
200: Pause/Unpause requested400: Node is not a standby nodeList standby nodes
Responses:
200: Operation successfulRevoke standby access
Instruct a standby node to leave its cluster
Parameters:
standbyid (None):Responses:
200: Node has been instructed to leave400: Node is not a standby nodeGet standby node status
Responses:
200: Operation successfulGet cluster status
Responses:
200: Operation successfulGet all metadata properties
Get information on all database metadata properties, including description and example values
Responses:
200: JSON object detailing all metadata optionsList data sources
Responses:
200: Operation successfulAdd data source
Request body:
Responses:
201: Data source createdDescribe the supported data source types and their options.
Responses:
200: Operation successfulList data sources' info
Responses:
200: Operation successfulTest the connection for a new data source
Request body:
Responses:
204: Data source test successful404:503: Data source test failedDelete data source
Parameters:
None (None):Responses:
204: Data source deleted404:Update data source
Parameters:
None (None):Request body:
Responses:
201: Virtual graph updatedAvailable
Returns whether or not the data source is available
Parameters:
None (None):Responses:
200: Operation successful404:Get data source info
Parameters:
None (None):Responses:
200: Operation successful404:Online data source
Parameters:
None (None):Responses:
204: Data source onlined404:Get data source options
Parameters:
None (None):Responses:
200: Operation successful404:Query data source
Parameters:
None (None):Request body:
Responses:
200: Query executedRefresh table row-count estimates
Parameters:
None (None):Request body:
Responses:
204: Data source counts refreshed404:Refresh metadata
Parameters:
None (None):Request body:
Responses:
204: Data source metadata refreshed404:Share data source
Parameters:
None (None):Responses:
204: Data source shared404:Test an existing data source connection
Parameters:
None (None):Responses:
204: Data source test successful404:503: Data source test failedList databases
List all the databases in the server
Responses:
200: Operation successfulCreate database
Add a new database to the server, optionally with RDF bulk-loaded
Request body: multipart/form-data
Responses:
201: Database created400: Invalid or malformed request bodyBackup all databases
Create a backup of all databases on the server
Parameters:
to (query): File location on the server to which to save the backups (defaults to $STARDOG_HOME/.backup)Responses:
200:Return all databases along with their configuration options
List all the databases in the server including all database configuration options
Responses:
200: Operation successfulDrop database
Delete the database
Parameters:
db (None):Responses:
200:404: Database does not existBackup a database
Create a backup of a database on the server
Parameters:
db (None):to (query): File location on the server to which to save the backup (defaults to $STARDOG_HOME/.backup)Responses:
200:404: Database does not existOffline database
Take a database offline
Parameters:
db (None):Request body:
Responses:
200:400:404: Database does not existOnline database
Bring a database online
Parameters:
db (None):Request body:
Responses:
200:404: Database does not existOptimize database
Optimize a database
Parameters:
db (None):Request body: application/json
Responses:
200:400:404: Database does not existGet all DB options
Get the value of every metadata option for a database
Parameters:
db (None):Responses:
200: JSON object detailing all database metadata404: Database does not existSet DB options
Set the value of specific metadata options for a database
Parameters:
db (None):Request body: application/json
Responses:
200:404: Database does not existGet DB options
Get the value of specific metadata options for a database
Parameters:
db (None):Request body: application/json
Responses:
200: Operation successful404: Database does not existRename database
Make existing database to be identified by a new name
Parameters:
db (None):Request body: text/plain
Responses:
200:404: Database does not existRepair database
Attempt to recover a corrupted database
Parameters:
db (None):Responses:
200:404: Database does not existReturn transaction Log
Return a chunk (or the entirety) of this database's transaction log for point in time recovers.
Parameters:
db (None):Responses:
200: Transaction Log404: Database does not existReplay Transaction Log
Replay a transaction log onto an existing database. This operation applies the provided transaction log to the database, typically for point in time restore.
Parameters:
db (None):validate (path) (required): Server should validate the transaction log before applying it. Checks if the last committed transaction is at the beginning of the Log. Default is trueRequest body: application/octet-stream
Responses:
200:404: Database does not existVerify database
Checks that the data in the database is not corrupted, for example, there're no inconsistencies across indexes
Parameters:
db (None):Responses:
200:404: Database does not existGet server diagnostics report
Responses:
200: Server diagnostics report zip createdDelete Stored Functions
Delete all stored functions on the server, or optionally just the function specified in the query string parameter
Parameters:
name (query): Stored Function nameResponses:
204: Function deleted400: Function does not exist404:Get Stored Functions
Retrieve all stored functions on the server, or optionally just the function specified in the query string parameter
Parameters:
name (query): Stored Function nameResponses:
200: Operation successful400: Function does not exist404:Add Stored Function
Request body: text/plain
Responses:
204: Function added422: Function with the given name existsDelete Stored Function
Delete the stored function specified in the query string parameter
Parameters:
None (None):Responses:
204: Function deleted400: Function does not exist404:Get Stored Function
Parameters:
None (None):Responses:
200: Operation successful400: Function does not exist404:Server health check
Determine whether the server is running and able to accept traffic
Responses:
200: Server is running and healthy503: Server is unavailableGet server logs
Retrieve server logs as a zip file. Supports filtering by log types, including rotated logs, and limiting the number of lines returned.
Request body: application/json
Responses:
200: Server logs zip returnedCheck User Permission
Check if the currently authenticated user has permission to perform an action on a resource, taking wildcards into account
Responses:
200: Permission check result400:Get effective user permissions
Get all permissions assigned to a given user as well as those granted by assigned roles
Parameters:
user (None):Responses:
200:404: User does not existGet role permissions
Get all permissions attributed to a given role
Parameters:
role (None):Responses:
200:404: Role does not existAdd Role Permission
Add a permission to a specified role
Parameters:
role (None):Request body:
Responses:
201: Permission added400:404: Role does not existDelete Role Permission
Remove a permission from a given role
Parameters:
role (None):Request body:
Responses:
201: Permission removed400:404: Role does not existGet user permissions
Get all permissions assigned to a given user
Parameters:
user (None):Responses:
200:404: User does not existAdd User Permission
Grant a permission directly to a specified user
Parameters:
user (None):Request body:
Responses:
201: Permission added400:404: User does not existDelete User Permission
Revoke a permission from a given user
Parameters:
user (None):Request body:
Responses:
201: Permission removed400:404: User does not existList processes
Get a list of all running processes
Parameters:
all (query): Whether to include all processes in cloudResponses:
200:Kill process
Parameters:
None (None):Responses:
204: Process killed404:Get process
Get details of a specific process
Parameters:
None (None):Responses:
200:404:Get server properties
Gets the property value for a server configuration option. This value will be the default for the option or the override in the properties file.
Parameters:
name (query): Specific names of server properties to retrieve (multiple params can be specified)Responses:
200: JSON object detailing all server propertiesSet server properties
Set the value of specific server properties
Request body: application/json
Responses:
200:List queries
Get a list of all running queries
Responses:
200:Delete all stored queries
Responses:
204: All stored queries deletedList stored queries
Parameters:
None (None):Responses:
200:Add stored query
Parameters:
None (None):Request body:
Responses:
204: Stored query added400:422: Stored query already existsUpdate stored query
Add stored query, overwriting if a query with that name already exists
Request body:
Responses:
204: Stored query updated400:Delete stored query
Parameters:
None (None):Responses:
204: Query deleted404:Get stored query
Parameters:
None (None):Responses:
200:404:Rename stored query
Parameters:
None (None):move (query):Request body: application/json
Responses:
204: Query renamed404:Kill query
Parameters:
None (None):Responses:
204: Query killed404:Get query
Get details of a specific query
Parameters:
None (None):plan (query):verbose (query):Responses:
200:404:Restore database
Restore a database from backup
Parameters:
from (query) (required): The location on the server of the backupforce (query): Whether or not to overwrite an existing database with this backupname (query): The name of the restored database, if differentResponses:
200:List Roles
Get the names of all roles in the system
Responses:
200:Add role
Request body:
Responses:
201: Role added400:List Roles with their permissions
Retrieve a detailed list of all roles, including their permissions
Responses:
200:Delete role
Parameters:
role (None):force (query): Whether to force delete if role is assigned to usersResponses:
204: Role deleted404: Role does not existGet users with role
Returns a list of all users that have a specific role
Parameters:
role (None):Responses:
200:404: Role does not existGet SDU usage events (streaming)
Retrieve SDU (Stardog Data Unit) usage events from the sdu_usage.log file. Events are streamed to avoid memory issues under heavy load. Optionally filter by start and end timestamps in ISO-8601 format (e.g., 2023-12-18T12:00:00Z).
Responses:
200: SDU usage events returned as streamed JSON array401: Not authorized to read logsGet SDU usage summary statistics
Retrieve aggregated summary statistics for SDU (Stardog Data Unit) usage events. Returns total queries, total elapsed time, and breakdowns by user, database, and agent. Optionally filter by start and end timestamps in ISO-8601 format (e.g., 2023-12-18T12:00:00Z).
Responses:
200: SDU usage summary returned as JSON object401: Not authorized to read logsShutdown server
Responses:
200: Shutdown request received405: Remote shutdowns not allowedShutdown all nodes
Responses:
200: Shutdown request received405: Remote shutdown not supportedGet Server/Database metrics
Return metric information from the registry in JSON format. If 'admin' is replaced in the path with a valid database name, metrics for just that database will be returned.
Responses:
200: Server/Database metricsGet Prometheus metrics
Return metric information from the registry in Prometheus format
Parameters:
include (query): Regex used to match metric names to be includedexclude (query): Regex used to match metric names to be excluded, takes precedence over includeResponses:
200: Prometheus metricsGet Prometheus metrics (only accessible from a restricted cidr range)
Return metric information from the registry in Prometheus format
Parameters:
include (query): Regex used to match metric names to be includedexclude (query): Regex used to match metric names to be excluded, takes precedence over includeResponses:
200: Prometheus metricsList users
Responses:
200:Add user
Request body: application/json
Responses:
201: User created400:List users with attributes, roles and permissions
Retrieve a detailed list of all users, including their roles, permissions, and status
Responses:
200:Delete User
Parameters:
user (None):Responses:
204: User deleted404: User does not existGet User
Retrieve attributes, roles, and permissions of a User
Parameters:
user (None):Responses:
200: Operation successful404: User does not existUser auto-created
Return whether a user was auto-created as a result the OAuth jwt authentication process
Parameters:
user (None):Responses:
200: Operation successful404: User does not existUser enabled
Return whether or not a user is enabled (active) in the system
Parameters:
user (None):Responses:
200: Operation successful404: User does not existEnable/Disable User
Parameters:
user (None):Request body: application/json
Responses:
200: Flag set400:404: User does not existChange user's password
Parameters:
user (None):Request body: application/json
Responses:
200: Password successfully changed400:404: User does not existGet user's roles
Retrieve a list of all roles explicitly assigned to a user
Parameters:
user (None):Responses:
200:404: User does not existAdd role to user
Parameters:
user (None):Request body:
Responses:
204: Role successfully added400:404: User does not existSet user's roles
Overwrite the list of roles explicitly assigned to a user
Parameters:
user (None):Request body: application/json
Responses:
200: Roles successfully updated400:404: User does not existRemove role from user
Parameters:
user (None):role (None):Responses:
204: Role successfully removed404: User/Role does not existUser is Superuser
Return whether or not a user is a Superuser
Parameters:
user (None):Responses:
200: Operation successful404: User does not existList virtual graphs
Responses:
200: Operation successfulAdd virtual graph
Request body:
Responses:
201: Virtual graph createdImport file
Import a CSV or JSON file as a virtual graph into the knowledge graph
Request body: multipart/form-data
Responses:
200: File imported successfullyImport virtual graph
Import (materialize) a virtual graph directly into the local knowledge graph
Request body: application/json
Responses:
204: Virtual graph importedList virtual graphs' info
Responses:
200: Operation successfulDelete virtual graph
Parameters:
None (None):Responses:
204: Virtual graph deleted404:Update virtual graph
Parameters:
None (None):Request body:
Responses:
201: Virtual graph updatedAvailable
Returns whether or not the virtual graph is available
Parameters:
None (None):Responses:
200: Operation successful404:Get database
Get the database associated with a virtual graph
Parameters:
None (None):Responses:
200: Operation successful404:Get virtual graph info
Parameters:
None (None):Responses:
200: Operation successful404:Get mappings
Parameters:
None (None):syntax (path) (required): The desired RDF syntax of the mappings (R2RML or SMS)Responses:
200: Virtual graph mappings as RDF404:Online virtual graph
Parameters:
None (None):Responses:
204: Virtual graph onlined404:Get virtual graph options
Parameters:
None (None):Responses:
200: Operation successful404:Import virtual graph
Import (materialize) a delimited file into the knowledge graph
Request body: application/json
Responses:
204: File importedImport virtual graph
Import (materialize) a virtual graph directly into the local knowledge graph
Request body: application/json
Responses:
204: Virtual graph importedAligns the source and target data source schemas
Responses:
200: aligned data source schemasDELETE graph
Deletes the RDF graph content identified by either the request or encoded IRI
Parameters:
db (None):graph (query): IRI of the named graph to deletedefault (query): Include instead of 'graph' to operate on the default graphResponses:
200: Graph deleted404: Database does not existGET graph
Retrieves an RDF payload that is a serialization of the named graph paired with the graph IRI in the database
Parameters:
db (None):graph (query): IRI of the named graph to retrievedefault (query): Include instead of 'graph' to operate on the default graphResponses:
200:404: Database does not existPOST graph
Merges the enclosed RDF payload with the specified graph content
Parameters:
db (None):graph (query): IRI of the target named graphdefault (query): Include instead of 'graph' to operate on the default graphRequest body:
Responses:
200: Graph merged404: Database does not existPUT graph
Stores the enclosed RDF payload as RDF graph content
Parameters:
db (None):graph (query): IRI of the target named graphdefault (query): Include instead of 'graph' to operate on the default graphNone (None):Request body:
Responses:
200: Graph overwritten201: Graph created404: Database does not existResolve entities
Parameters:
db (None):Responses:
200: Operation successful404: Database does not existResolve entities with reasoning enabled
Parameters:
db (None):None (None):None (None):Responses:
200: Operation successful404: Database does not existExplain SPARQL query
Parameters:
db (None):None (None):None (None):Responses:
200: Query plan400:404: Database does not exist501:Explain SPARQL query
Parameters:
db (None):None (None):None (None):None (None):None (None):Request body: application/sparql-query, multipart/form-data
Responses:
200: Query plan400:404: Database does not exist501:Export database
Parameters:
db (None):obf (query): Path to an obfuscation configuration file, or DEFAULTResponses:
200:404: Database does not existExport database (obfuscated)
Parameters:
db (None):Request body: text/turtle
Responses:
200:404: Database does not existPerform GraphQL query
Parameters:
db (None):query (query) (required):Responses:
200:404: Database does not existPerform GraphQL query
Parameters:
db (None):Request body: application/json
Responses:
200:404: Database does not existClear schemas
Parameters:
db (None):Responses:
204: Schemas cleared404: Database does not existList schemas
Parameters:
db (None):Responses:
200: List of schemas404: Database does not existRemove schema
Parameters:
db (None):schema (None):None (None):Responses:
204: Schema removed404: Database/Schema does not existGet schema
Parameters:
db (None):schema (None):None (None):Responses:
200: Operation successful404: Database/Schema does not existAdd schema
Parameters:
db (None):schema (None):None (None):Request body:
Responses:
201: Schema added404: Database/Schema does not existUpdate schema
Parameters:
db (None):schema (None):None (None):Request body:
Responses:
200: Schema updated404: Database/Schema does not existPerform GraphQL query with schema
Parameters:
db (None):schema (None):query (query) (required):None (None):Responses:
200:404: Database/Schema does not existPerform GraphQL query with schema
Parameters:
db (None):schema (None):None (None):Request body: application/json
Responses:
200:404: Database/Schema does not existList constraints
Parameters:
db (None):Responses:
200: Constraints in RDF format404: Database does not existSHACL validation report
Produces a SHACL validation report against the specified shape(s)
Parameters:
db (None):shapes (query): SHACL shapes to validateshacl.shape.graphs (query): SHACL shape graphs to validatenodes (query): SHACL focus node(s) to validatecountLimit (query): Maximum number of violations to reportshacl.targetClass.simple (query):shacl.violation.limit.shape (query): number of violation limits per SHACL shapesNone (None):None (None):Responses:
200:404: Database does not existValidate constraints
Determine whether or not the given constraints are valid
Parameters:
db (None):Request body:
Responses:
200:404: Database does not existSHACL validation report in transaction
Produces a SHACL validation report against the specified shape(s)
Parameters:
db (None):txid (None):shapes (query): SHACL shapes to validateshacl.shape.graphs (query): SHACL shape graphs to validatenodes (query): SHACL focus node(s) to validatecountLimit (query): Maximum number of violations to reportshacl.targetClass.simple (query):shacl.violation.limit.shape (query): number of violation limits per SHACL shapesResponses:
200:404: Database/Transaction does not existValidate constraints in transaction
Determine whether or not the given constraints are valid
Parameters:
db (None):txid (None):Request body:
Responses:
200:404: Database/Transaction does not existGenerate Model
Generate the reasoning model used by this database in various formats
Parameters:
db (None):None (None):output (query): Desired output format (text, owl, shacl, sql, graphql)Responses:
200:404: Database does not existGet namespaces
Retrieve the namespaces stored in the database
Parameters:
db (None):Responses:
200: A JSON object listing the prefixes and IRIs of the stored namespaces404: Database does not existImport namespaces
Add namespaces to the database via a block or blocks of RDF that declares them
Parameters:
db (None):Request body:
Responses:
200: A JSON object listing the prefixes and IRIs of the stored namespaces404: Database does not existPerform SPARQL query
Parameters:
db (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):Responses:
200:400:404: Database does not exist406: Accept header invalid for type of query sentPerform SPARQL query
Parameters:
db (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):Request body: application/sparql-query, multipart/form-data
Responses:
200:400:404: Database does not exist406: Accept header invalid for type of query sentPerform SPARQL query with reasoning enabled
Parameters:
db (None):None (None):Responses:
200: Query results400:404: Database does not exist406: Accept header invalid for type of query sentPerform SPARQL query with reasoning enabled
Parameters:
db (None):None (None):Request body: application/sparql-query, multipart/form-data
Responses:
200: Query results400:404: Database does not exist406: Accept header invalid for type of query sentCheck consistency
Returns whether or not the data in the database are consistent with respect to the ontology
Parameters:
db (None):Responses:
200: Operation successful404: Database does not existExplain inference
Explain how the inference engine inferred a specific piece of data
Parameters:
db (None):Request body: text/turtle, application/trig, application/rdf+xml, application/n-triples, application/n-quads, application/ld+json
Responses:
200:404: Database does not existExplain inconsistency
Explain how, if at all, the data are inconsistent with respect to the ontology
Parameters:
db (None):Responses:
200:404: Database does not existGet reasoning schema
Retrieve the reasoning schema in RDF of the given database
Parameters:
db (None):Responses:
200: Reasoning schema in RDF404: Database does not existExplain inference in transaction
Explain how the inference engine inferred a specific piece of data
Parameters:
db (None):txid (None):Request body: text/turtle, application/trig, application/rdf+xml, application/n-triples, application/n-quads, application/ld+json
Responses:
200:404: Database/Transaction does not existExplain inconsistency in transaction
Explain how, if at all, the data are inconsistent with respect to the ontology
Parameters:
db (None):txid (None):Responses:
200:404: Database/Transaction does not existGet DB Size
Retrieve the size of the db. Size is approximate unless the exact parameter is set to true
Parameters:
db (None):exact (query): Whether to request that the database size be exact instead of approximateResponses:
200: The size (in triples) of the database404: Database does not existList all open transactions on a database
Parameters:
db (None):Responses:
200: Operation successful404: Database does not existBegin a transaction
Parameters:
db (None):Responses:
200: Operation successful404: Database does not existBegin a transaction with specified txid
Parameters:
db (None):txid (None):Responses:
200: Transaction begun404: Database/Transaction does not existCommit a transaction
Parameters:
db (None):txid (None):Responses:
200: Commit successful404: Database/Transaction does not existRollback a transaction
Parameters:
db (None):txid (None):Responses:
200:404: Database/Transaction does not existPerform SPARQL Update query
Parameters:
db (None):None (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):Responses:
200: Update query succeeded400: Invalid query sent404: Database does not existPerform SPARQL Update query
Parameters:
db (None):None (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):Request body: application/sparql-update, application/x-www-form-urlencoded
Responses:
200: Update query succeeded400: Invalid query sent404: Database does not existAdd data within a transaction
Parameters:
db (None):txid (None):None (None):None (None):Request body: text/turtle, application/trig, application/rdf+xml, application/n-triples, application/n-quads, application/ld+json
Responses:
200:404: Database/Transaction does not existClear database within a transaction
Parameters:
db (None):txid (None):None (None):Responses:
200:404: Database/Transaction does not existExplain SPARQL query (within tx)
Parameters:
db (None):None (None):None (None):txid (path) (required): Transaction IDResponses:
200: Query plan400:404: Database does not exist501:Explain SPARQL query (within tx)
Parameters:
db (None):None (None):None (None):None (None):None (None):txid (path) (required): Transaction IDRequest body: application/sparql-query, multipart/form-data
Responses:
200: Query plan400:404: Database does not exist501:Perform SPARQL query (within tx)
Parameters:
db (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):txid (path) (required): Transaction IDResponses:
200:400:404: Database does not exist406: Accept header invalid for type of query sentPerform SPARQL query (within tx)
Parameters:
db (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):txid (path) (required): Transaction IDRequest body: application/sparql-query, multipart/form-data
Responses:
200:400:404: Database does not exist406: Accept header invalid for type of query sentRemove data within a transaction
Parameters:
db (None):txid (None):None (None):Request body: text/turtle, application/trig, application/rdf+xml, application/n-triples, application/n-quads, application/ld+json
Responses:
200:404: Database/Transaction does not existPerform SPARQL Update query (within tx)
Parameters:
db (None):None (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):txid (path) (required): Transaction IDResponses:
200: Update query succeeded400: Invalid query sent404: Database does not existPerform SPARQL Update query (within tx)
Parameters:
db (None):None (None):None (None):None (None):None (None):txid (query): Transaction IDNone (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):None (None):txid (path) (required): Transaction IDRequest body: application/sparql-update, application/x-www-form-urlencoded
Responses:
200: Update query succeeded400: Invalid query sent404: Database does not exist