Revoke an access token.

DELETE 
/access_token/:access_token

Revokes the given access credentials immediately. The request must be authenticated with the consumer credentials that created the token; a consumer may only revoke its own access tokens.

Request

Responses

200

The access token was revoked.

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"

403

forbidden (code 6) — Access credentials are not owned by the provided consumer credentials: the token exists but belongs to a different consumer.

404

missingObject (code 17), from two checks made in this order:

• No such access token — no credentials match the token in the path.
• No such consumer token — the credentials the request authenticated with are not consumer credentials. POST /access_token answers the same condition with a 403 forbidden instead; the asymmetry is intentional, so handle both.

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.