Terms of use

The API is free to use for any purpose, commercial or not. You may call it from a browser, a server, a mobile app, a script, a bot, a spreadsheet, a class project or a commercial product.

You may use, store, copy, analyse, transform and display the data it returns, and you may redistribute data you obtained through the API, including inside your own product or service.

You may use it without credit, though saying where the data came from is a kind thing to do. There is no fee. The course level data needs a key, and a key is free.

The scheme list, the grade scale, the branch list and the credit totals of each semester are open. The courses of one semester need a developer key. The whole scheme in one answer needs a key and is allowed five times a day.

A key is sent in the X-API-Key header. It is a line of text, it never belongs in code that runs in somebody else's browser, and it can be replaced at any time.

The calculator uses a session instead of a key. A session is short lived, has a request budget and a data budget, and every answer for it comes back encrypted. That is a control on how fast and how often the data can be taken. It is not a claim that taking it is impossible, and anyone who reads the calculator's source can see exactly how it works.

The scheme tables are the point of this service. They are meant to be consumed through the API, the way the calculator consumes them.

Please do not scrape the API to build a bulk mirror of the dataset, crawl every branch and every semester on every request when one call to /api/schemes/{scheme}/export would do, or republish the dataset as a downloadable file or a standalone product.

If you want the whole dataset, make a key and take the export route. It is one call with a budget, and that is the supported way to get everything.

There is a limit on every caller and the answer carries the numbers, so you always know where you stand. An address without a key gets 120 calls a minute and 10000 a day. A calculator session gets 150 calls and 96 KB of data for 30 minutes. A developer key gets 600 calls a minute, 100000 a day and five bulk exports.

Metadata answers are stable and carry a one day cache lifetime, so cache them. Send a User-Agent that identifies your client. If you are building something large, get in touch before you launch it.

We will not cut off a well-behaved client. We will slow down and log a client that is trying to take the service down.

The data comes from the official VTU scheme PDFs, and the credit totals are checked against the totals printed in those PDFs for every branch and every semester.

It is still a transcription, so it is not infallible. Check any figure against your own marks card before you rely on it. If you find a mistake, tell us and we will fix it.

The API and the data are provided on an as-is and best-effort basis, without warranty of any kind. We do not guarantee that it will be available, uninterrupted or free of errors, and we do not guarantee that it will stay at the same address.

To the maximum extent permitted by law, the maintainers of this API are not liable for any loss arising out of its use, including lost profits, lost data and lost goodwill, however that loss arises.

The API does not set cookies and does not collect personal data. The dashboard signs you in with Google and keeps a session cookie of its own. Server logs record the requested path, the client address, the status and the size of the answer, as any web server does. They are used to keep the service running and to find abuse. A key is never written to a log.

These terms may change. The version on this page is the version that applies. Material changes will be announced at https://dev.vtu.drshn.tech.