Delft University of Technology

Delft University of Technology (TU Delft) is the oldest and largest public technical university in the Netherlands and a member of the 4TU.Federation. Its programmable footprint is narrow, and this profile states that plainly rather than padding it. TU Delft operates exactly one public, unauthenticated API: the 4TU.ResearchData repository at data.4tu.nl, which runs on djehuty, open-source repository software written by 4TU.ResearchData and Nikhef. The /v2 surface is deliberately shape-compatible with the Figshare v2 API because that was a requirement of the 2023 migration OFF Figshare — the contract is not Figshare's, and the service runs inside TU Delft's own RIPE netblock (DUNET, 131.180.0.0/16). The other genuinely institution-operated machine-readable surface is a SAML 2.0 identity provider at login.tudelft.nl, published into the SURFconext national federation and onward to eduGAIN. Beyond those two, the picture is retirement and tenancy. The general-purpose institutional API platform at api.tudelft.nl — campus, buildings, courses, schedules, study results, organisation — no longer answers on port 80 or 443, and its documentation host apidoc.tudelft.nl has no DNS record at all. The research information portal at pure.tudelft.nl / research.tudelft.nl is an Elsevier Pure tenancy whose own API documentation canonicalises to api.elsevierpure.com: TU Delft's data, Elsevier's contract. The library discovery layer is an OCLC WorldCat tenancy. No working OAI-PMH endpoint exists on any TU Delft-operated host despite third-party registry entries claiming otherwise. TU Delft publishes no OpenAPI, no llms.txt, no scope vocabulary and no API changelog.

Delft University of Technology publishes 6 API contracts indexed on the APIs.io network, including Account API, Collections API, Datasets API, and 3 more. Tagged areas include University, Higher Education, Education, Technical University, and Research Data.

The Delft University of Technology catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Delft University of Technology’s developer surface includes documentation, API reference, engineering blog, support, authentication, and 36 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

47.6/100 developing ▬ flat Agent 19/100 agent aware Front door AI 2/6 trace Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFree⚡ Free to try

1 published contract

University Higher Education Education Technical University Research Data Open Access Identity Federation Research Repository Research Computing4TU.FederationNetherlands Europe Research Engineering

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Data & Reference Information Services

AE-230

Collections

GET /v2/collections

Research & Scholarship Management

BC-4780

Datasets

GET /v2/articles GET /v2/articles/{uuid} GET /v2/articles/{uuid}/versions

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 47.6/100 · developing

Contract Quality 12.5 / 21

Developer Ergonomics 6.1 / 17

Access Clarity 4.5 / 17

Operational Transparency 3.8 / 11

Contract Governance 3.4 / 10

Discoverability 6.5 / 9

Regulatory Posture 7.2 / 15

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Education & Research regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/tu-delft/"><img src="https://apis.io/badge/tu-delft/card.svg" alt="Delft University of Technology on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 26.3 — up to +14.7 composite points
Developer Ergonomics scores 35.7 — up to +12.9 composite points
Contract Quality scores 58.7 — up to +10.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/tu-delft/apis.yml: open an issue on github.com/api-evangelist/tu-delft to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Higher Education and Research	standard	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

TU Delft SAML 2.0 Identity Provider (NetID)

TU Delft's SimpleSAMLphp identity provider — the machine-readable half of NetID. It publishes a signed SAML 2.0 EntityDescriptor with an IDPSSODescriptor and is registered in SU...

Elsevier Pure research portal (TU Delft tenancy)

TU Delft runs an Elsevier Pure current research information system, exposed to the public as the research portal at research.tudelft.nl / pure.tudelft.nl and to integrators as t...

Delft University of Technology Account API

Token-authenticated endpoints scoped to a depositor account.

Delft University of Technology Collections API

Curated groupings of published datasets.

Delft University of Technology Datasets API

Published datasets (called "articles" on the Figshare-compatible v2 surface).

Delft University of Technology Reference API

Controlled vocabularies — licenses, categories and depositing groups.

Delft University of Technology API pricing

Not yet checked against Delft University of Technology's own pricing page. Compiled by API Evangelist on 2026-06-03 from raw.githubusercontent.com/api-evangelist/tu-delft/refs/he...; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free / Open free	Free
Affiliation / Credentialed free	Free

Plan details, limits and sources →

Rate limits

Default: see service documentation requests per minute

Compiled by API Evangelist, not yet checked against Delft University of Technology's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Tu Delft Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Tu Delft Rate Limits

1 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Delft University of Technology

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Tu Delft Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Tu Delft Context

16 classes · 0 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Delft University of Technology — 4tu rules

10 rules · 8 errors 2 warnings

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

4TU.ResearchData Dataset

42 properties

JSON SCHEMA

Examples 1

Example request and response payloads for these APIs.

Tu Delft 4Tu Researchdata Examples

5 fields

EXAMPLE

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Tu Delft Authentication

0 schemes

SECURITY

Tu Delft Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Tu Delft Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Tu Delft Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Documentation 3

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

APIReference

APIReference

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conformance

Lifecycle

Vocabulary

JSONLD

Build 7

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHubOrganization

SourceCode

LibraryCatalog

AITooling

Library

GitHubOrganization

GitHubOrganization

Scroll for all 7

Access & Security 6

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

SecurityTxt

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Scopes

Scopes

Learn 2

Tutorials, courses, talks, and written guidance

CourseCatalog

CourseCatalog

OpenCourseWare

OpenCourseWare

Operate 4

Status, limits, changes, and where to get help

IssueTracker

Releases

Support

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

PrivacyPolicy

TermsOfService

Plans

FinOps

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Other 8

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

OpenData

OpenData

ResearchRepository

ResearchRepository

ResearchRepository

ResearchRepository

IdentityFederation

IdentityFederation

ResearchComputing

ResearchComputing

AIPolicy

AIPolicy

Review

Review

Scroll for all 8

Source (apis.yml)

aid: tu-delft
name: Delft University of Technology
x-type: university
x-category: Technical University
description: 'Delft University of Technology (TU Delft) is the oldest and largest public technical university in the Netherlands
  and a member of the 4TU.Federation. Its programmable footprint is narrow, and this profile states that plainly rather than
  padding it. TU Delft operates exactly one public, unauthenticated API: the 4TU.ResearchData repository at data.4tu.nl, which
  runs on djehuty, open-source repository software written by 4TU.ResearchData and Nikhef. The /v2 surface is deliberately
  shape-compatible with the Figshare v2 API because that was a requirement of the 2023 migration OFF Figshare — the contract
  is not Figshare''s, and the service runs inside TU Delft''s own RIPE netblock (DUNET, 131.180.0.0/16). The other genuinely
  institution-operated machine-readable surface is a SAML 2.0 identity provider at login.tudelft.nl, published into the SURFconext
  national federation and onward to eduGAIN. Beyond those two, the picture is retirement and tenancy. The general-purpose
  institutional API platform at api.tudelft.nl — campus, buildings, courses, schedules, study results, organisation — no longer
  answers on port 80 or 443, and its documentation host apidoc.tudelft.nl has no DNS record at all. The research information
  portal at pure.tudelft.nl / research.tudelft.nl is an Elsevier Pure tenancy whose own API documentation canonicalises to
  api.elsevierpure.com: TU Delft''s data, Elsevier''s contract. The library discovery layer is an OCLC WorldCat tenancy. No
  working OAI-PMH endpoint exists on any TU Delft-operated host despite third-party registry entries claiming otherwise. TU
  Delft publishes no OpenAPI, no llms.txt, no scope vocabulary and no API changelog.'
type: Index
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - 4turesearchdata/djehuty
  open_source: unknown
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - openapi
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: free
  onboarding: unknown
  trial: false
  try_now: true
  public: true
  label: Free
  confidence: high
  source:
  - probed
  generated: '2026-08-19'
  method: probed
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/tu-delft.png
url: https://raw.githubusercontent.com/api-evangelist/tu-delft/refs/heads/main/apis.yml
x-docs-platform: mkdocs
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
tags:
- University
- Higher Education
- Education
- Technical University
- Research Data
- Open Access
- Identity Federation
- Research Repository
- Research Computing
- 4TU.Federation
- Netherlands
- Europe
- Research
- Engineering
created: '2026-06-03'
modified: '2026-08-19'
specificationVersion: '0.23'
x-coverage:
  state: covered
  reason: single_institutional_api_plus_federation_identity
  detail: 'The institution''s programmable surface was probed directly rather than inferred. One public institutional API
    was found and verified live (4TU.ResearchData, twelve endpoints answering HTTP 200/403/405 without credentials), and one
    machine-readable identity artifact was found and retrieved (SAML 2.0 IdP metadata, cross-confirmed in the live SURFconext
    aggregate). Three previously catalogued surfaces did not survive probing: the api.tudelft.nl platform is unreachable on
    both ports with its documentation host removed from DNS, and neither claimed OAI-PMH interface exists — data.4tu.nl returns
    a JSON 404 on every OAI path, and repository.tudelft.nl returns its soft-404 chrome on every OAI path over http and https,
    while the base URL OpenAIRE advertises for it belongs to TNO''s repository. One genuine tenant relationship the June 2026
    profile missed entirely was found and recorded rather than deleted: the Elsevier Pure instance at pure.tudelft.nl. The
    profile is thin because TU Delft''s public programmable footprint is thin, not because the hunt was short.'
  evidence:
  - url: https://data.4tu.nl/v2/articles?limit=1
    status: 200
  - url: https://data.4tu.nl/v3/datasets?limit=1
    status: 200
  - url: https://data.4tu.nl/v3/groups
    status: 200
  - url: https://data.4tu.nl/v2/licenses
    status: 200
  - url: https://data.4tu.nl/v2/categories
    status: 200
  - url: https://data.4tu.nl/v2/account/articles
    status: 403
  - url: https://data.4tu.nl/v2/articles/search
    status: 405
  - url: https://login.tudelft.nl/sso/saml2/idp/metadata.php
    status: 200
  - url: https://metadata.surfconext.nl/idps-metadata.xml
    status: 200
  - url: https://www.tudelft.nl/.well-known/security.txt
    status: 200
  - url: https://pure.tudelft.nl/ws/oai?verb=Identify
    status: 401
  - url: https://api.tudelft.nl/
    status: 0
    note: TCP timeout on 443 and 80; DNS resolves to 131.180.187.26 (DUNET)
  - url: https://apidoc.tudelft.nl/
    status: 0
    note: no DNS record
  - url: https://oauth.tudelft.nl/
    status: 0
    note: TCP timeout on 443
  - url: https://data.4tu.nl/oai?verb=Identify
    status: 404
  - url: https://repository.tudelft.nl/oai?verb=Identify
    status: 404
  - url: https://oai-pmh.tno.nl/OaiPmh?verb=Identify
    status: 200
    note: identifies as "TNO repository", noSetHierarchy — not TU Delft
  - url: https://www.tudelft.nl/llms.txt
    status: 404
  - url: https://data.4tu.nl/.well-known/openid-configuration
    status: 404
  - url: https://opendap.4tu.nl/thredds/catalog/catalog.xml
    status: 0
    note: documented by the operator, times out from the public internet
apis:
- aid: tu-delft:identity-federation
  name: TU Delft SAML 2.0 Identity Provider (NetID)
  x-operator: institution
  x-operator-evidence: The entityID is https://login.tudelft.nl/sso/saml2/idp/metadata.php, on the institution's own registrable
    domain, and the metadata document is served from that host directly with content-type application/samlmetadata+xml. The
    same entity appears in SURF's live SURFconext IdP aggregate under the display names "Technische Universiteit Delft" and
    "Delft University of Technology".
  description: 'TU Delft''s SimpleSAMLphp identity provider — the machine-readable half of NetID. It publishes a signed SAML
    2.0 EntityDescriptor with an IDPSSODescriptor and is registered in SURFconext, the Dutch national research and education
    identity federation operated by SURF, which in turn publishes into eduGAIN. This is the surface class universities operate
    by definition and almost never get catalogued for: it is institution-run, machine-readable, and it is what actually lets
    a researcher at another institution authenticate against a TU Delft service. Note what it is NOT — there is no OpenID
    Connect discovery document (login.tudelft.nl/.well-known/openid-configuration returns 403) and no OAuth 2.0 authorization
    server.'
  humanURL: https://www.tudelft.nl/en/it-manuals/netid
  baseURL: https://login.tudelft.nl/sso/saml2/idp/metadata.php
  tags:
  - Identity Federation
  - SAML
  - SSO
  - eduGAIN
  - SURFconext
  - NetID
  properties:
  - type: IdentityFederation
    url: authentication/tu-delft-saml-idp-metadata.xml
  - type: Metadata
    url: https://login.tudelft.nl/sso/saml2/idp/metadata.php
  - type: Authentication
    url: authentication/tu-delft-authentication.yml
  - type: Documentation
    url: https://www.tudelft.nl/en/it-manuals/netid
  - type: Federation
    url: https://metadata.surfconext.nl/idps-metadata.xml
- aid: tu-delft:pure
  name: Elsevier Pure research portal (TU Delft tenancy)
  x-operator: tenant
  x-operator-evidence: The API documentation served at https://pure.tudelft.nl/ws/api/ carries rel=canonical to https://api.elsevierpure.com/ws/api/index.html
    — the contract is Elsevier's product documentation running under a TU Delft hostname. The institution-specific subdomain
    makes this a tenancy, not an institutional API.
  description: TU Delft runs an Elsevier Pure current research information system, exposed to the public as the research portal
    at research.tudelft.nl / pure.tudelft.nl and to integrators as the Pure Web Service under /ws/api/ with a credential-gated
    OAI-PMH interface at /ws/oai (HTTP 401 — the interface exists and is gated, not absent). RECORDED AS A RELATIONSHIP, NOT
    A CONTRACT. The publications, people and project data are TU Delft's; the API surface that carries them is Elsevier's
    product and belongs on Elsevier's own scorecard. No Pure specification is saved into this repository, and nothing is derived
    from one. This entry exists so that a real institutional fact — TU Delft is a Pure customer — is on the record without
    a vendor's contract being credited to the university.
  humanURL: https://research.tudelft.nl/
  baseURL: https://pure.tudelft.nl/ws
  tags:
  - Research Information
  - CRI
  - Tenants
  - Elsevier Pure
  - Gated
  tags_raw:
  - Research Information
  - CRIS
  - Tenant
  - Elsevier Pure
  - Gated
  properties:
  - type: Website
    url: https://research.tudelft.nl/
  - type: Documentation
    url: https://pure.tudelft.nl/ws/api/
  - type: Authentication
    url: authentication/tu-delft-authentication.yml
- aid: tu-delft:tu-delft-account-api
  name: Delft University of Technology Account API
  description: Token-authenticated endpoints scoped to a depositor account.
  humanURL: https://data.4tu.nl/
  baseURL: https://data.4tu.nl
  tags:
  - Account
  properties:
  - type: OpenAPI
    url: openapi/tu-delft-account-api-openapi.yml
  - type: JSONSchema
    url: json-schema/tu-delft-4tu-dataset.json
  - type: Examples
    url: examples/tu-delft-4tu-researchdata-examples.json
  - type: Rules
    url: rules/tu-delft-4tu-rules.yml
  - type: Errors
    url: errors/tu-delft-4tu-errors.yml
  - type: Authentication
    url: authentication/tu-delft-authentication.yml
  - type: Scopes
    url: scopes/tu-delft-scopes.yml
  - type: Conformance
    url: conformance/tu-delft-conformance.yml
  - type: Lifecycle
    url: lifecycle/tu-delft-lifecycle.yml
  - type: Vocabulary
    url: vocabulary/tu-delft-vocabulary.yml
  - type: Documentation
    url: https://djehuty.4tu.nl/
  - type: SourceCode
    url: https://github.com/4TUResearchData/djehuty
  - type: TermsOfService
    url: https://data.4tu.nl/info/about-4turesearchdata/policies-guidelines
  - type: Support
    url: https://data.4tu.nl/info/about-4turesearchdata/contact
- aid: tu-delft:tu-delft-collections-api
  name: Delft University of Technology Collections API
  description: Curated groupings of published datasets.
  humanURL: https://data.4tu.nl/
  baseURL: https://data.4tu.nl
  tags:
  - Collection
  tags_raw:
  - Collections
  properties:
  - type: OpenAPI
    url: openapi/tu-delft-collections-api-openapi.yml
  - type: JSONSchema
    url: json-schema/tu-delft-4tu-dataset.json
  - type: Examples
    url: examples/tu-delft-4tu-researchdata-examples.json
  - type: Rules
    url: rules/tu-delft-4tu-rules.yml
  - type: Errors
    url: errors/tu-delft-4tu-errors.yml
  - type: Authentication
    url: authentication/tu-delft-authentication.yml
  - type: Scopes
    url: scopes/tu-delft-scopes.yml
  - type: Conformance
    url: conformance/tu-delft-conformance.yml
  - type: Lifecycle
    url: lifecycle/tu-delft-lifecycle.yml
  - type: Vocabulary
    url: vocabulary/tu-delft-vocabulary.yml
  - type: Documentation
    url: https://djehuty.4tu.nl/
  - type: SourceCode
    url: https://github.com/4TUResearchData/djehuty
  - type: TermsOfService
    url: https://data.4tu.nl/info/about-4turesearchdata/policies-guidelines
  - type: Support
    url: https://data.4tu.nl/info/about-4turesearchdata/contact
- aid: tu-delft:tu-delft-datasets-api
  name: Delft University of Technology Datasets API
  description: Published datasets (called "articles" on the Figshare-compatible v2 surface).
  humanURL: https://data.4tu.nl/
  baseURL: https://data.4tu.nl
  tags:
  - Datasets
  properties:
  - type: OpenAPI
    url: openapi/tu-delft-datasets-api-openapi.yml
  - type: JSONSchema
    url: json-schema/tu-delft-4tu-dataset.json
  - type: Examples
    url: examples/tu-delft-4tu-researchdata-examples.json
  - type: Rules
    url: rules/tu-delft-4tu-rules.yml
  - type: Errors
    url: errors/tu-delft-4tu-errors.yml
  - type: Authentication
    url: authentication/tu-delft-authentication.yml
  - type: Scopes
    url: scopes/tu-delft-scopes.yml
  - type: Conformance
    url: conformance/tu-delft-conformance.yml
  - type: Lifecycle
    url: lifecycle/tu-delft-lifecycle.yml
  - type: Vocabulary
    url: vocabulary/tu-delft-vocabulary.yml
  - type: Documentation
    url: https://djehuty.4tu.nl/
  - type: SourceCode
    url: https://github.com/4TUResearchData/djehuty
  - type: TermsOfService
    url: https://data.4tu.nl/info/about-4turesearchdata/policies-guidelines
  - type: Support
    url: https://data.4tu.nl/info/about-4turesearchdata/contact
- aid: tu-delft:tu-delft-reference-api
  name: Delft University of Technology Reference API
  description: Controlled vocabularies — licenses, categories and depositing groups.
  humanURL: https://data.4tu.nl/
  baseURL: https://data.4tu.nl
  tags:
  - Reference
  properties:
  - type: OpenAPI
    url: openapi/tu-delft-reference-api-openapi.yml
  - type: JSONSchema
    url: json-schema/tu-delft-4tu-dataset.json
  - type: Examples
    url: examples/tu-delft-4tu-researchdata-examples.json
  - type: Rules
    url: rules/tu-delft-4tu-rules.yml
  - type: Errors
    url: errors/tu-delft-4tu-errors.yml
  - type: Authentication
    url: authentication/tu-delft-authentication.yml
  - type: Scopes
    url: scopes/tu-delft-scopes.yml
  - type: Conformance
    url: conformance/tu-delft-conformance.yml
  - type: Lifecycle
    url: lifecycle/tu-delft-lifecycle.yml
  - type: Vocabulary
    url: vocabulary/tu-delft-vocabulary.yml
  - type: Documentation
    url: https://djehuty.4tu.nl/
  - type: SourceCode
    url: https://github.com/4TUResearchData/djehuty
  - type: TermsOfService
    url: https://data.4tu.nl/info/about-4turesearchdata/policies-guidelines
  - type: Support
    url: https://data.4tu.nl/info/about-4turesearchdata/contact
common:
- type: CapabilityMap
  url: capabilities/tu-delft-capability-edges.yml
  name: Delft University of Technology Business Capability Map
- type: IssueTracker
  url: https://github.com/4TUResearchData/djehuty/issues
- type: Releases
  url: https://github.com/4TUResearchData/djehuty/releases
- type: SecurityPolicy
  url: https://github.com/4TUResearchData/djehuty/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/4TUResearchData/djehuty/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/4TUResearchData/djehuty/blob/main/CONTRIBUTING.md
- type: Website
  url: https://www.tudelft.nl/
- type: LinkedIn
  url: https://www.linkedin.com/school/tu-delft/
- type: GitHubOrganization
  url: https://github.com/4TUResearchData
- type: SourceCode
  url: https://github.com/4TUResearchData/djehuty
- type: Documentation
  url: https://djehuty.4tu.nl/
- type: APIReference
  url: https://djehuty.4tu.nl/
- type: OpenData
  url: https://data.4tu.nl/
- type: ResearchRepository
  url: https://repository.tudelft.nl/
- type: ResearchRepository
  url: https://research.tudelft.nl/
- type: LibraryCatalog
  url: https://tudelft.on.worldcat.org/discovery
- type: CourseCatalog
  url: https://studiegids.tudelft.nl/
- type: IdentityFederation
  url: https://login.tudelft.nl/sso/saml2/idp/metadata.php
- type: ResearchComputing
  url: https://doc.dhpc.tudelft.nl/delftblue/
- type: AIPolicy
  url: https://www.tudelft.nl/en/teaching-support/educational-advice/assess/guidelines/ai-chatbots-in-unsupervised-assessment
- type: AITooling
  url: https://www.tudelft.nl/en/ai
- type: OpenCourseWare
  url: https://ocw.tudelft.nl/
- type: Library
  url: https://www.tudelft.nl/en/library/
- type: Blog
  url: https://community.data.4tu.nl/
- type: Support
  url: https://www.tudelft.nl/en/contact
- type: PrivacyPolicy
  url: https://www.tudelft.nl/en/privacy-statement
- type: TermsOfService
  url: https://data.4tu.nl/info/about-4turesearchdata/policies-guidelines
- type: SecurityTxt
  url: https://www.tudelft.nl/.well-known/security.txt
- type: VulnerabilityDisclosure
  url: security/tu-delft-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/tu-delft-domain-security.yml
- type: Authentication
  url: authentication/tu-delft-authentication.yml
- type: Scopes
  url: scopes/tu-delft-scopes.yml
- type: Conformance
  url: conformance/tu-delft-conformance.yml
- type: Lifecycle
  url: lifecycle/tu-delft-lifecycle.yml
- type: Vocabulary
  url: vocabulary/tu-delft-vocabulary.yml
- type: JSONLD
  url: json-ld/tu-delft-context.jsonld
- type: Plans
  url: plans/tu-delft-plans-pricing.yml
- type: RateLimits
  url: rate-limits/tu-delft-rate-limits.yml
- type: FinOps
  url: finops/tu-delft-finops.yml
- type: Review
  url: review.yml
- type: GitHubOrganization
  url: https://github.com/tudelft
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Delft University of Technology API — frequently asked questions

Does Delft University of Technology have an API?

Yes. APIs.io lists 6 APIs from Delft University of Technology, including TU Delft SAML 2.0 Identity Provider (NetID), Elsevier Pure research portal (TU Delft tenancy) and Delft University of Technology Account API, and 3 more.

Is there an OpenAPI specification for the Delft University of Technology API?

Yes. APIs.io indexes 4 OpenAPI specifications for Delft University of Technology, each linked for download from this page.

How do I authenticate with the Delft University of Technology API?

Delft University of Technology uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Tu Delft Authentication.

How much does the Delft University of Technology API cost?

APIs.io lists 2 pricing plans for Delft University of Technology, with each plan's price, limits and inclusions under Pricing on this page.

Is the Delft University of Technology API ready for AI agents?

Delft University of Technology has a Kin Score of 47.6 out of 100 (developing) and an Agent Readiness score of 18.5 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/tu-delft"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/tu-delft/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/tu-delft/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.