Cambridge 311

In the Ingest UI under Connectors → Cambridge 311, no credentials are required — just activate the connector.

Anonymous access works fine, but Socrata throttles unauthenticated traffic from a shared per-source-IP pool. A free Socrata app token grants a higher, dedicated quota — worth adding if you run heavy or frequent refreshes.

1. Go to data.cambridgema.gov/profile/edit/developer_settings and sign in (or create a free account).
2. In the App Tokens section, click Create New App Token, give it a name (e.g. Ingest), and save.
3. Copy the value in the App Token column (about 25 characters). Do not use the Secret Token — that is a separate credential this connector does not use.
4. Paste it into the Socrata app token (optional) field when you configure the 311 Service Requests endpoint.

The token is sent as the $$app_token query parameter. Leave the field blank for anonymous access. Important: an incorrect token makes requests fail with HTTP 403 — paste a valid token or leave it blank. (Socrata app tokens work across Socrata portals, so the same token can also serve the Somerville 311 connector.)

Ingest reads the dataset through Socrata and dispatches at 5 requests/second. Unauthenticated traffic draws from a shared pool throttled by source IP — ample for this dataset's refresh cadence — and the optional app token above raises that limit.