Discover/πš‹πšŠπš‘πšπšŽπš• API
live

πš‹πšŠπš‘πšπšŽπš• APIπš‹πšŠπš‘πšπšŽπš•.πšŒπš˜πš– β†—

Search Baxtel's data center facilities to find real-time operational details like power capacity, status, geographic coordinates, and nearby infrastructure. Quickly locate and compare data centers to identify the best options for your deployment or infrastructure planning needs.

This API takes change requests β€” .
Endpoint health
monitored
get_data_center
list_data_centers
Checks pendingself-healing
Endpoints
2
Updated
2h ago
This call costs2 credits / callβ€” charged only on success
Try it
Page number for paginated results. Each page returns up to 50 facilities.
Region slug identifying the geographic area (e.g. 'austin', 'dallas', 'houston', 'texas'). Use city/metro slugs for complete listings.
β†’ api.parse.bot/scraper/658b7f08-058f-4af3-a0a2-ebea9d21c0ea/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/658b7f08-058f-4af3-a0a2-ebea9d21c0ea/list_data_centers?page=1&region=austin' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK Β· recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects β€” the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed Β· autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API β€” it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: Baxtel SDK β€” bounded, re-runnable; every call capped."""
from parse_apis.api import Baxtel, DataCenterNotFound

client = Baxtel()

# List data centers in Austin, TX metro area
for facility in client.region("austin").list_facilities(limit=3):
    print(facility.name, facility.company, facility.status)

# Drill-down: get full details for the first facility
item = client.region("austin").list_facilities(limit=1).first()
try:
    detail = client.data_centers.get(slug=item.slug)
    print(detail.name, detail.power_mw, detail.status)
    print(detail.location.state, detail.location.metro)
    print(detail.latitude, detail.longitude)
except DataCenterNotFound as e:
    print(f"not found: {e.slug}")

# Navigate from summary to detail via .details()
summary = client.region("dallas").list_facilities(limit=1).first()
full = summary.details()
print(full.name, full.operator, full.year_built)
for site in full.nearby_sites[:2]:
    print(site.distance, site.name)

print("exercised: region.list_facilities / data_centers.get / summary.details")
All endpoints Β· 2 totalmissing one? Β·

List data center facilities in a geographic region (state or metro/city). Returns name, operating company, size class, operational status, and facility type for each facility. City/metro-level regions return complete facility tables; state-level regions return top facilities with a total count. Results are paginated at 50 per page.

Input
ParamTypeDescription
pageintegerPage number for paginated results. Each page returns up to 50 facilities.
regionrequiredstringRegion slug identifying the geographic area (e.g. 'austin', 'dallas', 'houston', 'texas'). Use city/metro slugs for complete listings.
Response
{
  "type": "object",
  "fields": {
    "page": "current page number",
    "region": "display name of the region",
    "facilities": "array of facility summaries with name, slug, company, size, status, type",
    "region_slug": "slug used in the request",
    "total_pages": "total number of pages",
    "total_in_table": "number of facilities listed in the HTML table",
    "total_in_region": "total number of facilities in the region (from map data)"
  },
  "sample": {
    "data": {
      "page": 1,
      "region": "Austin",
      "facilities": [
        {
          "name": "LOGIX Austin (1905 E 6th)",
          "size": "Small",
          "slug": "logix-austin-1905-e-6th",
          "type": "Carrier",
          "status": "Operational",
          "company": "LOGIX Fiber Networks"
        },
        {
          "name": "CyrusOne Austin I",
          "size": "Small",
          "slug": "cyrusone-austin-i",
          "type": "Carrier-Neutral",
          "status": "Operational",
          "company": "CyrusOne"
        }
      ],
      "region_slug": "austin",
      "total_pages": 2,
      "total_in_table": 94,
      "total_in_region": 94
    },
    "status": "success"
  }
}

About the πš‹πšŠπš‘πšπšŽπš• API

The πš‹πšŠπš‘πšπšŽπš• API on Parse exposes 2 endpoints for the publicly available data on πš‹πšŠπš‘πšπšŽπš•.πšŒπš˜πš–. Calls return JSON over HTTPS and are billed per successful response.

Pin a release with the API-Snapshot-Version header so canonical updates don't silently change your contract.