PTV Timetable API - Version 3

Name: PTV Timetable API - Version 3 API
Brand: PTV Timetable API - Version 3
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationMappingnone26 EndpointsREST

For Agents

Programmatically view departures for all routes from a stop, view departures for a specific route from a stop. Covers 26 operations.

Connect the PTV Timetable API - Version 3 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PTV Timetable API - Version 3, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PTV Timetable API - Version 3 API.

View departures for all routes from a stop

Get all disruption modes

Access PTV Timetable API - Version 3 resources via REST API

Use Cases

Patterns agents use PTV Timetable API - Version 3 API for, with concrete tasks.

GET STARTED

Start building with PTV Timetable API - Version 3 API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for PTV Timetable API - Version 3, keeping it validated and agent-ready.

The PTV Timetable API provides direct access to Public Transport Victoria’s public transport timetable data. The API returns scheduled timetable, route and stop data for all metropolitan and regional train, tram and bus services in Victoria, including Night Network(Night Train and Night Tram data are included in metropolitan train and tram services data, respectively, whereas Night Bus is a separa. The API exposes 26 endpoints.

★ Maps and Geolocation Operations

Use the PTV Timetable API - Version 3 to perform maps geolocation operations programmatically. The API provides 26 endpoints covering core functionality including view departures for all routes from a stop, view departures for a specific route from a stop, view directions that a route travels in.

Call GET /v3/departures/route_type/{route_type}/stop/{stop_id} to view departures for all routes from a stop

Automated Departures Management

Automate departures operations by combining multiple PTV Timetable API - Version 3 endpoints. Agents can view departures for a specific route from a stop and then view directions that a route travels in in a single workflow.

Call GET /v3/departures/route_type/{route_type}/stop/{stop_id}/route/{route_id} to view departures for a specific route from a stop, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PTV Timetable API - Version 3 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'view departures for all routes from a stop', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

26 endpoints — the ptv timetable api provides direct access to public transport victoria’s public transport timetable data.

METHOD

PATH

DESCRIPTION

GET

/v3/departures/route_type/{route_type}/stop/{stop_id}

View departures for all routes from a stop

GET

/v3/departures/route_type/{route_type}/stop/{stop_id}/route/{route_id}

View departures for a specific route from a stop

GET

/v3/directions/route/{route_id}

View directions that a route travels in

GET

/v3/directions/{direction_id}

View all routes for a direction of travel

GET

/v3/directions/{direction_id}/route_type/{route_type}

View all routes of a particular type for a direction of travel

GET

/v3/disruptions

View all disruptions for all route types

GET

/v3/disruptions/modes

Get all disruption modes

GET

/v3/disruptions/route/{route_id}

View all disruptions for a particular route

GET

/v3/departures/route_type/{route_type}/stop/{stop_id}

View departures for all routes from a stop

GET

/v3/departures/route_type/{route_type}/stop/{stop_id}/route/{route_id}

View departures for a specific route from a stop

GET

/v3/directions/route/{route_id}

View directions that a route travels in

GET

/v3/directions/{direction_id}

View all routes for a direction of travel

GET

/v3/directions/{direction_id}/route_type/{route_type}

View all routes of a particular type for a direction of travel

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PTV Timetable API - Version 3 none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'view departures for all routes from a stop') and Jentic returns the matching PTV Timetable API - Version 3 operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PTV Timetable API - Version 3 integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Here

Alternative maps geolocation API

Choose Here when you need a different approach to maps geolocation operations

Alternative

Tomtom

Alternative maps geolocation API

Choose Tomtom when you need a different approach to maps geolocation operations

Complementary

Googleapis

Complementary maps geolocation API

Choose Googleapis when you need a complementary approach to maps geolocation operations

FAQs

Specific to using PTV Timetable API - Version 3 API through Jentic.

What authentication does the PTV Timetable API - Version 3 use?

The PTV Timetable API - Version 3 uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I view departures for all routes from a stop with the PTV Timetable API - Version 3?

Yes. Use the GET /v3/departures/route_type/{route_type}/stop/{stop_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PTV Timetable API - Version 3?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I view departures for all routes from a stop through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'view departures for all routes from a stop'. Jentic returns the matching PTV Timetable API - Version 3 operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the PTV Timetable API - Version 3 have?

The PTV Timetable API - Version 3 exposes 26 endpoints covering departures, directions, disruptions operations.