GET v3/stock/:id

GET 
/v3/stock/:id

Retrieve one stock record.

The GET v3/stock/:id endpoint will return a specific stock record. Note that the endpoint returns information about a single stock record which will no longer exist once all products have been moved away from it. Stock is transient and may be moved around at any time. It is therefor recommended not to persist stock and id in your systems.

Including related resources

The endpoint also supports -to some degree- the inclusion of information of related resources. This option is provided to allow clients used to the v2 version of the stock endpoint to be able to use the v3 version more seemlessly. To get the details of related entities the include parameter must be added to the URI in the following way:

• GET {host}/v3/stock?include=stockLocation will return the stock with some stockLocation related details.

Note: inclusion of product has been deprecated.

Limitations of the GET v3/stock/:id

• Users are rate-limited to 1000 requests per hour on this service.

Request

Responses

200

OK

401

Unauthorized

403

403 Forbidden

The HTTP 403 Forbidden client error response status code indicates that the server understood the request but refused to process it. This status is similar to 401 Unauthorized, except that for 403 Forbidden responses, authenticating or re-authenticating makes no difference. The request failure is tied to application logic, such as insufficient permissions to a resource or action.

404

404 Not Found

A 404 Not Found response occurs when attempting to access a resource that cannot be found on the server. It indicates that the requested resource does not exist, either because it has been deleted, the URL is incorrect or because the endpoint has not been realized.

The following are common scenarios that may lead to a 404 Not Found response:

• Attempting to access an endpoint with an invalid or non-existent URL.
• Attempting to access an endpoint that has not (yet) been realized
• Requesting a resource that has been deleted or moved.

406

406 Not Acceptable

A 406 Not Acceptable response occurs when the server cannot provide a response that matches the client's requested format or content language for the requested resource. For instance, if a client sends an Accept header of text/html to an API endpoint that only supports application/json responses, the server would respond with a 406 Not Acceptable status code. This type of response is a required response for JSON:API compatible endpoints.

415

415 Unsupported Media Type

A 415 Unsupported Media Type response occurs when the server cannot process the request because the media type specified in the request is not supported for the requested resource. For example, if a client sends a request with a Content-Type header of application/pdf to an API endpoint that only supports application/json (the only valid media type for JSON:API), the server would respond with a 415 Unsupported Media Type status code. This type of error-response is a required for JSON:API compatible endpoints.

429

429 Too Many Requests

The request could not be completed because of a rate limit violation.