To access the MarketRock APIs, you mustrregister as a developer and accept our data usage terms: register as a developer
\n\nThen, if you don't yet have a MarketRock account with which to connect via API (e.g. the MarketRock account of one of your customers), you can create one for free here: Register a MarketRock account.
\nFor complete integration, we suggest following the following steps:
\n\nTo make calls you need to have an access token. The procedure for obtaining one is shown in the chapter \"How to obtain an access token\".
\n\nFolders allow you to organize products. You will probably just need the \"Create\" call. Keep in mind that the folder describes the element of discrimination for, for example, listing products on eBay. That is, products in the same folder will generate listings in the same eBay category.
\n\nOnce you have created the folders, create products inside them using the \"Create\" example (perhaps starting with the \"Create base\"). Before proceeding with this call, however, you need to create price lists on MarketRock. Once you have created them, download the IDs you will need to create the product by running the \"Get all pricelists\" call.
On the products you can (and probably have to) specify:
Once you have managed to create the products, make some basic calls to synchronize prices and quantities of the products that are changed. This is the most operationally important call. To do this, simply look at the \"Update\", obviously specifying only the PricingRows and Availabilities element. I remind you that if you do not specify a price, it will then be removed (causing it to be removed from the market to which that price list is connected).
\n\nOnce the products are on MarketRock, it will then be MarketRock's task to publish them on the various markets, depending on the customer's configurations. At this point, while you continue to update quantities and prices, MarketRock will accept the orders. In this case the general flow is as follows:
At MarketRock we care about the privacy of our users, so we want only applications authorized by our users to be able to access their data and until our users decide to revoke access. The result, once you have been authorized by one of our users, is our receipt of an Authorization Token (called AuthToken) which will allow you to operate on behalf of the client on his MarketRock account.
\n\nThe process for obtaining an authorization token is based on OAuth (if you don't already know, OAuth is a now standard protocol that we decided to implement to solve this need, for more info I recommendthis resource).
\n\nNormally, for these integrations, we use the flow called \"Authorization Code Flow\". This flow consists of these steps:
\n\n< li>if the user accepts, we redirect the user to a page that is on your server, passing a temporary code (usable only once and expiring in 5 minutes)< li>with this code (called code) make a call to our server, authenticating with a pair of keys called client_id and client_secret.
When we bring your application into production, we will issue you a pair of credentials (client_id and client_secret) that will be known only to us and must be kept secret. In this phase I will provide you with a pair of temporary keys, to test the authorization flow directly in Postman.
\n\nThe access token you will receive is valid for 1 day (86400 seconds), for security reasons. If you request it (in point 2) you will also be able to obtain a renewal token (called refresh_token) at the same time as the access token (in point 7). With this token you will be able, without obtaining the user's consent, to obtain a new access token that will allow you to continue operating on behalf of the customer. I don't have to tell you that this token must be stored with the utmost care!
\n\nCALLBACK_URL will be the URL to which the user will be directed, after giving us the ok. It will be agreed by us and cannot be modified by you independently. For this demo you can use https://www.getpostman.com/oauth2/callback
SCOPES are the permissions you want to ask the user. You can concatenate more than one, separating them by a + character and you can choose between:
at this point, from resource code that responds to CALLBACK_URI, you can start a call to the MarketRock token endpoint, i.e. https://auth.edock.it/identity/connect/token. Such a call must contain, passed as the body of the message in mode x-www-form-urlencoded:
If everything works as it should, you will receive an access_token in return, with the expiry date expressed in seconds.
\n\nThis whole discussion may seem very complicated and convoluted. I would like to underline that you will certainly find, whatever the language you use, numerous libraries that will allow you, once you have specified the parameters (client_id, client_secret, callback_uri, etc. etc.), to obtain the various tokens you will need. I preferred to illustrate everything to show you what happens behind the scenes!
\n\nIf, among the scopes, you asked for \"offline_access\", when you have completed the authentication round, in addition to the access_token, you will also receive a refresh_token. This refresh_token allows you to generate a new access_token, with the same scope as the previous one, without having to ask the user for authorization again.
\n\nWhen the access_token is about to expire, make a POST call to the MarketRock token endpoint (https://auth.edock.it/identity/connect/token), with the following parameters passed in x-www-form -urlencoded:
\n\nYou will receive another access_token, with which to continue accessing the client's MarketRock account.
\n\nEach MarketRock user may or may not own a MarketRock workspace. Furthermore, each user can have access, with different privileges, to different MarketRock workspaces.
\nExamples:
\nUser A owns a MarketRock workspace (to which he obviously has access), but does not have access to other workspaces
\nUser B does not own a MarketRock workspace, but can access two different MarketRock workspaces
\nUser C owns a MarketRock workspace and has access to two other workspaces.
\nTo access other Workspaces you must be invited by the Workspace owner.
\nEach user, on any workspace he or she owns, has access to all functionality (i.e. he or she can make any kind of API call).
\nOn the workspaces of which he is not the owner, however, he has permissions that are assigned by the owner user. Permissions are of different types (for example reading or writing products, reading or writing orders, reading or writing shipments and so on).
\nIf a call is made that requires privileges that the user does not have, HTTP code 401 (Unauthorized) will be returned.
\nEach API call is made on the user's default workspace.
\nThe default workspace is the workspace that you own. This means that an API call:
\nfor users A and C, it will be carried out on his property space
\nfor user B, it will fail with an HTTP 401 (Unauthorized) code
\nIt is possible to make the API call act on a workspace other than the default one, by valorising an X-eDock-Impersonate HTTP header, whose value is the workspace ID.
\nTo understand which workspaces a user can access and their IDs, you can call Users > Workspaces.
\nThis means that:
\nuser A will not be able to enhance the X-eDock-Impersonate installation (except by using the ID of his workspace, a useless operation)
\nuser B will be able to enhance the X-eDock-Impersonate header using, at his choice, the ID of the workspace 1 or 2 to which he has access
\nuser C will be able to act on workspaces of which he is not the owner by enhancing the X-eDock-Impersonate header.
\nThe first step is to redirect the user to MarketRock's central authentication service.
\nThe parameters to pass are:
\nresponse_type = code
\nclient_id = the client_id of your application (for testing, you can use demo_postman)
\nredirect_uri = the address to which the user will be redirected after successfully authenticating.
\nscope = list of scopes you intend to request (see initial documentation)
\nIf authentication is successful, the user will be redirected to the address passed as redirect_uri and a code parameter will be included that you can use to obtain access tokens (see Step 2).
\n","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"889fb7ee-3644-4d78-881a-cca72592e53e","id":"889fb7ee-3644-4d78-881a-cca72592e53e","name":"Auth&Auth","type":"folder"}},"urlObject":{"path":["identity","connect","authorize"],"host":["{{AuthServer}}"],"query":[{"key":"response_type","value":"code"},{"key":"client_id","value":"{{client_id}}"},{"key":"redirect_uri","value":"{{redirect_uri}}"},{"key":"scope","value":"openid+profile+items+orders+offline_access"}],"variable":[]}},"response":[],"_postman_id":"ea26d64f-9971-48d1-8a79-f9aa889a02df"},{"name":"Step 2 - Convert code to token","id":"c9ef1c4b-27ee-4217-ae28-8ad78f496970","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"authorization_code","type":"text"},{"key":"code","value":"{{code}}","type":"text"},{"key":"redirect_uri","value":"{{redirect_uri}}","type":"text"},{"key":"client_id","value":"{{client_id}}","type":"text"},{"key":"client_secret","value":"{{client_secret}}","type":"text"}]},"url":"{{AuthServer}}/identity/connect/token","description":"Once authentication has been successfully completed and the user has agreed to grant access to their data to your application, he will be redirected to the callback_uri indicated above.
\nMarketRock will send a parameter called code which is a disposable code with which your application can obtain the access_token and, if offline_access scope is required, also the refresh_token.
\nThe call involves passing these parameters:
\ngrant_type = authorization_code (fixed value)
\ncode = value of the code received
\nredirect_uri = the redirect_uri of your application
\nclient_id = the client_id of your application
\nclient_secret = your application's client_secret
\nIf the call is successful you will receive a response containing:
\naccess_token: access token with which you can make calls to the MarketRock API.
\nexpires_in: duration in seconds of the newly received access token (typically 1 day)
\nrefresh_token: only if the \"offline_access\" scope has been requested, contains the token with which it is possible to generate new access_tokens (see Step 3)
\nid_token: if the \"openid\" scope was requested, it contains the token with which it is possible to verify the identity (authentication) of the user.
\nATTENTION: the code parameter, once used, is destroyed. If the call fails (for example, due to the lack of some mandatory parameter), the code parameter is destroyed and it will be necessary to request a new one. Furthermore, the code parameter has a short expiry date, approximately 5 minutes, for security reasons.
\n","auth":{"type":"noauth","isInherited":true,"source":{"_postman_id":"889fb7ee-3644-4d78-881a-cca72592e53e","id":"889fb7ee-3644-4d78-881a-cca72592e53e","name":"Auth&Auth","type":"folder"}},"urlObject":{"path":["identity","connect","token"],"host":["{{AuthServer}}"],"query":[],"variable":[]}},"response":[{"id":"37983c9f-2af0-4212-a399-61e5d8edc738","name":"Step 2 - Convert code to token","originalRequest":{"method":"POST","header":[],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"authorization_code","type":"text"},{"key":"code","value":"{{code}}","type":"text"},{"key":"redirect_uri","value":"{{redirect_uri}}","type":"text"},{"key":"client_id","value":"{{client_id}}","type":"text"},{"key":"client_secret","value":"{{client_secret}}","type":"text"}]},"url":"{{AuthServer}}/identity/connect/token"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json; charset=utf-8"},{"key":"Date","value":"Wed, 29 Mar 2023 09:33:48 GMT"},{"key":"Server","value":"Microsoft-IIS/10.0"},{"key":"Cache-Control","value":"no-store, no-cache, max-age=0, private"},{"key":"Content-Encoding","value":"gzip"},{"key":"Pragma","value":"no-cache"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-AspNet-Version","value":"4.0.30319"},{"key":"X-Powered-By","value":"ASP.NET"}],"cookie":[],"responseTime":null,"body":"{\n \"id_token\": \"xxxxxx\",\n \"access_token\": \"[access_token]\",\n \"expires_in\": 86400,\n \"token_type\": \"Bearer\",\n \"refresh_token\": \"[refresh_token]\"\n}"}],"_postman_id":"c9ef1c4b-27ee-4217-ae28-8ad78f496970"},{"name":"Step 3 - Token refresh","id":"43a34804-a2a1-48d6-ab2f-0a384ddb5bbb","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"basic","basic":{"password":"{{client_secret}}","username":"{{client_id}}"},"isInherited":false},"method":"POST","header":[],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"refresh_token","type":"text"},{"key":"refresh_token","value":"{{refresh_token}}","type":"text"}]},"url":"{{AuthServer}}/identity/connect/token","description":"If, during the authentication phase, you requested the offline_access scope, you also received a refresh_token, which is a 30-day expiration token, automatically extended every time you use it (so in fact, it never expires).
\nFor this reason it is necessary that it is stored with the utmost care, since any loss of it, including the keys (client_id and client_secret), effectively causes deliberate access to the MarketRock accounts that authorized your application.
\nThe parameters to pass to update the token and therefore receive a new valid access_token are:
\ngrant_type: refresh_token
\nrefresh_token: value of your refresh_token
\nThe call must be authenticated by passing:
\nclient_id: value of your application's client_id, as username
\nclient_secret: value of your application's client_secret, as a password
\nIf the call is successful (i.e. the parameters are valid and the refresh_token has not expired), you will receive the following parameters:
\naccess_token: A new access token for calling our APIs
\nexpires_in: the new expiration of the passed access_token
\nrefresh_token: the refresh_token (technically it may not change from what you already had, but it is good practice to consider this as the new refresh_token to use for subsequent times)
\nid_token: if you asked for the \"openid\" scope, a new id_token to verify the identity (authentication) of the user.
\nATTENTION: As described in our API usage policies, in case of theft or loss of tokens you must contact us immediately at developer@marketrock.it so that we can promptly limit any data leaks.
\nFailure to promptly notify us will be considered a violation of our agreement and will result in immediate suspension of access to our API (key lockout) and invalidation of all tokens generated on behalf of your application.
\n","urlObject":{"path":["identity","connect","token"],"host":["{{AuthServer}}"],"query":[],"variable":[]}},"response":[{"id":"e6dadb1b-8c01-4ac9-a810-e2373241530a","name":"Step 3 - Token refresh","originalRequest":{"method":"POST","header":[],"body":{"mode":"urlencoded","urlencoded":[{"key":"grant_type","value":"refresh_token","type":"text"},{"key":"refresh_token","value":"{{refresh_token}}","type":"text"},{"key":"client_id","value":"{{client_id}}","type":"text"},{"key":"client_secret","value":"{{client_secret}}","type":"text"}]},"url":"{{AuthServer}}/identity/connect/token"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json; charset=utf-8"},{"key":"Date","value":"Wed, 29 Mar 2023 09:36:24 GMT"},{"key":"Server","value":"Microsoft-IIS/10.0"},{"key":"Cache-Control","value":"no-store, no-cache, max-age=0, private"},{"key":"Content-Encoding","value":"gzip"},{"key":"Pragma","value":"no-cache"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Vary","value":"Accept-Encoding"},{"key":"X-AspNet-Version","value":"4.0.30319"},{"key":"X-Powered-By","value":"ASP.NET"}],"cookie":[],"responseTime":null,"body":"{\n \"id_token\": \"[id_token]\",\n \"access_token\": \"[access_token]\",\n \"expires_in\": 86400,\n \"token_type\": \"Bearer\",\n \"refresh_token\": \"[refresh_token]\"\n}"}],"_postman_id":"43a34804-a2a1-48d6-ab2f-0a384ddb5bbb"}],"id":"889fb7ee-3644-4d78-881a-cca72592e53e","description":"In order to use the MarketRock API, you need to obtain an authentication token on behalf of your application.
\nEach application is identified by three parameters:
\nclient_id: a public identification
\nclient_secret: a security key, which must be kept by the developer with the utmost care
\nredirect_uri: a safe callback address through which the MarketRock authentication service can speak with the application
\nThe authentication process consists of two steps:
\nRedirection of the user to the MarketRock access page
\nReception of the code parameter and conversion of the same in an access_token
\nOnce the token has been generated, if the offline_access scope has been requested, it is possible to proceed with the update (refresh) of the same, through the call \"Token refresh\".
\nIn the following examples, a test application will be used whose parameters are:
\nclient_id: demo_postman
\nclient_secret: [contact us at developer@marketrock.it]
\nredirect_uri: https://www.getpostman.com/oauth2/callback
\nATTENTION: These keys must not be used in production, since marketrock will be invalidly invalid all generated tokens, even before their expiry for safety reasons.
\nIn production it will be necessary to use the keys obtained from MarketRock.
\nThe improper use of these test keys can lead to the complete suspension of your developer account.
\n\n","auth":{"type":"noauth","isInherited":false},"event":[{"listen":"prerequest","script":{"id":"bf214f5a-d2a8-443e-87a4-550716881621","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"a8d428cb-df08-4e8d-bc18-3a18bb6b4308","type":"text/javascript","exec":[""]}}],"_postman_id":"889fb7ee-3644-4d78-881a-cca72592e53e"},{"name":"Logistics Hub","item":[{"name":"Orders","item":[{"name":"Search","id":"203ab7b1-5ceb-6183-d1da-e27f464d8166","request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\r\n \"page\": 0, //Recupera questa pagina di ordini. Il conto inizia da 0. Obbligatorio.\r\n \"pageSize\": 5 //Dimensione della pagina. Obbligatorio\r\n}"},"url":"{{endpoint}}/orders/search","description":"Retrieve orders in your MarketRock account. Orders are returned paginated. The page and its size are controlled by the page and pageSize parameters.
The first page has index 0. The maximum value of the pageSize parameter is 500.
It is possible to carry out a targeted search on all orders present on MarketRock by filtering them according to all filters passed in the filters parameter. All the filters that are passed are considered AND between them (i.e. the orders that respect all the passed filters are returned).
\nAvailable filters
\nidStatusFilter: Order status ID
\nOrderIdGreaterOrEqualThan: Order ID greater than or equal to...
\nOrderIdLowerOrEqualThan: Order ID less than or equal to...
\nModuleIDFilter: ID of the marketplace on which the order was generated (for the value, check the \"Modules\" call)
\nPaid: Paid (true / false)
\nCreatedOnStart: Created starting from yyyy-mm-dd
\nCreatedOnEnd: Created until yyyy-mm-dd
\nShippedOnStart: Shipped starting yyyy-mm-dd
\nShippedOnEnd: Shipped until yyyy-mm-dd
\nMarketplaceOrderId: ID of this order in the source marketplace
\nOrders, unless otherwise specified, are returned with a set of basic information (i.e. Rows, ShippingAddress and BillingAddress details are loaded by default). This information is generally sufficient for order processing. For more advanced integration scenarios, it is possible to request additional details, using the \"details\" field.
\nDetails parameter can be populated with one or more of the following values:
\nHistory: history of the order
\nFees: commissions applied by the marketplace
\nInvoices: invoices linked to the order
\nExternalSellerReference: for orders coming from eBay and Amazon, the \"SellerAccount\" field is filled in, containing the account name of the seller who received the sale
\nPayments: the \"Payments\" field is filled in, containing all the information on PayPal payments received for eBay orders
\nRowVariationAttributes: the \"VariationValues\" field on the order lines is enhanced. This field contains the names and values of the attributes of the purchased variants
\nContactInformations: the \"ContactInformations\" field is filled in, containing all the information on the buyers passed by the marketplace on which the order was generated
\nAttachments: the \"Attachments\" field is filled in, containing all the attachments of an order
\nMeasures: retrieves measures linked to contained items
\nMarketplaceAdditionalInformations: additional informations retrieved from the marketplace from which this orders has been generated
\nIf the details field is used, all details NOT specified will not be passed. For this reason, to get the basic information (which is passed by default when \"details\" is not populated), you can pass these details:
\nBillingAddress: billing address
\nShippingAddress: shipping address
\nRows: order lines
\nRetrieves an order, whose ID is passed in the idOrder parameter.
Optionally it is possible to pass in the detail parameter, separated by commas, the details that you intend to retrieve.
If the detail parameter is not passed, all available details are returned.
Check \"Get all\" documentation for valid values for the detail parameter.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Sposta uno o più ordini in un altro stato.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Segnala gli ordini come pagati.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Segnala l'ordine come spedito, specificando le informazioni per il tracking.
\nValorizza le note dell'ordine.
\nPuò essere utile per impostare qualche nota sullo stato di importazione come,\nad esempio, messaggi di errore in fase di importazione o avvertenze varie.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Crea un ordine su MarketRock
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Modifica un ordine già esistente su MarketRock
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Genera l'etichetta PDF per la spedizione con il nome, il cognome, l'indirizzo, il codice postale, il città e la nazione.
\nOccorre passare l'id ordine (idOrderInt) dell'ordine di cui si vuole generare l'etichetta.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Recupera le informazioni su un cliente il cui ID è passato nel parametro {{idCustomer}}. La risposta contiene alcune informazioni aggiuntive fornite dal marketplace su cui l'ordine è stato effettuato.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Esporta gli ordini indicati nel parametro idOrders. Il parametro OrderExportType accetta questi valori:
\nATTENZIONE: per poter creare una esportazione è necessario che il vostro client sia abilitato alla ricezione delle informazioni personale. Il client \"demo_postman\" non è abilitato a queste informazioni, per cui la chiamata restituirà sempre errore.
\nBartolini VAS
\nÈ necessario passare anche un parametro Bartolini con il seguente formato:
\n{
\n \"CodiceBolla\": \"CODICE_BOLLA\",\n \"CodiceCliente\": \"CODICE_CLIENTE\",\n \"CodiceTariffa\": \"CODICE_TARIFFA\",\n \"FilialePartenza\": \"CODICE_FILIALE_PARTENZA\",\n \"ServizioBolle\": \"CODICE_SERVIZIO_BOLLE\",\n \"ValorePeso\": \"VALORE_DEL_PESO\",\n \"DataSpedizione\": \"DATA_ESEMPIO_2021-01-01\",\n \"Formato\": \"FORMATO_VEDI_NOTE\",\n \"Network\": \"NETWORK_VEDI_NOTE\",\n \"NotifyType\": \"SEGUI_NOTE_BARTOLINI\",\n \"ExportContent\": \"VEDI NOTE\"\n\n}
\nCarica una fattura / ricevuta, associandola ad un ordine.
\nNel caso di ordine Amazon, questa operazione scatena l'upload su Seller Central.
\nI parametri della richiesta sono:
\nRecupera gli stati degli ordini.
\nGli stati non sono altro che cartelle in cui gli ordini possono essere
inseriti. Un ordine deve necessariamente stare in uno stato.
MarketRock contiene 4 stati predefiniti:
\nSegnaliamo che \"Pagato\" non è uno stato su MarketRock,
poiché un ordine pagato può trovarsi in qualunque stato (ad esempio,
un ordine spedito in contrassegno, non è ancora pagato, eppure è spedito).
Per recuperare i soli ordini pagati è necessario valorizzare il filtro \"Paid\"
impostando il valore a \"true\" (vedi chiamata \"Get all (with filters)\").
Invia al provider di fatturazione configurato sull'account MarketRock la richiesta di generazione dei corrispettivi per gli ordini selezionati (passati nell'array idOrders).
\nSi può opzionalmente richiedere la generazione dei corrispettivi ad un provider di fatturazione specifico, valorizzando l'oggetto \"FiscalProvider\". Tale oggetto è composto dalle seguenti proprietà:
\nName: nome del provider di fatturazione
\nParameters: array di parametri per la personalizzazione della generazione dei documenti
\nInvia al provider di fatturazione configurato sull'account MarketRock la richiesta di generazione di documenti fiscali per gli ordini selezionati (passati nell'array idOrders).
\nI documenti richiedibili sono:
\ninvoice: fatture
\nreceipt: ricevute
\ndelivery_note: DDT (documenti di traporto)
\nSi può opzionalmente richiedere la generazione dei documenti ad un provider di fatturazione specifico, valorizzando l'oggetto \"FiscalProvider\". Tale oggetto è composto dalle seguenti proprietà:
\nName: nome del provider di fatturazione
\nParameters: array di parametri per la personalizzazione della generazione dei documenti
\nSets the order as canceled. If buyer-initiated cancellation is supported on the source marketplace, MarketRock will submit the cancellation request to the marketplace as well. You can understand if the marketplace supports buyer-initiated cancellation, performing a Marketplaces > Orders > IsCancellationEnabled call.
\nIn order to cancel an order you can provide:
\na CancelReason parametrer. Some marketplaces will ask for particular value for this message. You can perform a Marketplaces > Orders > Get Cancellation Reasons call to retrieve supported values. If no values is returned, then this field can be considered as free text.
\nan UpdateStorage parameters. If set to true, storage will be updated reverting unloaded quantities previously reduced by the order
\nAllows you to retrieve all shipping configurations currently active on your MarketRock account.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Allows you to retrieve a particular shipping configuration given its id.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Allows you to retrieve a particular shipping configuration's parameters given its id.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Verify if the shipping configuration you are trying to define is correct and complete.
\nCall this endpoint before inserting a configuration in order to be assured that it is valid and usable.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Insert a new shipping configuration
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Modifies an existing shipping configuration
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"On your MarketRock account you can define different shipping configurations for the different supported couriers.
\nEach shipping configuration is essentially a particular set of parameters, defined by the courier, which allow MarketRock to generate shipping labels and tracking codes.
\nIt is possible to define multiple shipping configurations for each courier, this to allow complex scenarios (i.e. multiple contracts for different regions).
\n","_postman_id":"20ddeb5e-1eca-4b42-b1cc-d87879373190","auth":{"type":"oauth2","oauth2":{"useBrowser":"Allows you to retrieve the carriers currently supported by MarketRock for generating shipping labels.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"Retrieve a carrier given his ID.
\n","auth":{"type":"oauth2","oauth2":{"useBrowser":"