General Notes » History » Version 28

« Previous - Version 28/40 (diff) - Next » - Current version
Seulki Lee, 01/03/2014 09:15 AM

General Notes


SSL only

We require that all requests are done over SSL.

UTF-8 encoding

Every string passed to and from the Bricklink API needs to be UTF-8 encoded.

Date format

All timestamps in the API are strings in ISO 8601 format:


Rounding policy

For all financial calculations, BrickLink API uses values with 4 decimal places. Any values that has greater precision will be rounded up to the 4 places.

Base URL

All URLs referenced in the documentation have the following base:


  • OAuth parameters should be included in every request.
  • In the PUT or POST, you represent the resource object you wish to update as form of urlencoded JSON.
  • Optional parameters (ex pagination info) should be provided as query string with urlencoded form.


BrickLink API supports returning resource representations as JSON with the following structure:

Property Name Value Description Notes
meta Object Extra information about the response
meta.code Integer API result code. (2xx if successful, any other number otherwise) Result Code
meta.message String More granular information about the result
meta.description String Detailed description of the result
data Object Requested information. Depending on the type of request you made, the HTTP response message body may be empty (typically for DELETE messages), but if the body is not empty, it will always be JSON object.
    "data": {

Add picture from clipboard (Maximum size: 24.4 MB)