HTTP Status Codes

HTTP Status Codes

The following table shows the HTTP status codes and, if appropriate, additional subcodes, common to many Netflix API resources. In addition to the codes, the table shows the accompanying status messages. Note that some of the same status codes may have different messages. The status message correlates with the specific resource.

Code Subcode Applies to… Status Message
200   All resources n/a. The resource's representation is returned in the response.
201   POSTs Resource created
201 640 POSTs to users/user_token/queues/instant Only some titles in the set were added.
304   All resources Resource not modified
400   All resources parameter name is invalid
400   POSTs to users/user_token/queues/instant

Cannot move a series parent title

Invalid format for this user
400 120 All resource collections Query parameter max_results must be a positive integer.
400 130 POSTs to users/user_token/queues/instant Title not found or not available
400 620 POSTs to users/user_token/queues/instant Title is saved; cannot move it
400 650 POSTs to users/user_token/queues/instant Queue is too large
400 660 POSTs to users/user_token/queues/instant Invalid title format
400 690 POSTs to users/user_token/queues/instant Title currently at home
401   All resources

Access token is invalid

Access token validation failed

User ID is invalid

User ID access token mismatch
401   All feeds

Bad feed token

User not found

Mismatch between user token and feed token

Token resource mismatch
401   Login resources

Authorization failed

User must accept terms of use.
401   OAuth and access token resources

Expired or bad request token

Missing Required Consumer Key

Application name undefined

Unable to find or verify access token credentials

Application name mismatch

Consumer key mismatch
401   All resources Invalid signature
403

 

   All feeds Invalid feed token
404   All resources Resource not found
412   All resources Precondition failed. Resource has been modified.
412 710 users/user_token/queues/instant Title already in queue
422   users/user_token/ratings/title/actual Title has already been rated
500   All resources Internal error

version 5 as of 8 months ago by David Gross

6 Comments

  1. Doug – 2 years ago

    I've recently run into a status code not defined by this table: <status_code>405</status_code>

    The status code is returned as a response to an "https://api-user.netflix.com/oauth/login" request. The request is:

    https://api-user.netflix.com/oauth/login
    ?application_name=<myApp>
    &oauth_token=jfafgrb3cr5mdf5gtx8ht3d4
    &oauth_consumer_key=k4bghqddunxytt5x8p3qx9bf
    &oauth_callback=http://<myServer>/my/path/?request_token=jfafgrb3cr5mdf5gtx8ht3d4
    &request_token_secret=<mySecret>
    &oauth_timestamp=1260481210
    &oauth_nonce=4RiQMA
    &oauth_signature_method=HMAC-SHA1
    &oauth_signature=N%2B2Swwj2eWf%2Flg1wgzrHrjcA3cY%3D

    This has happened twice so far. It seems to be intermittent. After the first occurrence, I tried again and the api call succeeded.

    Any thoughts?

  2. eddiewebb – 2 years ago

    I am seeing an unknown subcode 710, with status code of 412
    - disc already exists in queue.

    Please update :)

  3. krishman – 1 year ago

    what about african movies, is it included for viewing?

  4. krishman – 1 year ago

    is it possible to sent african movies from this site www.bunibuni.com to netflix?

  5. Edward Petersen – 7 months ago

    I'm getting a status code of 403 when attempting to expand the person details on each member of a cast. The content just shows this:

    403 Developer Over Qps

    ... anyone know what this means? By the way, the return is inconsistent, sometimes it happens on cast member 2 of 6, sometimes on 3, sometimes on 4. But I never get through the whole cast, always an error.

  6. Edward Petersen – 7 months ago

    Just wanted to post again, since I was able to find the reason for my issue ...

    In the post above where I was getting the 403 error when attempting to expand the person details on each member of a cast, it was because the cast had 7 members in it and I was making my calls too quickly and hitting the developer limit of 4 calls per second.

    So, until the batch processing is live and works, I (and anyone else who might have the same issue) will need to throttle our calls.

    But if this table is attempting to be complete, it might want to have an entry in the 403 area for hitting the call limit.

Please sign in to post a comment.