← Binfluencer

Binfluencer for councils

A simple guide to sending us your bin collection data.

Binfluencer shows residents which bin goes out next and reminds them the night before. Right now we read your published calendars. If you send us your data directly, residents get official dates straight from you, including holiday changes, and we stop reading your website. Fewer "when's my bin day?" calls for everyone.

Two ways to send your data

1. By spreadsheet

No technical work needed. Email us a spreadsheet and we'll load it for you. Send an updated one whenever your dates change.

What to put in it ↓

2. By API

Your systems send updates to us automatically. Four simple steps, and your team can have it running in an afternoon.

How it works ↓

The three things we need

Whichever way you choose, we need the same three things:

  1. Your bins: what each bin is called, its colour and how often it's collected.
  2. Your homes: each home's UPRN, address, postcode and which collection round it's on.
  3. Your dates: for each round, which bin is collected on which date.

Homes on the same round share one calendar, so you only send the dates once per round, not once per home.

Option 1: spreadsheet

One spreadsheet with three tabs. Excel, Google Sheets or CSV files are all fine.

Tab "Bins"

BinColourEvery how many days
Recyclingblue14
Generalgreen21

Tab "Homes"

UPRNAddressPostcodeRound
000125006743115 Alexandra Parade, DunoonPA23 8AWCOW_22

Tab "Dates"

RoundBinDate
COW_22Recycling2026-10-07
COW_22General2026-10-14

Email it to hello@lbysoftware.co.uk. Please write dates as year-month-day (2026-10-07) so nobody mixes up October and July.

Option 2: API

Before you start

https://iwjqwswwcxitbafaajic.supabase.co
  /functions/v1/api/v1

Authorization: Bearer bfk_your_key_here
Content-Type: application/json

Step 1. Tell us your bins

PUT /councils/argyll-bute/bin-types

{
  "binTypes": [
    {
      "code": "Recycling",
      "label": "Blue bin (mixed recycling)",
      "colour": "blue",
      "frequencyDays": 14
    },
    {
      "code": "General",
      "label": "Green bin (general waste)",
      "colour": "green",
      "frequencyDays": 21
    }
  ]
}

The code is the name you'll use for that bin in step 3.

Step 2. Tell us your homes

PUT /councils/argyll-bute/properties

{
  "properties": [
    {
      "externalId": "000125006743",
      "address": "115 Alexandra Parade, Dunoon",
      "postcode": "PA23 8AW",
      "routeKey": "COW_22"
    }
  ]
}

externalId is the UPRN and routeKey is the collection round. Up to 5,000 homes per request, so send big lists in batches.

Step 3. Send the dates for each round

PUT /councils/argyll-bute/routes/COW_22
    /collections

{
  "collections": [
    { "binType": "Recycling", "date": "2026-10-07" },
    { "binType": "General",   "date": "2026-10-14" }
  ]
}

This replaces every date for that round from the earliest date you send. So to make a change, just send the full, updated list again. Up to 2,000 dates per request.

Step 4. Check it worked

GET /councils/argyll-bute/status

Shows how many homes and rounds we hold for you, when you last updated, and any rounds that are running out of dates.

Trying it from the command line

curl -X PUT \
  "https://iwjqwswwcxitbafaajic.supabase.co/functions/v1/api/v1/councils/argyll-bute/routes/COW_22/collections" \
  -H "Authorization: Bearer bfk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"collections":[{"binType":"Recycling","date":"2026-10-07"}]}'

Good to know

If a request fails

CodeWhat it means
401The key is missing or wrong.
403That key belongs to a different council.
400 / 422Something in the data needs fixing, for example a bin name we don't know or a date like 2026-13-01. The reply lists exactly which items.

Want the full technical detail? Here's the OpenAPI specification, which your developers can load into most API tools.

Questions? We're happy to help your team get set up. Email hello@lbysoftware.co.uk.