Driffle Seller API
  • Driffle Seller API
  • Guide
    • Getting Started
    • Monitoring Your Competition
  • FAQ
    • Cannot use the API, it throws 401/403/404 errors
  • Reference
    • Automate Your Stock with "Declare Stock"
    • API Reference
      • Products
        • Get Products List
        • Get Single product
        • Get Product Commission
      • Competition
      • Offers (Auction)
        • Offers List
        • Get Single Offer
        • Update Offer Price
        • Enable/Disable Offers
        • Create a new offer
        • Update Offer
        • Bulk Update Offers
      • Manage Inventory/Stock
        • Declare Stock
        • Upload Stock
        • Inventory Actions
        • Fetch a single Key
      • Transactions
        • Get Transactions List
        • Get a Single Transaction
      • Dashboard Stats
      • Regions
      • Platforms
Powered by GitBook
On this page
  • Reason for receiving "401" errors
  • Reason for receiving "403" errors
  • Reason for receiving "404" errors
  1. FAQ

Cannot use the API, it throws 401/403/404 errors

PreviousFAQNextAutomate Your Stock with "Declare Stock"

Last updated 1 year ago

Following the HTTP standards, you should know that:

  • 401 Unauthorized response code means that you are not authenticated (in simpler terms "not logged in").

  • 403 Forbidden response code means that you are not authorized to access your designated resource.

  • 404 Not Found response code means that the resource you are looking for does not exist.

Having that in mind during the usage of our API you might encounter these in multiple scenarios.

Reason for receiving "401" errors

The reason for getting 401 Unauthorized errors is simply because you did not provide or provided a wrong Bearer Authorization header (reference the section for additional details).

Reason for receiving "403" errors

One of the most common reasons for receiving a 403 Forbidden is that the issued access_token being used is not authorized to access an endpoint or an action is not allowed on the access_token.

Reason for receiving "404" errors

Make sure to use the right REST API endpoints:

Getting Access
https://services.driffle.com/api/seller/legacy/