Group multiple operations in an atomic transaction.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/eclipse-rdf4j:eclipse-rdf4j-transactions-api"curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: RDF4J REST Transactions API
version: '10'
description: 'The RDF4J REST API is an HTTP protocol that covers a fully compliant implementation of the SPARQL 1.1 Protocol W3C Recommendation. This ensures that RDF4J Server functions as a fully standard-compliant SPARQL endpoint.
The RDF4J REST API additionally supports the SPARQL 1.1 Graph Store HTTP Protocol W3C Recommendation. The RDF4J REST API extends the W3C standards in several aspects, the most important of which is database transaction management.'
servers:
- url: http://localhost:8080/rdf4j-server/
description: RDF4J Server on localhost
tags:
- name: Transactions
description: RDF4J supports a REST-styleimplementation of a transactional protocol, by means of treating the transaction itself as a new resource that can be updated with consecutive operations. A transaction is started by a POST request to the transactions endpoint, which will return a new unique endpoint location for the new transaction. Operations (such as adding data, querying, committing/rolling back the transaction) are executed by means of PUT requests of consecutive operations against that unique transaction endpoint.
externalDocs:
url: https://rdf4j.org/documentation/programming/repository/#transactions
paths:
/repositories/{repositoryID}/transactions:
post:
tags:
- Transactions
summary: Start a new transaction
description: RDF4J supports a RESTful implementation of a transactional protocol, by means of treating the transaction itself as a new resource that can be updated with consecutive operations. A transaction is started by a POST request to the transactions endpoint, which will return a new unique endpoint location for the new transaction. Operations (such as adding data, querying, committing/rolling back the transaction) are executed by means of PUT requests of consecutive operations against that unique transaction endpoint.
parameters:
- name: repositoryID
in: path
required: true
description: The repository ID
schema:
type: string
example: myDB
responses:
201:
description: Started
headers:
Location:
description: URL of the newly created transaction resource
schema:
type: string
example: /rdf4j-server/repositories/myDB/transactions/64a5937f-c112-d014-a044-f0123b93
operationId: postRepositoriesByRepositoryIDTransactions
x-operation-id-source: derived
/repositories/{repositoryID}/transactions/{transactionID}:
put:
tags:
- Transactions
summary: Execute a transaction action
description: Transaction operations are carried on this endpoint. The full URI is the exact value of the Location header as returned by the request to start a transaction.
parameters:
- name: repositoryID
in: path
required: true
description: The repository ID
schema:
type: string
- name: transactionID
in: path
required: true
description: The transaction ID
schema:
type: string
- name: action
in: query
required: true
schema:
type: string
enum:
- ADD
- DELETE
- GET
- QUERY
- UPDATE
- SIZE
- COMMIT
- PING
description: 'Specifies the type of operation being carried on the transaction.
'
- name: subj
in: query
required: false
description: GET actions only. Restricts the operation to statements with the specified N-Triples encoded resource as subject.
schema:
type: string
- name: pred
in: query
required: false
description: GET actions only. Restricts the operation to statements with the specified N-Triples encoded resource as predicate.
schema:
type: string
- name: obj
in: query
required: false
description: GET actions only. Restricts the operation to statements with the specified N-Triples encoded resource as object.
schema:
type: string
- name: query
in: query
required: false
description: QUERY actions only. Specifies the SPARQL query to evaluate.
schema:
type: string
- name: queryLn
in: query
required: false
description: QUERY actions only. Specifies the query language that is used for the query. Acceptable values are strings denoting the query languages supported by the server, i.e 'sparql' for SPARQL queries. If not specified, the server assumes the query is a SPARQL query.
schema:
type: string
- name: infer
in: query
required: false
description: GET and QUERY actions only. Specifies whether inferred statements should be included in the result. Inferred statements are included by default (if available in the repository). Specifying any value other than 'true' (ignoring case) restricts the result to explicit statements only.
schema:
type: boolean
- name: update
in: query
required: false
description: UPDATE actions only. Specifies the SPARQL 1.1 Update operation to be executed. The value is expected to be a syntactically valid SPARQL 1.1 Update string.
schema:
type: string
- name: baseURI
in: query
required: false
description: UPDATE, DELETE, and ADD actions only. Specifies a base URI to be used for executing the operation.
schema:
type: string
- name: using-graph-uri
in: query
required: false
description: UPDATE actions only. One or more named graph URIs to be used as the default graph(s) for retrieving statements.
schema:
type: boolean
- name: using-named-graph-uri
in: query
required: false
description: UPDATE actions only. One or more named graph URIs to be used as named graphs for retrieving statements.
schema:
type: boolean
- name: remove-graph-uri
in: query
required: false
description: UPDATE actions only. One or more named graph URIs to be used as the default graph(s) for removing statements.
schema:
type: boolean
- name: insert-graph-uri
in: query
required: false
description: UPDATE actions only. One or more named graph URIs to be used as the default graph(s) for inserting statements.
schema:
type: boolean
requestBody:
description: 'RDF Data payload. Only relevant for ADD actions.
'
content:
application/rdf+xml:
schema:
type: object
xml:
name: RDF
namespace: http://www.w3.org/1999/02/22-rdf-syntax-ns#
text/plain:
schema:
type: string
text/turtle:
schema:
type: string
text/rdf+n3:
schema:
type: string
text/x-nquads:
schema:
type: string
application/ld+json:
schema:
type: object
format: json
application/rdf+json:
schema:
type: object
format: json
application/trix:
schema:
type: object
xml:
name: TriX
application/x-trig:
schema:
type: string
application/x-binary-rdf:
schema:
type: string
format: binary
responses:
200:
description: OK
204:
description: No content
operationId: putRepositoriesByRepositoryIDTransactionsByTransactionID
x-operation-id-source: derived
delete:
tags:
- Transactions
summary: Abort a transaction
description: An active transaction can be aborted by means of a HTTP DELETE request on the transaction resource. This will execute a transaction rollback on the repository and will close the transaction. After executing a DELETE, further operations on the same transaction will result in an error.
parameters:
- name: repositoryID
in: path
required: true
description: The repository ID
schema:
type: string
- name: transactionID
in: path
required: true
schema:
type: string
description: The transaction ID
responses:
204:
description: Successfully aborted the defined transaction.
operationId: deleteRepositoriesByRepositoryIDTransactionsByTransactionID
x-operation-id-source: derived
externalDocs:
url: https://rdf4j.org/documentation/reference/rest-api/
x-provenance:
method: harvested
publisher: Eclipse RDF4J
source: https://rdf4j.org/documentation/reference/rest-api/rdf4j-openapi.yaml
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)