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

Texas A&M GeoServices Geocoding API

Free geocoding, address normalisation and standardisation, census intersection and reverse geocoding from Texas A&M GeoServices. Version 5.0.0 returns up to 172 output fields; an API key from a free self-service account profile is required on every request and travels as a query parameter. Institution-operated: geoservices.tamu.edu is under Texas A&M's own registrable domain and the service is the university's own research product, not a platform vendor's. Verified live 2026-09-01 — an anonymous call returns HTTP 200 carrying queryStatusCode APIKeyMissing, which confirms both the parameter contract and the auth model.

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

Tagged areas include Geocoding, Geospatial, Address, and GIS. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

1 operations 1 paths 2 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.0.0
Base URL
https://geoservices.tamu.edu/Api/Geocode/V5/
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Texas A&M GeoServices Geocoding API declares 1 security scheme for authenticating requests. An API key is passed in the query as apiKey (apiKeyQuery).

  • apiKeyQuery — Free API key issued from the GeoServices account profile at https://geoservices.tamu.edu/Signup/. Sent as a query parameter; there is no header form.

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.

Geocoding 1

Address to coordinate resolution with optional census intersection.

GET
/
Geocode a US street address
geocodeAddress 28 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are GeocodeResult (8 properties), GeocodeEnvelope (4 properties). Each schema is shown below with its type and property counts.

GeocodeEnvelope
object
Response envelope observed live on 2026-09-01. The error shape (statusCode, message, error, data) was captured from a real anonymous call; the success members…
4 properties
GeocodeResult
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

texas-a-m-university-geoservices-geocoding-openapi.yml Raw ↑

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

Aggie Map Dining Locations API
Campus Micromobility Vehicle Positions 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 Texas A&M GeoServices Geocoding 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.