Organization Service
Services represent content-producing entities that NPR interacts with. “Content” here can be interpreted broadly; it can refer to text stories displayed on a website, podcasts, audio played over a stream, a newscast file, etc. Importantly, all content produced by a Service should utilize a single, consistent branding label; they should use the same title, logo, etc. on all content produced.
Organizations can be affiliated with Services; this affiliation is maintained via external data sources and represented in the Organization Service via the /v4/organizations/<org ID> endpoint. Because Organizations may produce content under multiple brands, Organizations can have multiple Services, but each Service can only have up to one Organization.
Stations and Legacy Organizations are associated with Services as well. Each Station and Legacy Organization will have one and only one Service associated; Services can be affiliated with any number of these entities.
In the Organization Service, Service data is available via the /v4/services/<service ID> endpoint.
A consortium is a Service that aggregates a group of other Services. The Services associated with a consortia is available through the /v4/services/<service ID> endpoint.
Each Service in the Organization Service has a “service ID”. This is a unique identifier for the Service data. While many service IDs take the form of s<org ID>, this is NOT an assumption developers should rely on; many service IDs do not take this form. In addition, due to the dynamic nature of station and service relationships, developers should NOT assume that a service with the ID s<org ID> is affiliated with the station with <org ID>; this station may have moved, merged, or even been deleted.
Like other IDs within the Organization Service, service IDs should be treated independently of other IDs, and data should not be parsed from the ID itself.