PREDIK Data-Driven

PREDIK Location Intelligence & Foot Traffic Data API

Partner-delivered, contact-sales data API that serves PREDIK's enriched location-intelligence products - POI data, aggregated foot-traffic and mobility data, company and commercial-area intelligence, and socio-demographic enrichment. PREDIK lists REST API, SOAP API, and Feed API (alongside S3-bucket) as delivery channels, with output in JSON, CSV, or SQL. No public developer portal, base URL, authentication scheme, or endpoint reference is published; access, schema, and coverage are negotiated per engagement. Endpoints are not modeled because no public API documentation exists (endpointsModeled=false).

GitHub

Documentation

📖
Documentation
https://predikdata.com/location-intelligence-solutions/

Other Resources

🔗
Listing
https://datarade.ai/data-providers/centralamericadata/profile
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/predikt-ai/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
aid: predikt-ai:predikt-ai-location-intelligence-data-api
name: PREDIK Location Intelligence & Foot Traffic Data API
tags:
- Location Intelligence
- Foot Traffic
- POI Data
- Data Enrichment
- Web Intelligence
- Company Data
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://predikdata.com/location-intelligence-solutions/
properties:
- url: https://predikdata.com/location-intelligence-solutions/
  type: Documentation
- url: https://datarade.ai/data-providers/centralamericadata/profile
  type: Listing
description: Partner-delivered, contact-sales data API that serves PREDIK's enriched location-intelligence
  products - POI data, aggregated foot-traffic and mobility data, company and commercial-area intelligence,
  and socio-demographic enrichment. PREDIK lists REST API, SOAP API, and Feed API (alongside S3-bucket)
  as delivery channels, with output in JSON, CSV, or SQL. No public developer portal, base URL, authentication
  scheme, or endpoint reference is published; access, schema, and coverage are negotiated per engagement.
  Endpoints are not modeled because no public API documentation exists (endpointsModeled=false).