Local Business Listings Submission API by Listings API

Submit, manage and distribute accurate business listing data across 50+ listing sites: the search engines, maps, GPS/voice assistants and directories people use to find local businesses, all from one API with no code required.

This Actor wraps the full REST API. Pick an operation, add your parameters, run it, and the results are saved to the dataset. Keep every business's name, address, phone, hours, categories and photos consistent everywhere. That consistency is the foundation of local SEO, map-pack visibility and customer trust.

What you need

A Listings API account and an API key. Create one at https://listingsapi.com. You use your Listings API key, so the Actor acts as you and respects your plan's limits.

Input

Field	Required	Description
apiKey	Yes	Your Listings API key (stored as a secret).
operation	Yes	The endpoint to call. Pick from the dropdown (locations, listings, posts, reviews, analytics).
pathParams	No	Values for path placeholders, e.g. { "locationId": "123" }.
query	No	Query-string parameters, e.g. { "limit": 50 }.
body	No	JSON body for write operations (create/update). Ignored for GETs.
paginate	No	For list endpoints, follow pageInfo.hasNextPage and collect every page.
maxItems	No	Stop after N items across pages (0 = no limit).

Results are written to the dataset, one row per item, and can be exported as JSON, CSV or Excel.

Examples

List locations

{ "apiKey": "<your key>", "operation": "allLocations", "query": { "limit": 50 }, "paginate": true }

Get a location's photos (path parameter)

{ "apiKey": "<your key>", "operation": "mediaFilesOfLocation", "pathParams": { "locationId": "123" } }

Create a location (write, JSON body)

{
  "apiKey": "<your key>",
  "operation": "createLocation",
  "body": { "input": { "name": "Acme Dental", "description": "...", "subCategoryId": 743, "countryIso": "US", "city": "Austin" } }
}

The exact body and query shape for each operation is in the Listings API reference. This Actor forwards them as-is.

Output

List responses are unwrapped into individual dataset rows. Non-2xx responses stop the run and are reported cleanly (status, error code and message), with the full response saved as one { "_error": true, ... } record for debugging.

Docs & support

Full endpoint reference and guides: https://docs.listingsapi.com. More info: https://www.listingsapi.com