Introduction
5 min
the pricemoov api is organized around rest our api has predictable resource oriented urls, accepts form encoded request bodies, returns json encoded responses, and uses standard http response codes, authentication, and verbs hosts the rest api lets you interact directly with pricemoov from anything that can send an http request all api access must use https the primary host is api pricemoov com for write and read operations format the entire api uses json encoded as utf 8 the body of post and put requests must be either a json object or a json array (depending on the particular endpoint) and their content type header should be set to application/json ; charset=utf 8 the body of responses is always a json object, and their content type is always application/json ; charset=utf 8 parameters unless otherwise stated, parameters must be passed in the url query string for get and delete requests in the request body for put and post requests parameters passed in the url must be properly url encoded, using the utf 8 encoding for non ascii characters furthermore, the plus character (+) is interpreted as a space (it’s, therefore, an alternative to %20) pagination default parameters for all get endpoints are offset limit type integer , default 0 , optional type integer , default 25 , optional errors the pricemoov api uses the following error codes error code meaning 400 bad request your request is invalid 401 unauthorized your api key is wrong 403 forbidden the entity requested is hidden for administrators only 404 not found the specified entity could not be found 405 method not allowed you tried to access an entity with an invalid method 406 not acceptable you requested a format that isn't json 409 conflict 410 gone the entity requested has been removed from our servers 429 too many requests you're requesting too many entities! slow down! 500 internal server error we had a problem with our server try again later 503 service unavailable we're temporarily offline for maintenance please try again later versioning the current version of the api is v1
