Godcaster · API Overview · For Station Teams

Everything your station broadcasts, available as data.

Your Godcaster dashboard already holds your players, your programs, your episodes, and your listening numbers. The Godcaster API lets your website, mobile app, lobby screen, or newsletter tool pull that same information automatically — no copying and pasting, no manual updates. And it now works in both directions: the same key that reads your data can also manage your lineup, colors, artwork, and settings. This guide explains what a standard station API key can do, and what a radio station might do with it.

A quick word on how it works: every request is a simple web address. Your station's API key — found in your Godcaster dashboard — goes along with the request to prove it's you. The answer comes back as structured data (JSON) that any web developer, app builder, or no-code tool can read. Hand this guide to whoever runs your website and they'll know exactly what to do with it.

Your key works for the players your station owns. You can't pull another station's private information, and nobody can pull yours. The same rule holds for changes: only your own key can modify your players.

Part One · Pulling data out What your website, app, or reports can read from Godcaster.

88.1

Player data — your full on-air lineup

The complete picture of one player, in a single request.

A "player" in Godcaster is the curated lineup you present to listeners — the shows you carry, in the look and order you chose. This request returns everything about one player: its name, description, and artwork; your brand colors and styling; your location and timezone; your website and support links; and every program on the player, each with its 50 most recent episodes — titles, artwork, descriptions, publish dates, durations, and the audio itself.

GET https://api.godcaster.fm/api/v1/player/{player_id}/data/json

Your player's ID number is shown in the dashboard.

What comes back

  • Station player name, description & artwork
  • Your brand colors and player styling
  • Location, timezone & website
  • Donation / support links per program
  • Every program, with its 50 latest episodes
  • Episode audio files, durations & publish dates

A station might use it to

  • Power a "Listen" page on the station website that updates itself
  • Show "latest episodes" on the homepage, always current
  • Drive a lobby or studio screen showing what's on
  • Feed a station mobile app without re-entering shows

ON AIRLive streams and live episodes carried on your player are included and flagged as live, so your website can show a "live now" indicator the moment you go on air.

90.7

Listening stats — this month's numbers

The same figures as your dashboard's stats page, ready for reports.

This request returns the current month's listening activity for one of your players: how many plays, downloads, shares, page visits, follows, and support clicks you've received — plus breakdowns by episode, by program, by listener location, by device, by traffic source, and by podcast app.

GET https://api.godcaster.fm/api/v1/player/{player_id}/stats/json

What comes back

  • Plays, downloads & RSS downloads this month
  • Shares, visits, follows & support clicks
  • Top episodes and top programs
  • Where listeners are located
  • Devices, traffic sources & podcast apps used

A station might use it to

  • Build a monthly board or committee report automatically
  • Send underwriters and sponsors real listening figures for their shows
  • Spot the most popular programs to promote them harder
  • See which towns are tuning in and plan outreach
94.1

Program data — one show, up close

Details and recent episodes for a single program.

Where player data gives you the whole lineup, this request zooms in on one program: its title, host, description, artwork, website, and donation link, along with its 50 most recent episodes. It's the right choice when a single show deserves its own spotlight.

GET https://api.godcaster.fm/api/v1/program/{program_id}/data/json

What comes back

  • Program title, host & description
  • Program artwork & website
  • Donation / support link
  • The 50 latest episodes with audio

A station might use it to

  • Give a flagship show its own page on the station site
  • Embed a "latest episode" box for one program
  • Auto-fill the newsletter with a show's newest episode
96.9

Collections & channels — your grouped lineups

For stations that organize players into themed groups.

If your station groups players into collections — by genre, by language, by ministry, by sister station — these requests return those groupings so your website can mirror them. There are three flavors, from full detail to a fast, lightweight listing:

GET …/api/v1/player/{player_id}/collections/json
GET …/api/v1/player/{player_id}/channels/json
GET …/api/v1/channel/{channel_id}/data/json

All three begin with https://api.godcaster.fm — shortened here to fit.

What comes back

  • Collections — every collection you own, each with its programs and recent episodes
  • Channels — the same listing without episodes: small and quick to load
  • Channel data — the full detail of one channel, like player data

A station might use it to

  • Build a program directory organized the way you organize it
  • Offer a browse-by-category menu that stays in sync
  • Give each channel its own landing page

Part Two · Making changes The same key can now manage your players — every change takes effect right away, just like editing in the dashboard.

100.3

Lineup management — add, remove & reorder shows

Curate a player's program lineup without opening the dashboard.

These requests let your own tools manage what's on a player. You can list the current lineup in display order, add a program, remove one, or submit a complete new running order. When you add a program Godcaster doesn't know yet, it looks up the show's title, artwork, and details automatically — you only supply the program's ID number. There's a catalog search to find that number by name, and you can even create a brand-new player from scratch.

GET  …/api/v1/player/{player_id}/programs
POST …/api/v1/player/{player_id}/programs/add
POST …/api/v1/player/{player_id}/programs/remove
POST …/api/v1/player/{player_id}/programs/order
GET  …/api/v1/programs/search?query={show name}
POST …/api/v1/player/create

All addresses begin with https://api.godcaster.fm — shortened here to fit.

What you can do

  • List a player's programs in their display order
  • Add a program by its ID — details fill in automatically
  • Remove a program from the lineup
  • Submit a full new running order in one request
  • Search the podcast catalog to find programs
  • Create a new player (within your plan's limit)

A station might use it to

  • Run a seasonal lineup change across players in one script
  • Let your website's own admin page manage shows, no extra logins
  • Spin up a new player for a special event and stock it with shows
  • Keep player lineups in sync with your program schedule automatically

ON AIRLive-stream tiles on a player are protected: they can be reordered along with everything else, but adding or removing them stays in the dashboard's player settings screen.

103.9

Look & feel — colors, artwork & settings

Everything on the dashboard's player settings page, readable and writable.

Three groups of requests cover a player's appearance and behavior. Colors reads or updates the player's full color scheme — change one color or all seventeen, or reset the whole scheme back to the defaults. Image uploads new player artwork (JPEG or PNG, up to 4 MB). Settings reads or updates the rest: the player's title, layout style, how many programs and episodes to display, description, website, donation link, location, and toggles like the public directory listing and Open Mic. Change your player's location and Godcaster re-maps it and updates the timezone for you.

GET / POST …/api/v1/player/{player_id}/colors  ·  POST …/colors/reset
POST …/api/v1/player/{player_id}/image
GET / POST …/api/v1/player/{player_id}/settings

What you can do

  • Read or update any of the 17 scheme colors
  • Reset the color scheme to defaults
  • Upload new player artwork
  • Update title, layout, description & links
  • Change location — mapping & timezone update automatically
  • Flip toggles: directory listing, Open Mic & more

A station might use it to

  • Match the player to a website redesign in one call
  • Swap in pledge-drive artwork on schedule, then swap back
  • Update the donation link everywhere at once
  • Keep station details consistent across every player automatically

Good to know

Where your key lives
Your API key is in the Godcaster dashboard. Treat it like a station door code — share it with your web developer, not with the public.
How your developer sends it
The key goes in the request's Authorization header. That's the only setup there is.
How fresh the data is
Player, program, and collection responses may be up to about ten minutes behind your latest dashboard change — new episodes appear on your website within minutes, not instantly. Changes you make through the API take effect right away. Stats reflect the current month as gathered throughout the day.
Changes are checked before they land
Every update is validated the same way the dashboard validates it — a bad color code, an oversized image, or a malformed web address is politely refused with an explanation, and nothing changes until the request is right.
For your developer
A complete technical reference — every request with its exact fields, responses, and error cases — is available as a Postman collection. Ask us for it.
What it costs to use
Nothing extra. The API is part of your Godcaster service.
What's not in this guide
Godcaster also has administrative endpoints used internally for network-wide services. They require special credentials and aren't available to station keys, so they're not covered here.