BibSonomy REST API

Name: BibSonomy REST API API
Brand: BibSonomy REST API
Availability: InStock

✓ Official Vendor SpecProductivityNote Takingbasic46 EndpointsREST

For Agents

Manage BibSonomy bookmarks, BibTeX publications, tags, concepts, groups, and document attachments for academic reference sharing.

Quickstart

Get started with BibSonomy REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a BibSonomy post"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BibSonomy REST API API.

Publish BibTeX publications and bookmarks to a BibSonomy user account

Tag publications with controlled vocabulary concepts for organised reading lists

Manage concepts (tag hierarchies) used to structure a personal library

Attach PDF documents and supplementary files to a BibSonomy post

GET STARTED

Start building with BibSonomy REST API API

Explore with Jentic

View OpenAPI Document

Use for: I need to add a BibTeX entry to my BibSonomy library, Find all posts tagged with 'machine-learning' for a specific user, Upload a PDF document to attach to a publication post, List the members of a research group on BibSonomy

Not supported: Does not handle full-text search across the academic literature, citation graphs, or DOI resolution — use for personal and group reference library management only.

BibSonomy is a social bookmarking and academic publication sharing system run by the University of Kassel and partners. The REST API gives programmatic access to users, posts (which can be either bookmarks or BibTeX publications), tags, concepts (controlled hierarchies of tags), groups, persons, and document attachments. Authentication uses HTTP Basic with the BibSonomy username and API key generated in the user settings. The 46 endpoints are organised around the user as the primary resource and let agents publish references, share reading lists, and collaborate inside research groups.

Use Cases

Patterns agents use BibSonomy REST API API for, with concrete tasks.

★ Reference Manager Sync

Sync a researcher's BibTeX library between a desktop reference manager and BibSonomy so collaborators can read and cite the shared library through the web interface. POST /users/{username}/posts publishes a publication; GET /users/{username}/posts retrieves the full library; PUT updates an entry. Document attachments under /documents/ keep PDFs alongside the metadata.

POST a new BibTeX entry to /users/researcher42/posts with title, authors, year, and an attached PDF.

Research Group Reading List

Run a shared reading list inside a BibSonomy group so every member sees newly added papers and can comment via tags. GET /groups/{groupname} returns the group profile, and posts are surfaced through the group's user-tagged publications. The clipboard endpoint helps a curator stage papers before publishing them to the group.

List the members of group 'lab-deep-learning' and surface every paper they have tagged with 'transformers' in the last 30 days.

Tag-Based Discovery Feed

Build a discovery feed that surfaces new bookmarks and publications from across BibSonomy by tag, similar to a topic tracker. Iterate user posts with a tag filter and present new items to the reader. This is useful for staying on top of an evolving research area without subscribing to individual users.

Iterate /users/{username}/posts for a curated set of users and pull every post tagged 'graph-neural-networks' added in the last week.

AI Agent Reference Curator

An AI agent helping a PhD student curate references can publish new papers to BibSonomy and tag them appropriately, reading existing posts to avoid duplicates. Through Jentic, the agent searches by intent ('add a BibTeX entry to my library'), loads the schema, and executes — Jentic supplies the basic-auth credentials so the agent never sees the username and password pair.

Search Jentic for 'create a BibSonomy post', execute POST /users/researcher42/posts, and tag the resulting entry with 'literature-review'.

Key Endpoints

46 endpoints — bibsonomy is a social bookmarking and academic publication sharing system run by the university of kassel and partners.

METHOD

PATH

DESCRIPTION

GET

/users/{username}/posts

List posts for a user

POST

/users/{username}/posts

Create a post

PUT

/users/{username}/posts/{resourceHash}

Update a post

POST

/users/{username}/posts/{resourceHash}/documents/

Add a document to a post

GET

/users/{username}/concepts

List concepts for a user

GET

/groups

List all groups

GET

/users/{username}/posts

List posts for a user

POST

/users/{username}/posts

Create a post

PUT

/users/{username}/posts/{resourceHash}

Update a post

POST

/users/{username}/posts/{resourceHash}/documents/

Add a document to a post

GET

/users/{username}/concepts

List concepts for a user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BibSonomy basic-auth credentials (username plus API key) are stored encrypted in the Jentic vault (MAXsystem). Agents call BibSonomy operations via Jentic and the Authorization header is injected at execution time — raw API keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create a BibSonomy post') and Jentic returns the matching operation with its body schema, so the agent does not need to navigate the user-scoped 46-endpoint reference to find publication posting.

Time to first call

Direct BibSonomy integration: 1-2 days for basic-auth handling, BibTeX schema, and document attachment flows. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mendeley API

Mendeley is a commercial reference manager API operated by Elsevier with broader catalogue integrations.

Choose Mendeley when integrating with the Elsevier ecosystem; choose BibSonomy for open academic bookmarking and BibTeX-first workflows.

Complementary

Crossref API

Crossref resolves DOI metadata that can be published as BibTeX entries into BibSonomy.

Use Crossref to fetch authoritative metadata for a DOI, then publish the resulting BibTeX entry to BibSonomy.

Complementary

Figshare API

Figshare hosts the underlying datasets and PDFs that can be linked from BibSonomy posts.

Pair the two when an agent uploads research outputs to Figshare and registers the citation in BibSonomy.

FAQs

Specific to using BibSonomy REST API API through Jentic.

What authentication does the BibSonomy API use?

BibSonomy uses HTTP Basic authentication with your BibSonomy username and API key (the API key is generated in user settings, separate from the web password). Through Jentic, the basic-auth pair is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time so the agent never sees the API key.

Can I publish a BibTeX entry to my BibSonomy library?

Yes. POST /users/{username}/posts accepts a publication post body that includes the BibTeX fields (title, author, year, and so on) plus tags. The response includes a resourceHash that identifies the new post for later updates or document attachments.

How do I attach a PDF to a BibSonomy post?

After creating the post, POST the file to /users/{username}/posts/{resourceHash}/documents/. The document then appears alongside the post and can be renamed via PUT or removed via DELETE on the same path with the document's filename.

How do I create a BibSonomy post through Jentic?

Search Jentic for 'create a BibSonomy post', load /users/{username}/posts (POST), and execute with the BibTeX entry body. With the SDK: pip install jentic, then SearchRequest, LoadRequest, ExecutionRequest in an async flow — Jentic injects the basic-auth credentials.

Is the BibSonomy API free?

Yes — BibSonomy is run as a free academic service by the University of Kassel and partners. Use it within fair-use rate limits, which are not declared in the OpenAPI spec but enforced server-side.