gh-k-dense-ai-claude-scientific-skills-scientific-skills/skills/labarchive-integration/references/api_reference.md

LabArchives API Reference

API Structure

All LabArchives API calls follow this URL pattern:

https://<base_url>/api/<api_class>/<api_method>?<authentication_parameters>&<method_parameters>

Regional API Endpoints

Region	Base URL
US/International	https://api.labarchives.com/api
Australia	https://auapi.labarchives.com/api
UK	https://ukapi.labarchives.com/api

Authentication

All API calls require authentication parameters:

• access_key_id: Provided by LabArchives administrator
• access_password: Provided by LabArchives administrator
• Additional user-specific credentials may be required for certain operations

API Classes and Methods

Users API Class

users/user_access_info

Retrieve user ID and notebook access information.

Parameters:

• login_or_email (required): User's email address or login username
• password (required): User's external applications password (not regular login password)

Returns: XML or JSON response containing:

• User ID (uid)
• List of accessible notebooks with IDs (nbid)
• Account status and permissions

Example:

params = {
    'login_or_email': 'researcher@university.edu',
    'password': 'external_app_password'
}
response = client.make_call('users', 'user_access_info', params=params)

users/user_info_via_id

Retrieve detailed user information by user ID.

Parameters:

• uid (required): User ID obtained from user_access_info

Returns: User profile information including:

• Name and email
• Account creation date
• Institution affiliation
• Role and permissions
• Storage quota and usage

Example:

params = {'uid': '12345'}
response = client.make_call('users', 'user_info_via_id', params=params)

Notebooks API Class

notebooks/notebook_backup

Download complete notebook data including entries, attachments, and metadata.

Parameters:

• uid (required): User ID
• nbid (required): Notebook ID
• json (optional, default: false): Return data in JSON format instead of XML
• no_attachments (optional, default: false): Exclude attachments from backup

Returns:

• When no_attachments=false: 7z compressed archive containing all notebook data
• When no_attachments=true: XML or JSON structured data with entry content

File format: The returned archive includes:

• Entry text content in HTML format
• File attachments in original formats
• Metadata XML files with timestamps, authors, and version history
• Comment threads and annotations

Example:

# Full backup with attachments
params = {
    'uid': '12345',
    'nbid': '67890',
    'json': 'false',
    'no_attachments': 'false'
}
response = client.make_call('notebooks', 'notebook_backup', params=params)

# Write to file
with open('notebook_backup.7z', 'wb') as f:
    f.write(response.content)

# Metadata only backup (JSON format, no attachments)
params = {
    'uid': '12345',
    'nbid': '67890',
    'json': 'true',
    'no_attachments': 'true'
}
response = client.make_call('notebooks', 'notebook_backup', params=params)
import json
notebook_data = json.loads(response.content)

notebooks/list_notebooks

Retrieve all notebooks accessible to a user (method name may vary by API version).

Parameters:

• uid (required): User ID

Returns: List of notebooks with:

• Notebook ID (nbid)
• Notebook name
• Creation and modification dates
• Access level (owner, editor, viewer)
• Member count

Entries API Class

entries/create_entry

Create a new entry in a notebook.

Parameters:

• uid (required): User ID
• nbid (required): Notebook ID
• title (required): Entry title
• content (optional): HTML-formatted entry content
• date (optional): Entry date (defaults to current date)

Returns: Entry ID and creation confirmation

Example:

params = {
    'uid': '12345',
    'nbid': '67890',
    'title': 'Experiment 2025-10-20',
    'content': '<p>Conducted PCR amplification of target gene...</p>',
    'date': '2025-10-20'
}
response = client.make_call('entries', 'create_entry', params=params)

entries/create_comment

Add a comment to an existing entry.

Parameters:

• uid (required): User ID
• nbid (required): Notebook ID
• entry_id (required): Target entry ID
• comment (required): Comment text (HTML supported)

Returns: Comment ID and timestamp

entries/create_part

Add a component/part to an entry (e.g., text section, table, image).

Parameters:

• uid (required): User ID
• nbid (required): Notebook ID
• entry_id (required): Target entry ID
• part_type (required): Type of part (text, table, image, etc.)
• content (required): Part content in appropriate format

Returns: Part ID and creation confirmation

entries/upload_attachment

Upload a file attachment to an entry.

Parameters:

• uid (required): User ID
• nbid (required): Notebook ID
• entry_id (required): Target entry ID
• file (required): File data (multipart/form-data)
• filename (required): Original filename

Returns: Attachment ID and upload confirmation

Example using requests library:

import requests

url = f'{api_url}/entries/upload_attachment'
files = {'file': open('/path/to/data.csv', 'rb')}
params = {
    'uid': '12345',
    'nbid': '67890',
    'entry_id': '11111',
    'filename': 'data.csv',
    'access_key_id': access_key_id,
    'access_password': access_password
}
response = requests.post(url, files=files, data=params)

Site Reports API Class

Enterprise-only features for institutional reporting and analytics.

site_reports/detailed_usage_report

Generate comprehensive usage statistics for the institution.

Parameters:

• start_date (required): Report start date (YYYY-MM-DD)
• end_date (required): Report end date (YYYY-MM-DD)
• format (optional): Output format (csv, json, xml)

Returns: Usage metrics including:

• User login frequency
• Entry creation counts
• Storage utilization
• Collaboration statistics
• Time-based activity patterns

site_reports/detailed_notebook_report

Generate detailed report on all notebooks in the institution.

Parameters:

• include_settings (optional, default: false): Include notebook settings
• include_members (optional, default: false): Include member lists

Returns: Notebook inventory with:

• Notebook names and IDs
• Owner information
• Creation and last modified dates
• Member count and access levels
• Storage size
• Settings (if requested)

site_reports/pdf_offline_generation_report

Track PDF exports for compliance and auditing purposes.

Parameters:

• start_date (required): Report start date
• end_date (required): Report end date

Returns: Export activity log with:

• User who generated PDF
• Notebook and entry exported
• Export timestamp
• IP address

Utilities API Class

utilities/institutional_login_urls

Retrieve institutional login URLs for SSO integration.

Parameters: None required (uses access key authentication)

Returns: List of institutional login endpoints

Response Formats

XML Response Example

<?xml version="1.0" encoding="UTF-8"?>
<response>
    <uid>12345</uid>
    <email>researcher@university.edu</email>
    <notebooks>
        <notebook>
            <nbid>67890</nbid>
            <name>Lab Notebook 2025</name>
            <role>owner</role>
        </notebook>
    </notebooks>
</response>

JSON Response Example

{
    "uid": "12345",
    "email": "researcher@university.edu",
    "notebooks": [
        {
            "nbid": "67890",
            "name": "Lab Notebook 2025",
            "role": "owner"
        }
    ]
}

Error Codes

Code	Message	Meaning	Solution
401	Unauthorized	Invalid credentials	Verify access_key_id and access_password
403	Forbidden	Insufficient permissions	Check user role and notebook access
404	Not Found	Resource doesn't exist	Verify uid, nbid, or entry_id are correct
429	Too Many Requests	Rate limit exceeded	Implement exponential backoff
500	Internal Server Error	Server-side issue	Retry request or contact support

Rate Limiting

LabArchives implements rate limiting to ensure service stability:

• Recommended: Maximum 60 requests per minute per API key
• Burst allowance: Short bursts up to 100 requests may be tolerated
• Best practice: Implement 1-2 second delays between requests for batch operations

API Versioning

LabArchives API is backward compatible. New methods are added without breaking existing implementations. Monitor LabArchives announcements for new capabilities.

Support and Documentation

For API access requests, technical questions, or feature requests:

• Email: support@labarchives.com
• Include your institution name and specific use case for faster assistance