Waste collection calendar at the Oslo address
oslo_waste_calendar21 fieldsNot in the demo
Available with: none — not served through the API
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- Exact-address Oslo calendar observation, not a nearby dwelling's calendar. The latest stored observation is projected; earlier observations remain in the collection ledger. Empty or missing exact-address results are not zero collections.
- Published collection dates do not establish truck arrival time, actual completed collection, residents served or noise levels. Bin counts refer to published service containers and shared collection points must not be added as independent households.
- observed_at is our source retrieval clock. The source-update clock is unknown and section freshness remains unverified; observation_age_hours shows retrieval age. Collection dates use Europe/Oslo and retain date-only precision.
- Customer publication is withheld until source reuse terms are confirmed. Adding this section grants no source rights.
Fields
3 of 21 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| address_id | string | context |
| pipeline_run_id | string | context |
| observed_at | string | context |
| source_status | string | context |
| address_match | string | null | context |
| source_updated_at | string | null | context |
| observation_age_hours | number (hours) | context |
| collection_point_id | integer | null | context |
| service_id | integer | null | context |
| next_collection_date | string | null | value |
| time_precision | string | null | context |
| timezone | string | null | context |
| fraction_id | integer | null | context |
| fraction_name | string | null | context |
| bin_count | integer | null (bins) | value |
| bin_capacity_litres | integer | null (litres) | value |
| frequency_text | string | null | context |
| published_weekday | string | null | context |
| arrival_window | string | null | context |
| people_served | integer | null | context |
| redistribution_rights | string | context |
Fetch this section
Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.
curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=oslo_waste_calendar' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/oslo_waste_calendar?limit=25'
Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.