# Austin and Seattle Issued Building Permits

**Use case:** 

Returns 50 recently issued building permits, 25 from the Austin open data portal and 25 from Seattle, mapped to one set of fields. Each row has the permit number, type, description, status, issue date, project value, address, ZIP code and contractor where the city publishes it. Contractors and suppliers use it to find new projects. Change the cities, or add a date range, to reuse it.

## Input

```json
{
  "cities": [
    "austin-tx",
    "seattle-wa"
  ],
  "maxItemsPerCity": 25,
  "includeRaw": false,
  "maxItems": 50
}
```

## Output

```json
{
  "portalName": {
    "label": "Portal Name"
  },
  "permitNumber": {
    "label": "Permit Number"
  },
  "permitType": {
    "label": "Permit Type"
  },
  "description": {
    "label": "Description"
  },
  "status": {
    "label": "Status"
  },
  "issuedDate": {
    "label": "Issued Date"
  },
  "valuation": {
    "label": "Valuation",
    "format": "number"
  },
  "address": {
    "label": "Address"
  },
  "zip": {
    "label": "Zip"
  },
  "contractorName": {
    "label": "Contractor Name"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Building Permits Scraper: City Open Data, No Login Actor is ready to run with the inputs already set for "Austin and Seattle Issued Building Permits". [Sign up or log in](https://console.apify.com/create-task-from-example/yBdGCiJLqyguRSrlc) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Austin and Seattle Issued Building Permits" task

The Building Permits Scraper: City Open Data, No Login Actor will start running based on the input automatically. You can also change all the input fields, like cities and counties, results per city, and more, to match your specific use case.

### 3. Receive the "Austin and Seattle Issued Building Permits" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as portal name, permit number, permit type, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Austin and Seattle Issued Building Permits" task via API](https://apify.com/one_dollar_store/city-building-permits-scraper.md).

## About this Actor

This example demonstrates how to use [Building Permits Scraper: City Open Data, No Login](https://apify.com/one_dollar_store/city-building-permits-scraper.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/one_dollar_store/city-building-permits-scraper.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/one_dollar_store/city-building-permits-scraper.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).
