Report how far into a play the client has listened.

POST 
/play/:play_id/elapse

Periodically report the elapsed playback position of a started play, so that the correct duration is reported for royalties if the client disappears mid-song. Typical clients send this every 10 to 30 seconds, and again when playback is paused or stopped.

seconds is required.

Request

Responses

200

The elapsed time was accepted.

400

missingParameter (code 16) — no client_id was supplied, the seconds property was absent (Missing 'seconds' parameter), or the play id in the path is missing or non-numeric (Invalid or missing play id.).

invalidParameter (code 15) — seconds was present but did not parse as a number.

401

Credentials were missing or invalid. The response carries WWW-Authenticate: Basic realm="Feed.fm".

Response Headers

WWW-Authenticate
The authentication challenge. Always Basic realm="Feed.fm".
Example: Basic realm="Feed.fm"

404

missingObject (code 17) — no such play.

429

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.

default

An error occurred.