Introduction
The KynectLocal API lets third-party developers read location data on behalf of franchise brands — enabling custom integrations, external dashboards, and data pipelines built around a brand’s location network.
When you’d use this
Section titled “When you’d use this”- You are an agency or developer hired by a franchise brand to build a custom integration
- You need to pull location data into an external system (CRM, analytics platform, custom website)
- You are building a tool that reads KynectLocal location profiles for display or processing elsewhere
Who the API is for
Section titled “Who the API is for”The KynectLocal API is intended for third-party developers — agencies, contractors, and technical partners working on behalf of franchise brands. It is not a tool for franchisees or brand admins to use directly; those users have the KynectLocal admin interface.
If you are a brand admin looking to connect KynectLocal to another platform, contact your account team about available integrations before building a custom API solution.
What the API does in v1
Section titled “What the API does in v1”The v1 API is read-only. You can retrieve data; you cannot create, update, or delete resources through the API.
Available in v1:
| Resource | What you can do |
|---|---|
| Locations | List all locations for a brand; retrieve a single location’s profile data |
Write endpoints, webhooks, and additional resources are planned for future versions.
Base URL
Section titled “Base URL”All API requests go to:
https://api.kynectlocal.comThere is no versioning prefix in the URL — the current version is implied. Breaking changes will be communicated with migration guides before they take effect.
Related
Section titled “Related”- Authentication — how to get an API key and authenticate requests
- Rate Limits — request limits and how to handle 429 responses
- Errors — standard error envelope and common error codes
- API Reference — full endpoint documentation