Read/write ELN entries and registered entities via the Benchling REST API
domain: benchling.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate a personal API key from Benchling user Profile Settings, or an App client ID/secret for OAuth Bearer auth
Authenticate with HTTP Basic auth using the API key as username and an empty password against your tenant subdomain, e.g. https://<tenant>.benchling.com/api/v2/...
Call GET /api/v2/dna-sequences, /api/v2/entries, or /api/v2/custom-entities to list ELN/registry data, filterable by projectId, registryId, or schemaId
Resolve IDs first via GET /api/v2/projects and GET /api/v2/registries before filtering entity list calls
Register new entities into the registry per Benchling's documented Registering Entities workflow
Use the returning query parameter (comma-separated field paths or a wildcard) to shape bulk listing responses
Known gotchas
API keys are scoped to one Benchling tenant subdomain — they don't work against a different tenant
Bulk listing endpoints are paginated by default
Enterprise customers must call their company subdomain for both auth and API requests, not the base benchling.com domain
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?