Baton Rouge 311

governmentbuilt on requestauth: None

Sync Baton Rouge 311 service requests into your warehouse.

The Baton Rouge 311 connector syncs Baton Rouge service requests into analytics-ready tables in your data warehouse. Pull citizen requests for service, the department that owns each one and its open or closed status from the Open Data BR Socrata API, with Ingest handling pagination and retries so the tables stay current.

Baton Rouge 311 is not a certified connector yet. Ingest authors one from the vendor's API documentation when a customer asks for it, runs it against the real API, and only then lists it as deployable. Request it and it moves up the queue.

What you can sync

Ingest lands the following Baton Rouge 311 data in your warehouse or lake, each as its own table on the schedule you pick:

  • Service requests
  • Request status and closure
  • Request types
  • Location and district

Authentication

None. The Baton Rouge 311 API is public and needs no credential.

Credentials go into a form, never into a chat, and are held in a secret store under your own path. Only the key NAMES ever reach the control database.

Resources