RWTH Aachen University GraphMetadataContent API

Controller responsible for accessing and managing RDF metadata content associated with specific graph nodes of a project resource.

Operations 3

GET /api/v2/projects/{projectId}/resources/{resourceId}/graphs/{encodedPath}/metadata/content Retrieves the raw RDF content of a specific metadata graph version for the given resource and path. #
PUT /api/v2/projects/{projectId}/resources/{resourceId}/graphs/{encodedPath}/metadata/content Creates a new metadata graph version for a given resource and graph path. Accepts RDF content as the request body. #
OPTIONS /api/v2/projects/{projectId}/resources/{resourceId}/graphs/{encodedPath}/metadata/content Responds with the HTTP methods allowed for the endpoint.

Documentation

Specifications

Schemas & Data

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/rwth-aachen-university-graphmetadatacontent-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

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 Specification

rwth-aachen-university-graphmetadatacontent-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Coscine Web Admin Graph Metadata Content API
  description: Coscine (short for <b>CO</b>llaborative <b>SC</b>ientific <b>IN</b>tegration <b>E</b>nvironment) is the research data management platform for your research project.
  termsOfService: https://about.coscine.de/en/termsofuse/
  contact:
    name: Coscine Team
    email: servicedesk@rwth-aachen.de
  version: '2.0'
servers:
- url: https://coscine.rwth-aachen.de/coscine
security:
- Bearer: []
tags:
- name: GraphMetadataContent
  description: 'Controller responsible for accessing and managing RDF metadata content

    associated with specific graph nodes of a project resource.'
paths:
  /api/v2/projects/{projectId}/resources/{resourceId}/graphs/{encodedPath}/metadata/content:
    get:
      tags:
      - GraphMetadataContent
      summary: 'Retrieves the raw RDF content of a specific metadata graph version

        for the given resource and path.'
      operationId: GetMetadataContent
      parameters:
      - name: projectId
        in: path
        description: The unique identifier of the project. Supplied as a route parameter.
        required: true
        schema:
          type: string
      - name: resourceId
        in: path
        description: The unique identifier of the resource. Supplied as a route parameter.
        required: true
        schema:
          type: string
          format: uuid
      - name: encodedPath
        in: path
        description: The URL-encoded path representing the location of the graph node.
        required: true
        schema:
          type: string
      - name: graphVersion
        in: query
        description: The version identifier of the metadata graph to retrieve.
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved the RDF content stream.
          content:
            text/turtle:
              schema:
                type: string
            application/ld+json:
              schema:
                type: string
        '404':
          description: The specified metadata version or path was not found.
        '400':
          description: Invalid route or query parameters supplied.
        '401':
          description: The user is not authorized to access the resource.
    put:
      tags:
      - GraphMetadataContent
      summary: 'Creates a new metadata graph version for a given resource and graph path.

        Accepts RDF content as the request body.'
      operationId: CreateMetadataVersion
      parameters:
      - name: projectId
        in: path
        description: The unique identifier of the project. Supplied as a route parameter.
        required: true
        schema:
          type: string
      - name: resourceId
        in: path
        description: The unique identifier of the resource. Supplied as a route parameter.
        required: true
        schema:
          type: string
          format: uuid
      - name: encodedPath
        in: path
        description: The URL-encoded path representing the location of the graph node.
        required: true
        schema:
          type: string
      requestBody:
        content:
          application/ld+json:
            schema:
              type: string
              description: JSON-LD payload
          text/turtle:
            schema:
              type: string
              description: Turtle (TTL) RDF payload
        required: true
      responses:
        '200':
          description: OK
        '201':
          description: The metadata version was successfully created.
        '400':
          description: Invalid or malformed RDF content was supplied.
        '401':
          description: The user is not authorized to modify the resource.
        '415':
          description: The provided content type is unsupported.
    options:
      tags:
      - GraphMetadataContent
      summary: Responds with the HTTP methods allowed for the endpoint.
      parameters:
      - name: projectId
        in: path
        required: true
        schema:
          type: string
      - name: resourceId
        in: path
        required: true
        schema:
          type: string
      - name: encodedPath
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK
components:
  securitySchemes:
    Bearer:
      type: apiKey
      description: JWT Authorization header using the Bearer scheme.
      name: Authorization
      in: header