Wmata

Incidents

Rail, bus, and elevator disruptions/outages.

Logistics & shipping#openapi#transport

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

Rail, bus, and elevator disruptions/outages.

Endpoints 6

  • GETXML - Bus Incidents/BusIncidents?Route=90<h4 class="text-primary">Description</h4> <p>Returns a set of reported bus incidents/delays for a given Route. Omit the Route to return all reported…
  • GETXML - Elevator/Escalator Outages/ElevatorIncidents?StationCode=A03<h4 class="text-primary">Description</h4> <p>Returns a list of <em>reported</em> elevator and escalator outages at a given station. Omit the StationCode…
  • GETXML - Rail Incidents/Incidents<h4 class="text-primary">Description</h4> <p>Returns reported rail incidents (significant disruptions and delays to normal service). The data is identical to…
  • GETJSON - Bus Incidents/json/BusIncidents?Route=90<h4 class="text-primary">Description</h4> <p>Returns a set of reported bus incidents/delays for a given Route. Omit the Route to return all reported…
  • GETJSON - Elevator/Escalator Outages/json/ElevatorIncidents?StationCode=A03<h4 class="text-primary">Description</h4> <p>Returns a list of <em>reported</em> elevator and escalator outages at a given station. Omit the StationCode…
  • GETJSON - Rail Incidents/json/Incidents<h4 class="text-primary">Description</h4> <p>Returns reported rail incidents (significant disruptions and delays to normal service). The data is identical to…

API details

Base URL
https://api.wmata.com/Incidents.svc
Authentication
An API key in the api_key header
An API key in the api_key query parameter
Operations
6 operations on 6 pathsGET 6
Description format
Swagger 2.0, API version 1.0
Listed from
APIs.guru OpenAPI Directory (CC0-1.0)
Source updated

How to test the Incidents in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Incidents collection, without the publisher's secrets.
  3. Add your credentialsThis API uses an API key in the api_key header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “XML - Bus Incidents” (GET /BusIncidents?Route=90), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Incidents?

Rail, bus, and elevator disruptions/outages. It is listed under Logistics & shipping and has 6 endpoints.

Who publishes the Incidents?

It is listed from Wmata's public API description (an OpenAPI document), not published by Wmata on Swastik Codes. Anyone who controls wmata.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Incidents?

Requests go to https://api.wmata.com/Incidents.svc. Endpoint paths are added to this base URL.

How do I authenticate with the Incidents?

It accepts 2 methods: an API key in the api_key header; an API key in the api_key query parameter.

How many endpoints does the Incidents have?

6 operations on 6 paths (6 GET).

Is forking the Incidents free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.