Business search
/api/directorySearch published businesses by name, service or location. Use the returned slug to read a profile.
Developer Center
Find a business, read its public profile, and connect your application to a shared business identity.
Run a small search, choose a returned slug, then request its business profile.
curl --fail-with-body \
'https://directory.websdocs.com/api/directory?limit=3&page=1' \
-H 'Accept: application/json'/business/{slug}.jsonStart with these public read endpoints. The deployed OpenAPI document is the reference for the running API.
/api/directorySearch published businesses by name, service or location. Use the returned slug to read a profile.
/business/{slug}.jsonRead one published business identity. Replace {slug} with a slug returned by Directory search.
/api/homepageRead published, registry-verified and country counts from the scheduled Metrics snapshot.
/api/categoriesRead approved category slugs. Continue using nextCursor as the next request’s after value.
/.well-known/asg-directory.jsonFind machine-readable Directory entry points and discovery links.
/api/globeRead the globe payload when building a map. It can be larger than a summary; use /api/homepage for counts.
Migrating an older integration? /api/locations and /api/activity are retired. Filter business search by country.
No requests run automatically. This playground allows selected public GET routes only.
Ready when you are.
Choose a request path to generate an example.Browser integrations depend on the API’s CORS policy. If access is blocked, test from your server.
No request yet. Start with a small result set. You can inspect the response here without leaving the page.
Manual requests · 20-second timeout · 1 MiB display limit · no background refresh
Keep queries small, respect freshness, and distinguish published evidence from ownership or agent availability.
Business search accepts q, country, city, category, page and limit. Start at page 1.
Follow pagination.hasNext. Do not assume a total is exact unless pagination.totalExact confirms it. Page-size limits are set by the server.
Categories use a cursor: pass returned nextCursor as after. Use category slugs from the API.
/api/homepage returns the three homepage counts.
Check generatedAt and available delivery fields. Keep null as unknown; do not turn it into zero. Respect cache headers and avoid rapid polling.
Check the HTTP status before reading a success payload. Handle missing profiles, unavailable snapshots and upstream failures.
If you receive HTTP 429, honor Retry-After when supplied. For transient failures, use capped backoff with jitter. Do not repeatedly retry invalid requests.
This page does not promise a fixed rate limit or uptime SLA. Inspect current responses and contact support for sustained integration needs.
Registry verification, owner claims and operational agents are different signals. Treat each field according to its contract.
Read a business profile first. Follow returned gatewayDiscovery.urls; do not guess a gateway identifier from a Directory slug.
confirmed_live reflects a previous check, not guaranteed availability. Supported interactions may require separate authorization or credits. Explore the AI network ↗
Listing submission, claims, corrections and Website Audit use separate workflows. They can create records or trigger processing, so this playground does not run them. See List Business, Claim Business, Corrections and Website Audit. Public reads do not grant permission to manage a business.
Use the specification for the full API surface and discovery documents for published entry points.