List the stations in a placement.
GET/placement/:placement_id/station
Returns a page of the stations in the given placement that this client
may play. Behaves like GET /station, with the placement named
explicitly instead of defaulting to the app's default placement. The
placement must belong to the credentials making the request, otherwise
the response is a 404.
Naming the offline placement returns its offline stations, which GET /station never lists. They arrive without expire_date: that property
is rendered only by POST /session.
Stations are filtered before paging, so total is the number of
stations that matched the filters, not the number in the placement.
By default the list is also filtered by the country the caller's IP
address resolves to. Pass and_countries/or_countries to filter by
explicit countries instead, or all_countries to disable the country
filter entirely.
Request
Responses
- 200
- 400
- 401
- 404
- 429
- default
The page of stations that matched the filters.
missingParameter (code 16) — Missing client id, no client_id
was supplied.
invalidParameter (code 15) — invalid page number (non-numeric
page), invalid per_page value (non-numeric per_page), or
could not parse that JSON query (a q starting with { that is
not valid JSON).
Credentials were missing or invalid. The response carries
WWW-Authenticate: Basic realm="Feed.fm".
Response Headers
The authentication challenge. Always Basic realm="Feed.fm".
Basic realm="Feed.fm"missingObject (code 17) — No placement with the given id is connected to this application: there is no such placement, or it
belongs to different credentials, or it has no stations for this
client and location.
The server judged the rate of requests from these credentials to be excessive and is refusing them for a time. The block lasts 30 seconds from the request that tripped it. Requests made during the block are refused and do not extend it.
The threshold is not published, and is not part of this contract. The threshold is also tuned from time to time.
The response carries a Retry-After header giving whole seconds until
the block clears. Wait at least that long. It says when to come back,
not what rate to aim for, and retrying sooner simply meets the block
again.
This exists to stop abuse, and a well-behaved client should not reach it; if yours does, the fix is to reduce your request rate rather than to retry on a timer. If you believe your application needs a rate that trips it, contact Feed.fm rather than working around it.
An error occurred.