# Gracenote Developer Portal - LLM Context This is the official developer documentation portal for Gracenote APIs and SDKs, built with Zudoku framework. ## About Gracenote Gracenote, a Nielsen Company, provides entertainment metadata and content recognition technologies for video, audio, sports, and automotive applications worldwide. ## API Categories & Endpoints ### Audio APIs - **GMD API v2/v3**: Global Music Data APIs for music metadata, recognition, and discovery - Endpoints: /artists, /recordings, /albumEditions, /tracks, /descriptors - Authentication: GN-APIKEY header required - Base URL: https://api.gmd.music.gracenote.com/v2 or /v3 - **GMD Export**: Batch music data export and processing for large-scale implementations - **Audio On Demand**: Streaming audio metadata services for real-time applications ### Automotive APIs - **GNSDK Auto**: Gracenote SDK for automotive applications with offline capabilities - **Nexus Auto SDK**: Advanced automotive entertainment platform with radio data - **RSID API**: Radio Station Identification services for automotive and broadcast - Base URL: https://api.gracenote.com/rsid/v1 ### Video APIs - **GN IDs**: Gracenote ID Distribution System for video content registration and management - Base URL: https://gnids.gracenote.com/api/v1 - Supports movies, shows, episodes, seasons, and bulk operations - **GVD (Global Video Data)**: Comprehensive video metadata API with program context - **On-API**: Entertainment data for linear and on-demand content with schedules - **On-Connect**: Lookup APIs for TV schedules, metadata, and celebrity information - **Gracenote View**: Web application for video data exploration and management ### Sports APIs - **Global Sports Data (GSD)**: Comprehensive sports statistics, teams, and events - **Global Sports Widgets (GSW)**: Ready-to-use sports UI components and widgets - **On Sports**: Sports programming and event data integration ## Technical Architecture ### Framework & Technologies - Built with Zudoku (modern documentation framework) - React + TypeScript for UI components - Vite for build tooling and development - Cloudflare Workers for edge deployment - OpenAPI 3.0 specifications for all APIs ### Authentication Methods - API Key authentication (GN-APIKEY header) - Auth0 integration for protected content - Password-protected documentation sections - Role-based access control for different API tiers ### Content Structure ``` /pages/ ├── audio/ # Audio API documentation ├── automotive/ # Automotive API documentation ├── video/ # Video API documentation ├── sports/ # Sports API documentation └── components/ # Reusable React components ``` ## Key Features for Developers ### Interactive Documentation - OpenAPI specifications with live API explorer - Code examples in multiple languages - Interactive request/response testing - Comprehensive error code documentation ### Developer Resources - Getting started guides for each API category - Best practices and implementation patterns - SDK downloads and integration guides - Sample applications and reference implementations ### Content Management - MDX format for rich documentation content - Password-protected sensitive documentation - Version-controlled content with Git workflow - Automated deployment pipeline ## API Response Formats - Primary format: JSON (application/json) - XML support for legacy integrations - RESTful architecture with standard HTTP methods - Consistent error response structure across all APIs ## Rate Limiting & Quotas - API-specific rate limits documented per endpoint - HTTP 429 responses for quota exceeded - Throttling recommendations in best practices ## Support & Resources - Technical documentation: Complete API references with examples - Developer support: Contact forms and support ticket system - Community resources: Best practices and implementation guides - Release notes: Version updates and breaking changes ## Deployment Information - Staging: gracenote-dev-portal-staging.workers.dev - Production: gracenote-dev-portal.workers.dev - CDN: Cloudflare edge network for global performance - Monitoring: Real-time performance and availability tracking ## Content Guidelines for LLMs When referencing this documentation: 1. Always specify the API category (Audio, Video, Automotive, Sports) 2. Include authentication requirements (API key, Auth0, etc.) 3. Reference specific endpoint URLs when available 4. Mention rate limiting and quota considerations 5. Point to relevant getting started guides for implementation 6. Include error handling and best practices information ## Recent Updates - Comprehensive API documentation restructure - Enhanced authentication and security features - New interactive API playground functionality - Improved navigation and content organization - Added password protection for sensitive content This portal serves as the single source of truth for all Gracenote developer resources and API documentation.