Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/toyota-trips-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Toyota Connected Services Trips API
description: Toyota Connected Services API enables authorized applications to access real-time vehicle data and remote control features for Toyota and Lexus connected vehicles. Provides vehicle status, location, electric vehicle charging data, climate control, trip history, notifications, and service history for vehicles enrolled in Toyota Connected Services.
version: 1.0.0
contact:
name: Toyota Developer Portal
url: https://developer.eig.toyota.com/
servers:
- url: https://api.toyota.com/connected/v1
description: Toyota Connected Services API
security:
- bearerAuth: []
tags:
- name: Trips
description: Trip history and driving data
paths:
/vehicles/{vin}/trips:
get:
operationId: getTrips
summary: Get Trips
description: Returns trip history for a connected vehicle within a specified date range.
tags:
- Trips
parameters:
- name: vin
in: path
required: true
schema:
type: string
- name: fromDate
in: query
required: true
schema:
type: string
format: date
description: Start date for trip history
- name: toDate
in: query
required: true
schema:
type: string
format: date
description: End date for trip history
- name: limit
in: query
schema:
type: integer
default: 50
maximum: 50
description: Maximum trips to return
- name: offset
in: query
schema:
type: integer
default: 0
description: Pagination offset
- name: includeRoute
in: query
schema:
type: boolean
default: false
description: Include GPS route for each trip
- name: includeSummary
in: query
schema:
type: boolean
default: true
description: Include trip summary statistics
responses:
'200':
description: Trip history
content:
application/json:
schema:
$ref: '#/components/schemas/TripHistoryList'
components:
schemas:
TripHistoryList:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/TripHistory'
total:
type: integer
limit:
type: integer
offset:
type: integer
TripHistory:
type: object
properties:
id:
type: string
vin:
type: string
startTime:
type: string
format: date-time
endTime:
type: string
format: date-time
distanceMiles:
type: number
durationMinutes:
type: integer
averageSpeedMph:
type: number
maxSpeedMph:
type: number
startAddress:
type: string
endAddress:
type: string
startCoordinates:
$ref: '#/components/schemas/Coordinates'
endCoordinates:
$ref: '#/components/schemas/Coordinates'
route:
type: array
items:
$ref: '#/components/schemas/Coordinates'
Coordinates:
type: object
properties:
latitude:
type: number
format: double
longitude:
type: number
format: double
timestamp:
type: string
format: date-time
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT