How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Campus Micromobility Vehicle Positions API

Live positions of shared micromobility vehicles on and around campus as GeoJSON, served from veoride.geoservices.tamu.edu inside Texas A&M's own geoservices estate. Verified 200 on 2026-09-01 returning 3,300 Point features. The scooter fleet is a vendor's; the feed is published from a Texas A&M host. Every feature's properties object is empty, so no vehicle id, type, battery level or availability is exposed — that absence is recorded deliberately.

Campus Micromobility Vehicle Positions API is one of 13 APIs that Texas A&M University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Campus Life, Transportation, Micromobility, and GeoJSON. The published artifact set on APIs.io includes an OpenAPI specification, sample payloads, and 1 JSON Schema.

This API exposes 1 operation across 1 path, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://veoride.geoservices.tamu.edu.

1 operations 1 paths 3 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://veoride.geoservices.tamu.edu
Resource Areas
1

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Micromobility 1

Shared vehicle positions on campus.

GET
/api/vehicles/basic/geojson
Current shared-vehicle positions as GeoJSON
getVehiclePositionsGeoJson → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are VehicleFeature (3 properties), PointGeometry (2 properties), VehicleFeatureCollection (2 properties). Each schema is shown below with its type and property counts.

VehicleFeatureCollection
object
2 properties 2 required
VehicleFeature
object
3 properties 3 required
PointGeometry
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

texas-a-m-university-campus-micromobility-openapi.yml Raw ↑

Other APIs Texas A&M University publishes across the network.

Texas A&M GeoServices Geocoding API
Aggie Map Dining Locations API
Texas A&M IT ArcGIS REST Services
OAKTrust Institutional Repository — OAI-PMH
Texas A&M Shibboleth Identity Provider Metadata
InCommon Federation Registration
UIN Services API
Texas A&M Course Catalog (CourseLeaf)
Canvas Learning Management System (tenancy)
DataCite Registrant — Texas A&M Libraries
Crossref Member — Texas A&M University Libraries
ROR Registration
Where this information came from

This is an independent, third-party profile of Campus Micromobility Vehicle Positions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.