◉ PermitPost
PRIVATE PERMIT WORKSPACE

Welcome back

Sign in to continue to your permit mailing workspace.

First run creates your administrator account. Passwords are stored as salted hashes.
◉PermitPost
PPLocal workspacePrivate on this computer
MAILING WORKFLOW
DATA TOOLS
Source CSV remains unchanged.
Assessor checks are recorded with reviewer and date.
PermitPost / Overview
LOGIN PROTECTED
LOS ANGELES · PERMIT MAILING WORKFLOW

Overview

Explore the permit source, apply filters, and prepare a traceable mailing list.

Source coverage

October update values retained from the uploaded CSV.

RAW DATA

Workflow

Permit issuance and construction activity are separate facts.

i
Issued does not mean construction started.

The master list keeps source status as recorded. Assessor match means a reviewer compared the permit address against the Assessor Portal and entered the displayed address.

Permit status in source file

Counts are not mailing eligibility decisions.

Filter permit records

Combine fields to create the candidate set for your mailing.

Permit records

Permit addressPermit / APNType & useStatusIssue date · valueLADBS updateAssessor check
1 / 1

Weekly LA permit master preview

Checks the official city dataset each Monday at 9:00 AM Pacific and reports eligible records that are missing from your master list.

Open city dataset ↗

City API imports are free. New records are deduplicated by permit number and marked Pending LADBS enrichment. This step does not call ZenRows.

Schedule a public page scrape

Jobs call ZenRows from this server. API credentials stay out of the browser.

Only public HTTPS pages are accepted. Scraped content is saved for review; it does not silently change the permit master.

ZenRows connection

The key is masked and saved on the VPS. A test request to example.com may use a ZenRows credit.
🔒
Private server-side storage

PermitPost saves the API key in a restricted file on the VPS. The key is never returned to this page or written to application logs.

FlameProxies connection

API key not configured

Saved on the VPS only. This API key can also make purchases, so PermitPost restricts its own API calls to account reads and proxy generation.
🔒
Key stays on the server

The key and generated proxy credentials are never returned to the browser or written to logs. PermitPost does not call purchase or add-data endpoints.

Test one LADBS permit page

Generates one proxy from an existing package, then requests the saved sample permit detail page once.

This sends one request through the selected trial pool and uses a small amount of its bandwidth. It does not purchase bandwidth.

Scheduled jobs

Run history includes status and a short content preview.

PERMIT RECORD