How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

University of Amsterdam tag management API

The tag management API from University of Amsterdam — 12 operation(s) for tag management.

University of Amsterdam tag management API is one of 122 APIs that University of Amsterdam publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tag Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 12 operations across 12 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.95.0.

Requests are made against a single base URL, https://llmproxy.uva.nl.

12 operations 12 paths 22 schemas 8 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.95.0
Base URL
https://llmproxy.uva.nl
Authentication
API Key
Resource Areas
1

Authentication & Security 1

University of Amsterdam tag management API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-litellm-api-key (APIKeyHeader).

  • APIKeyHeader — Bearer token

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 8 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

tag management 12
POST
/tag/new
New Tag
new_tag_tag_new_post body → 200422
POST
/tag/update
Update Tag
update_tag_tag_update_post body → 200422
POST
/tag/info
Info Tag
info_tag_tag_info_post body → 200422
GET
/tag/list
List Tags
list_tags_tag_list_get 2 params → 200422
POST
/tag/delete
Delete Tag
delete_tag_tag_delete_post body → 200422
GET
/tag/daily/activity
Get Tag Daily Activity
get_tag_daily_activity_tag_daily_activity_get 7 params → 200422
GET
/tag/distinct
Get Distinct User Agent Tags
get_distinct_user_agent_tags_tag_distinct_get → 200
GET
/tag/dau
Get Daily Active Users
get_daily_active_users_tag_dau_get 2 params → 200422
GET
/tag/wau
Get Weekly Active Users
get_weekly_active_users_tag_wau_get 2 params → 200422
GET
/tag/mau
Get Monthly Active Users
get_monthly_active_users_tag_mau_get 2 params → 200422
GET
/tag/summary
Get Tag Summary
get_tag_summary_tag_summary_get 4 params → 200422
GET
/tag/user-agent/per-user-analytics
Get Per User Analytics
get_per_user_analytics_tag_user_agent_per_user_analytics_get 4 params → 200422

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are DailySpendMetadata (15 properties), TagUpdateRequest (12 properties), SpendMetrics (12 properties), TagNewRequest (12 properties). Each schema is shown below with its type and property counts.

TagActiveUsersResponse
object
Response for tag active users metrics
5 properties 3 required
TagSummaryMetrics
object
Summary metrics for a tag
7 properties 7 required
DailySpendMetadata
object
15 properties
ActiveUsersAnalyticsResponse
object
Response for active users analytics
1 property 1 required
DailySpendData
object
3 properties 2 required
MetricWithMetadata
object
3 properties 1 required
BreakdownMetrics
object
Breakdown of spend by different dimensions
7 properties
TagUpdateRequest
object
12 properties 1 required
DistinctTagsResponse
object
Response for all distinct user agent tags
1 property 1 required
KeyMetadata
object
Metadata for a key
2 properties
SpendMetrics
object
12 properties
ValidationError
object
5 properties 3 required
PerUserAnalyticsResponse
object
Response for per-user analytics
5 properties 5 required
TagInfoRequest
object
1 property 1 required
TagNewRequest
object
12 properties 1 required
TagSummaryResponse
object
Response for tag summary analytics
1 property 1 required
DistinctTagResponse
object
Response for distinct user agent tags
1 property 1 required
HTTPValidationError
object
1 property
PerUserMetrics
object
Metrics for individual user
8 properties 1 required
TagDeleteRequest
object
1 property 1 required
SpendAnalyticsPaginatedResponse
object
2 properties 1 required
KeyMetricWithMetadata
object
Base class for metrics with additional metadata
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-amsterdam-tag-management-api-openapi.yml Raw ↑

Other APIs University of Amsterdam publishes across the network.

UvA Identity Provider (SAML 2.0 / SURFconext)
DataNose API
UvA Library Linked Open Data (TriplyDB tenancy)
UvA-DARE OAI-PMH and Pure Web Service (Elsevier Pure tenancy)
UvA Archives Collection Descriptions OAI-PMH (ArchivesSpace tenancy)
UvA Central Catalogue OAI-PMH (Ex Libris Alma tenancy)
UvA/HvA Research Data Repository (Figshare tenancy)
UvA Timetable API (MyTimetable tenancy)
University of Amsterdam A2a API
University of Amsterdam A2a Registration API
University of Amsterdam access group management API
University of Amsterdam Adaptive Router API
Where this information came from

This is an independent, third-party profile of University of Amsterdam tag management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.