Indian Institute of Science Bangalore · API Governance Rules

Indian Institute of Science Bangalore API Rules

Spectral linting rules defining API design standards and conventions for Indian Institute of Science Bangalore.

6 Rules error 2 warn 4
Derived by API Evangelist Measured from the API contracts Indian Institute of Science Bangalore publishes — the conventions those documents already follow, written down as rules. Indian Institute of Science Bangalore did not publish this file.
View Rules File View on GitHub

Rule Categories

iisc

Rules

warn
iisc-info-contact
API info should include a contact.
$.info
error
iisc-server-https
ETD@IISc REST servers must be served over HTTPS.
$.servers[*].url
error
iisc-operation-id
Every operation must declare an operationId.
$.paths[*][get,post,put,delete,patch]
warn
iisc-object-has-uuid
Core DSpace resource schemas (Community, Collection, Item, Bitstream) should expose a uuid property, matching the live API.
$.components.schemas[Community,Collection,Item,Bitstream]
warn
iisc-object-has-type-discriminator
DSpace base object must carry a string "type" discriminator.
$.components.schemas.DSpaceObject.properties.type
warn
iisc-read-only-paths
The public ETD@IISc profile is read-only; only GET operations are expected on documented paths.
$.paths[*]

Spectral Ruleset

Raw ↑
---
# x-generated: '2026-09-01'
# x-method: derived
# x-source: openapi/_original/iisc-etd-rest.yaml — Spectral rules encoding conventions observed in the ETD@IISc DSpace 6 contract
# Spectral ruleset encoding patterns observed in the ETD@IISc DSpace 6 REST API.
# These rules express conventions confirmed against the live API: UUID-keyed
# resources, handle identifiers, a discriminating "type" field, and read-only
# JSON responses.
formats:
  - oas3
rules:
  iisc-info-contact:
    description: API info should include a contact.
    severity: warn
    given: $.info
    then:
      field: contact
      function: truthy

  iisc-server-https:
    description: ETD@IISc REST servers must be served over HTTPS.
    severity: error
    given: $.servers[*].url
    then:
      function: pattern
      functionOptions:
        match: "^https://"

  iisc-operation-id:
    description: Every operation must declare an operationId.
    severity: error
    given: $.paths[*][get,post,put,delete,patch]
    then:
      field: operationId
      function: truthy

  iisc-object-has-uuid:
    description: >-
      Core DSpace resource schemas (Community, Collection, Item, Bitstream)
      should expose a uuid property, matching the live API.
    severity: warn
    given: $.components.schemas[Community,Collection,Item,Bitstream]
    then:
      function: defined

  iisc-object-has-type-discriminator:
    description: DSpace base object must carry a string "type" discriminator.
    severity: warn
    given: $.components.schemas.DSpaceObject.properties.type
    then:
      field: type
      function: truthy

  iisc-read-only-paths:
    description: >-
      The public ETD@IISc profile is read-only; only GET operations are
      expected on documented paths.
    severity: warn
    given: $.paths[*]
    then:
      field: post
      function: undefined

Work with this as data

Every ruleset 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 spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset in the catalog.
  • 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 ruleset
curl "https://apis.io/api/v1/rules/iisc-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?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.