Mint a new client.
POST/client
Creates a brand new client and returns its id. This endpoint is useful
for server-side processes that want to create a new feed client id, but
aren't going to immediately use it for music playback. Generally,
clients should use POST /session to create new client ids.
This endpoint always mints a new client. There is no way to use this
call to look up, reuse or adopt an existing id; send the client_id on
POST /session for that.
Request
Responses
- 200
- 401
- 429
- default
A new client was created. client_id is the new id.
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"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.