Your rides,everywhere riders look.

Every D76 API key needs approval first, read keys included. Tell us what you're building, and we'll review it. Ask from your API keys page; once it's approved, make a key there. Every request goes to https://api.d76riders.com/v1 with your key as a bearer token. Keep it on your server, never in a browser or an app, and list upcoming events:

curl "https://api.d76riders.com/v1/events?state=TN&type=BIKE_NIGHT,GROUP_RIDE&limit=10" \
  -H "Authorization: Bearer $D76_API_KEY"

A key belongs to your D76 account and can never do more than you can on the site. It's shown once; D76 keeps only a fingerprint of it. Revoke one any time and anything using it stops at once.

• events:read

  Read events

  Upcoming public events, by area, type and date, and your own events.

• events:write

  Manage events

  Post, edit and cancel events you organize. Needs two-step sign-in.

• crews:read

  Read crews

  Public crews, their events and public members, and the crews you run.

• crews:write

  Manage crews

  Edit the details of crews you lead and post their events. Needs two-step sign-in.

• shops:read

  Read shops

  Shop listings as the site shows them, their review ratings and backed rides, and the shops you own.

• shops:write

  Manage shops

  Update hours, contact details and listing details of shops you own, back rides, and reply to reviews. Needs two-step sign-in.

Every key needs approved API access and a confirmed email. Managing events, crews and shops also needs two-step sign-in on your account. Both are checked on every call, so withdrawn access stops every key at once, and turning two-step sign-in off stops a write key straight away.

Keys starting d76_test_ read the same data. An event a test key creates is a draft only you can see, a test key can change only those drafts, and a crew or shop change is checked without being saved (dry_run: true). Wire up your tool without a test ride landing on anyone's calendar.

Send times in ISO 8601 with the IANA time_zone they're in. A group ride needs a kickstands-up time. Before your first event, accept the Organizer Agreement once on the site. Send an Idempotency-Key so a retry never posts twice.

curl -X POST "https://api.d76riders.com/v1/events" \
  -H "Authorization: Bearer $D76_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: toy-run-2026-12-12" \
  -d '{
    "title": "Toys for Tots Ride",
    "type": "CHARITY",
    "time_zone": "America/Chicago",
    "starts_at": "2026-12-12T10:00:00-06:00",
    "meet": { "name": "Liberty Park", "address": "1188 Cumberland Dr, Clarksville, TN" },
    "excerpt": "Bring a new, unwrapped toy."
  }'

The verified owner of a listing can change it. Hours and phone go live at once; anything else waits for our team's review, as on the site (review: true). Only the days you send in hours change.

curl -X PATCH "https://api.d76riders.com/v1/shops/your-shop" \
  -H "Authorization: Bearer $D76_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "hours": { "sat": { "open": "09:00", "close": "15:00" }, "sun": null } }'

Every error has the same shape. The code is stable; the message is a sentence you can show a person.

{
  "error": {
    "code": "forbidden",
    "status": 403,
    "message": "This key doesn't have the events:write scope."
  }
}

Codes: unauthorized (401), forbidden (403), not_found (404), invalid_input (400), conflict (409), rate_limited (429), unavailable (503).

Lists take limit (1–100, default 25) and cursor, and answer { data, next_cursor }. Pass next_cursor back as cursor for the next page; it's null on the last one.

Send an Idempotency-Key (8–100 letters, digits, - or _) on POST and PATCH. A retry with the same key gets the first answer back for 7 days, marked Idempotent-Replayed: true. One still running gets 409; the same key on a different request gets 422.

Per key: 600 reads and 60 writes a minute. Every answer carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (seconds); a 429 adds Retry-After. Writes also stay under the site's own limits for your account.

Every field and answer is in the API reference, generated from the same contract the API runs on (https://api.d76riders.com/v1/openapi.json).

Anything about a rider that isn't already public on D76: no RSVP lists, messages, live locations, ride logs, Emergency ID, Rider Assist or email addresses. Counts appear only where the site already shows them.