{"activeVersionTag":"latest","latestAvailableVersionTag":"latest","collection":{"info":{"_postman_id":"0aea9400-c9e4-4c5b-8f3d-8d4253d9b514","name":"ShareGroop API","description":"# Welcome to ShareGroop API\n\nOn this page right panel, you can find some pre-made requests and response examples for you to explore the API :\n\n- you can select the desired code langage of theses examples (on to top right select)\n    \n- each calls have a success and error payload examples too\n    \n\nYou can take advantage of this reference by using it on your Postman :\n\n- click on **run in postman** button\n    \n- setup your postman [environment variables](https://www.getpostman.com/docs/v6/postman/environments_and_globals/manage_environments)\n    \n\n---\n\n# API Authorization\n\nTo call the API, you need your secret API key.\n\nYour key carry privileges, so be sure to keep them secure.  \nThink of your private key like a password:\n\n- Store it securely\n    \n- Don't share it with anyone outside of your `organization`\n    \n- Don't put it in any code public code\n    \n\nIt can be found on your [Dashboard](https://sandbox.sharegroop.com), in your `platform` page :\n\n- keys are different for each environment\n    \n- Your platforms (if many) have different keys\n    \n\nYou keys are different by platform. Hence, different in sandbox and production environment. Sandbox keys have `_test_` in their prefix.\n\nTo use it, simply add the header `Authorization: secret-key` to your requests.\n\n`401`is returned if authentication fails.\n\nAll requests enforce HTTPS.\n\n---\n\n# API Endpoints\n\n- sandbox : `https://api.sandbox.sharegroop.com/v1`\n    \n- production : `https://api.sharegroop.com/v1`\n    \n\n---\n\n# Modules integration\n\n## Single\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#pay-later-integration) to get started.\n\nYou can refer to the POST /orders (Single) reference below.\n\n## Pay later\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#pay-later-integration) to get started.\n\nYou can refer to the POST /orders (Pay later) reference below.\n\n## Installments\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#installments-integration) to get started.\n\nYou can refer to the POST /orders (Installments) reference below.\n\n## Multi cards\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#multi-cards-integration) to get started.\n\n## ANCV Connect\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#ancv-connect) to get started.\n\n## Recurring payments\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#ancv-connect) to get started.\n\nYou can refer to the POST /orders (tokenize\\*) references below.\n\n## Subscription\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#ancv-connect) to get started.\n\nYou can refer to the collections : Customers, Subscriptions, Invoices.\n\n## Virtual Iban\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#virtual-iban-integration) to get started.\n\nYou can refer to :\n\n- by Order (1 IBAN by Order) : the request POST /orders (Virtual Ibans)\n    \n- by Customer (1 IBAN by Customer) : the request POST /customers/id/viban\n    \n- [simulation endpoints](https://sharegroop.postman.co/workspace/SG-V2---API-public~f54737ee-b57c-444f-835e-5026ec50012e/folder/168771-35776a0e-f9ee-499a-bbf0-11a5e4ade20e?action=share&source=copy-link&creator=168771&ctx=documentation) to trigger a payment on a virtual iban so you can test your integration without waiting real bank transfers.\n    \n\n## Split (group payments)\n\n#### Get started\n\nPlease read our [module documentation](https://docs.sharegroop.com/modules.html#split-integration) to get started.\n\nTo integrate our **Split** solution, you only need few backend calls.\n\n#### 1\\. Create an order\n\nTo get and `order id`, your first need to create an order using `POST /orders`, with at least an order `amount` in cents.\n\nAlso, **we strongly recommand** to also specify your `captain` contact : `email`, `firstName`, `lastName`. Otherwise, they will be asked to fill during payment. Theses are used to communicates to its co-buyers.\n\nOnce you get this id, **save it**.\n\nl then be able to start its group payment using our [Captain component](https://docs.sharegroop.com/integrations.html#captain-component).\n\n#### 2\\. Verify the payment\n\nTo **check the captain payment** on captain component validation, just call `GET /order/{id}`, and check for status `confirmed`\n\n#### 3\\. Confirm\n\n- mode `direct`:  \n    At this point, you can confirm the order on your side, as if it was a regular single payment, since we pre-authorized the full order amount on the captain's card. Your payment is guaranteed !  \n    Following steps with the group will be handled by ShareGroop. Money will be captured at the end of the share.\n    \n\nAlso, **we strongly recommand** to display the unique sharing link on your captain's confirmation page using our [Link component](https://docs.sharegroop.com/integrations.html#link-component).\n\n## Viral booking\n\nTo integrate our **Dynamic Pricing** solution, you only need few backend calls.\n\n#### 1\\. Create an order to hold the dynamic pricing logic\n\nTo get and `order id`, your first need to create an order using `POST /orders` by specifiying dynamic pricing rules.\n\nOnce you get this id, **save it**.\n\n#### 2\\. Before each payment, initiate a transaction\n\nUsing `POST /transactions` (specifying the `orderId` on this transaction).\n\nOn front-end : Your captain will then be able to start its group payment using our [widget](https://docs.sharegroop.com/integrations.html#captain-component).  \nYou will need to specify `transactionId: transaction.id` instead of the `orderId` in the widget.initCaptain() data.\n\n#### 3\\. Verify the payment\n\nAfter the widget validation event, **check the payment** from your back-end by calling `GET /transactions/{id}`, status can be `authorized` or `captured`\n\n#### 4\\. Order finalization\n\nDynamic pricing orders will be closed when the due date is reached. At this point, all authorized transactions will be captured according to the defined order rules.\n\n---\n\n### Refunds\n\nTo refund a group, just call `POST /orders/{id}/refund`.\n\nAll captured transaction of the group will be refunded.\n\nOrder state will then be `refunded`.\n\nIndividual refunds can be triggered using `POST /transactions/{id}/refund`.\n\n---\n\n### Cancel\n\nTo cancel an order just call `POST /orders/{id}/cancel`.\n\nOrder state will then be `canceled`.\n\nAll transaction still authorized will be voided.\n\nIndividual void can be triggered using `POST /transactions/{id}/void`.\n\nDepending on your platform configuration, if a transaction is already captured before. You must should refund them by calling `POST /transactions/{id}/refund`.\n\n---\n\n# Reportings\n\nTo reconcile with your payments, use the Reporting collection to :\n\n- fetch the list of Operations\n    \n- fetch the list of Payout(s) (bank transfer(s) we made to your configured bank(s) account(s), and list of Operations that compose a Payout\n    \n\n---\n\n# Webhooks\n\nIf the integration of our solution requires notifications to your system. You can refer to our [Webhooks documentation](https://docs.sharegroop.com/webhook.html#setting-up-webhooks).\n\n---\n\n# Disclaimer\n\nPlease **do not** strictly enforce our API responses payload, nor store front-end scripts.\n\nShareGroop is moving forward to bring more front-end and back-end features, updates will likely introduce minor changes.\n\nIf you have a need which is not fulfilled yet by this documentation, please contact us at [support@sharegroop.com](https://mailto:support@sharegroop.com).\n\n---\n\n# General knowledge\n\n## Order lifecycle\n\nThe lifecycle of a Sharegroop order is as follows:\n\n### initiated\n\nThe first status of an order is `initiated`. At this step, no payment has been made on the order.  \nThe order payment link is accessible.\n\n- **Webhook** : No webhook is sent to the merchant when the order status is `initiated`.\n    \n- **Email** : No email is sent to the buyer when the order status is `initiated`.\n    \n\n### confirmed\n\nThe order status becomes `confirmed` when a first transaction authorization has been made.  \nThe order payment link is accessible.\n\n- **Webhook** : If configured, a webhook for the event `order.confirmed` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### pendingCommit\n\nOnly for the [two-phase commit integration](https://docs.sharegroop.com/integrations.html#two-phase-commit). The order status becomes `pendingCommit` when the order is supposed to be `completed` and you did not already commit the order.  \nThe order payment link is not accessible anymore.\n\n- **Webhook** : If configured, a webhook for the event `order.pendingCommit` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n    \n- **Email** : No email is sent to the buyer.\n    \n\n### completed\n\nThe order status becomes `completed` when the total order amount has been collected.  \nWhen an order is `completed`, no online payments can be made. The order payment link is not accessible anymore.\n\n- **Webhook** : If configured, a webhook for the event `order.completed` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n    \n- **Email :** Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### refunded\n\nThe order becomes `refunded` when the total amount collected has been refunded.  \nThe order payment link is not accessible anymore.\n\n- **Webhook** : If configured, a webhook for the event `order.refunded` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n    \n- **Email :** Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### canceled\n\nThe order becomes `canceled` when the merchant cancels the order from the Sharegroop API or from the Sharegroop Dashboard. All transactions `authorized` and `pendingAuthorization` are voided.  \nThe order payment link is not accessible anymore.\n\n- **Webhook** : If configured, a webhook for the event `order.canceled` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n    \n- **Email :** Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n## Transaction lifecycle\n\nThe lifecycle of a Sharegroop transaction is as follows:\n\n### initiated\n\nThe first status of a transaction is `initiated`. At this step, the payment has been initiated but is not yet authorized.  \nThe order payment link is accessible.\n\n- **Webhook** : No webhook is sent to the merchant when the transaction status is `initiated`.\n    \n- **Email** : No email is sent to the buyer when the transaction status is `initiated`.\n    \n\n### pendingAuthorization\n\nOnly for the [Installments](https://docs.sharegroop.com/modules.html#installments) and [Pay-later](https://docs.sharegroop.com/modules.html#pay-later) integrations. The transaction status becomes `pendingAuthorization` when the deadline corresponding to this transaction has not been reached. The payment of this deadline is pending.\n\n- **Webhook** : No webhook is sent to the merchant.\n    \n- **Email** : No email is sent to the buyer.\n    \n\n### authorized\n\nThe transaction status becomes `authorized` when the payment has been authorized. At this step, the amount is not yet collected.\n\n- **Webhook** : If configured, a webhook for the event `transaction.authorized` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### failed\n\nThe transaction status becomes `failed` when an action on the transaction has failed. The failure code and reason can be found in the transaction details.\n\n- **Webhook** : If configured, a webhook for the event `transaction.failed` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### captured\n\nThe transaction status becomes `captured` when the amount has been collected.\n\n- **Webhook** : If configured, a webhook for the event `transaction.captured` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### refundedPartial\n\nThe transaction status becomes `refundedPartial` when a part of the amount captured has been refunded and there is still some amount captured but not refunded.\n\n- **Webhook** : If configured, a webhook for the event `transaction.refundedPartial` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### refunded\n\nThe transaction status becomes `refunded` when the total amount captured has been refunded.\n\n- **Webhook** : If configured, a webhook for the event `transaction.refunded` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### refundFailed\n\nThe transaction status becomes `refundFailed` when the refund has failed. The failure code and reason can be found in the transaction details.\n\n- **Webhook** : If configured, a webhook for the event `transaction.refundFailed` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email :** Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### voided\n\nThe transaction status becomes `voided` when a void request for the transaction has succeeded.\n\n- **Webhook** : If configured, a webhook for the event `transaction.voided` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : Depending on the Sharegroop module configured, the buyer can receive an email.\n    \n\n### voidFailed\n\nThe transaction status becomes `voidFailed` when a void request for the transaction has failed. The failure code and reason can be found in the transaction details.\n\n- **Webhook** : If configured, a webhook for the event `transaction.voidFailed` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- **Email** : No email is sent to the buyer when the transaction status becomes `voidFailed`.\n    \n\n## Order cancellation\n\nAn order can be canceled (which is different from the refund). You can cancel an order from the Sharegroop dashboard or from the Sharegroop API. An order with status `completed` or `refunded` cannot be canceled.\n\nWhen you cancel an order:\n\n- all transactions with status `authorized` or `pendingAuthorization` are voided\n    \n- a webhook for the event `transaction.voided` or `transaction.pendingAuthorization` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- if the transactions voided have installments linked, each installment status becomes `canceled` (except for the module with installments non-automatic)\n    \n- for each transaction voided, the order amount is reduced by the amount voided\n    \n- the order status becomes `canceled`\n    \n- a webhook for the event `order.canceled` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n    \n\nWhen an order is `canceled`:\n\n- the order payment link is not accessible anymore\n    \n- the order data can still be updated by calling the Sharegroop API\n    \n- the refund from the Sharegroop dashboard or by calling the Sharegroop API is not possible at the order level\n    \n- if the order has a transaction `captured`, it is possible to do a refund at the transaction level by calling the Sharegroop API or from the Sharegroop dashboard.\n    \n    - a webhook for the event `transaction.refunded` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n        \n    - if the order amount captured is totally refunded, the order becomes `refunded`. A webhook for the event `order.refunded` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n        \n- an external transaction can still be added\n    \n    - If it is an external transaction for payment, the amount captured of the order is increased. If the amount captured of the order is equal or greater than the order amount, the order status becomes `completed`. A webhook for the event `order.completed` is then sent to the merchant when the external transaction is added from the Sharegroop dashboard. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n        \n\nModule installments lifecycle\n\n### Create the order\n\n_Order_\n\nWhen an order with installments is created, the order status is `initiated`. At this step, no payment has been made on the order.\n\nThe order payment link is accessible.\n\nNo webhook is sent to the merchant.\n\nNo email is sent to the buyer.\n\n_Installments_\n\nIf the merchant calls the Sharegroop API to create the order and specify the parameter `installmentsCount` or `installments` (without financing only), the installments table will be directly created. All installments statuses will be `pending`. (see [Create an Installments order](https://docs.sharegroop.com/modules.html#installments-integration))\n\nNo webhook is sent to the merchant.\n\nNo email is sent to the buyer.\n\n_Transaction_\n\nAt this step, no transaction is created.\n\n### The buyer confirms his purchase\n\n_Order_\n\nAs soon as the buyer has confirmed his purchase and the first transaction is authorized, the order status becomes `confirmed`.\n\nThe order payment link is accessible to complete in advance the full remaining balance of the order.\n\nA webhook for the event `order.confirmed` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n\nThe buyer receives an email which contains the link to complete in advance the full remaining balance of the order.\n\n_Installments_\n\nThe first installment status becomes `paid`.\n\nA webhook for the event `installment.paid` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-installment)).\n\n_Transaction_\n\nThe first transaction corresponding to the first installment becomes `authorized` then `captured` when the amount is collected.\n\nA webhook for the event `transaction.captured` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction)).\n\n### Next deadlines payment\n\nDepending on the configuration, when the next deadlines are approaching the buyer receives an email to remind him that the scheduled payment of the deadline is approaching. The email will also contain a link to allow the buyer to pay his deadline online.\n\nWhen the deadline is paid:\n\n- the corresponding installment status becomes `paid`\n    \n- a webhook for the event `installment.paid` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-installment))\n    \n- the corresponding transaction status becomes `authorized` then `captured`\n    \n- a webhook for the event `transaction.captured` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- the buyer receives an email to inform him that his payment is confirmed\n    \n\n### Order completion\n\nWhen the last deadline is paid:\n\n_Order_\n\nThe total order amount has been collected. The order status becomes `completed`.\n\nThe order payment link is not accessible anymore.\n\nA webhook for the event `order.completed` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-order))\n\nThe buyer receives an email to inform him that the last deadline has been paid.\n\n_Installments_\n\nThe last installment status becomes `paid`.\n\nA webhook for the event `installment.paid` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-installment)).\n\n_Transaction_\n\nThe last transaction corresponding to the last installment becomes `authorized` then `captured` when the amount is collected.\n\nA webhook for the event `transaction.captured` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n\n### Installments payment failures\n\nWhen the scheduled payment of an installment fails (see [Installments recovery](https://docs.sharegroop.com/modules.html#installments-recovery)):\n\n- the installment status becomes `unpaid`\n    \n- a webhook for the event `installment.unpaid` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-installment))\n    \n- the buyer receives an email to inform him that the payment of his deadline has failed. The email will also contain a link to allow the buyer to directly pay his installment online.\n    \n- the corresponding transaction status becomes `failed`\n    \n\nIf the payments recovery is configured, there will be several retries within a specific interval and a maximum number of retries. Each time the payment attempt fails:\n\n- a webhook for the event `installment.unpaid` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-installment))\n    \n- the buyer receives an email to inform him that the payment of his deadline has failed. The email will also contain a link to allow the buyer to directly pay his installment online.\n    \n\nIf this maximum of retries is reached and the payment is still failed, a webhook for the event `installment.recoveryFailed` is sent to the merchant.\n\n### Installments refunds and cancellations\n\nInstallments can be refunded or canceled depending on the use case. (see [Installments cancellations](https://docs.sharegroop.com/modules.html#installments-cancellations))\n\nIf the installment is refunded or partially refunded:\n\n- the installment status remains `paid`\n    \n- the corresponding transaction status becomes `refundedPartial` or `refunded`\n    \n- a webhook for the event `transaction.refundedPartial` or `transaction.refunded` is sent to the merchant. (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- the buyer receives an email to inform him that the payment of his deadline has been refunded or partially refunded\n    \n\nIf the installment is canceled:\n\n- the installment status becomes `canceled`\n    \n- the corresponding transaction status becomes `voided`\n    \n- a webhook for the event `transaction.voided` is sent to the merchant (see [Webhooks documentation](https://docs.sharegroop.com/webhook.html#resource-transaction))\n    \n- an installment with status `paid` can never becomes `canceled`, its status remains `paid`\n    \n\n---\n\n# API Reference","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","isPublicCollection":false,"owner":"168771","team":152044,"collectionId":"0aea9400-c9e4-4c5b-8f3d-8d4253d9b514","publishedId":"RWaRMkMY","public":true,"publicUrl":"https://documenter-api.postman.tech/view/168771/RWaRMkMY","privateUrl":"https://go.postman.co/documentation/168771-0aea9400-c9e4-4c5b-8f3d-8d4253d9b514","customColor":{"top-bar":"007BFF","right-sidebar":"484848","highlight":"007BFF"},"documentationLayout":"classic-double-column","version":"8.10.1","publishDate":"2019-10-25T14:27:48.000Z","activeVersionTag":"latest","documentationTheme":"light","metaTags":{},"logos":{}},"statusCode":200},"environments":[{"name":"sandbox","id":"58fc52e8-6fd4-4ca9-9f82-c07acf67b886","owner":"168771","values":[{"key":"base-url","value":"https://api.sandbox.sharegroop.com/v1","enabled":true,"type":"default"},{"key":"api-key","value":"sk_test_e1ed6973-3ed9-467e-af49-9d6330cd49aa","enabled":true,"type":"default"},{"key":"orderId","value":"ord_d50e2109-8c13-4196-8d2d-0a1c17653072","enabled":true,"type":"default"},{"key":"walletId","value":"","enabled":true,"type":"default"},{"key":"api-key-tenant","value":"","enabled":true,"type":"default"},{"key":"api-key-platform","value":"","enabled":true,"type":"default"},{"key":"moduleId_for_card_payment","value":"","enabled":true,"type":"default"},{"key":"moduleId_for_viban_payment","value":"","enabled":true,"type":"default"},{"key":"moduleId_for_wallet_consumption","value":"","enabled":true,"type":"default"}],"published":true}],"user":{"authenticated":false,"permissions":{"publish":false}},"run":{"button":{"js":"https://run.pstmn.io/button.js","css":"https://run.pstmn.io/button.css"}},"web":"https://www.getpostman.com/","team":{"logo":"https://res.cloudinary.com/postman/image/upload/t_team_logo_pubdoc/v1/team/431fc598419e31207125c00a2f39a374f001774c501801cebdcecf243f7489f4","favicon":""},"isEnvFetchError":false,"languages":"[{\"key\":\"csharp\",\"label\":\"C#\",\"variant\":\"HttpClient\"},{\"key\":\"csharp\",\"label\":\"C#\",\"variant\":\"RestSharp\"},{\"key\":\"curl\",\"label\":\"cURL\",\"variant\":\"cURL\"},{\"key\":\"dart\",\"label\":\"Dart\",\"variant\":\"http\"},{\"key\":\"go\",\"label\":\"Go\",\"variant\":\"Native\"},{\"key\":\"http\",\"label\":\"HTTP\",\"variant\":\"HTTP\"},{\"key\":\"java\",\"label\":\"Java\",\"variant\":\"OkHttp\"},{\"key\":\"java\",\"label\":\"Java\",\"variant\":\"Unirest\"},{\"key\":\"javascript\",\"label\":\"JavaScript\",\"variant\":\"Fetch\"},{\"key\":\"javascript\",\"label\":\"JavaScript\",\"variant\":\"jQuery\"},{\"key\":\"javascript\",\"label\":\"JavaScript\",\"variant\":\"XHR\"},{\"key\":\"c\",\"label\":\"C\",\"variant\":\"libcurl\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Axios\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Native\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Request\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Unirest\"},{\"key\":\"objective-c\",\"label\":\"Objective-C\",\"variant\":\"NSURLSession\"},{\"key\":\"ocaml\",\"label\":\"OCaml\",\"variant\":\"Cohttp\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"cURL\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"Guzzle\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"HTTP_Request2\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"pecl_http\"},{\"key\":\"powershell\",\"label\":\"PowerShell\",\"variant\":\"RestMethod\"},{\"key\":\"python\",\"label\":\"Python\",\"variant\":\"http.client\"},{\"key\":\"python\",\"label\":\"Python\",\"variant\":\"Requests\"},{\"key\":\"r\",\"label\":\"R\",\"variant\":\"httr\"},{\"key\":\"r\",\"label\":\"R\",\"variant\":\"RCurl\"},{\"key\":\"ruby\",\"label\":\"Ruby\",\"variant\":\"Net::HTTP\"},{\"key\":\"shell\",\"label\":\"Shell\",\"variant\":\"Httpie\"},{\"key\":\"shell\",\"label\":\"Shell\",\"variant\":\"wget\"},{\"key\":\"swift\",\"label\":\"Swift\",\"variant\":\"URLSession\"}]","languageSettings":[{"key":"csharp","label":"C#","variant":"HttpClient"},{"key":"csharp","label":"C#","variant":"RestSharp"},{"key":"curl","label":"cURL","variant":"cURL"},{"key":"dart","label":"Dart","variant":"http"},{"key":"go","label":"Go","variant":"Native"},{"key":"http","label":"HTTP","variant":"HTTP"},{"key":"java","label":"Java","variant":"OkHttp"},{"key":"java","label":"Java","variant":"Unirest"},{"key":"javascript","label":"JavaScript","variant":"Fetch"},{"key":"javascript","label":"JavaScript","variant":"jQuery"},{"key":"javascript","label":"JavaScript","variant":"XHR"},{"key":"c","label":"C","variant":"libcurl"},{"key":"nodejs","label":"NodeJs","variant":"Axios"},{"key":"nodejs","label":"NodeJs","variant":"Native"},{"key":"nodejs","label":"NodeJs","variant":"Request"},{"key":"nodejs","label":"NodeJs","variant":"Unirest"},{"key":"objective-c","label":"Objective-C","variant":"NSURLSession"},{"key":"ocaml","label":"OCaml","variant":"Cohttp"},{"key":"php","label":"PHP","variant":"cURL"},{"key":"php","label":"PHP","variant":"Guzzle"},{"key":"php","label":"PHP","variant":"HTTP_Request2"},{"key":"php","label":"PHP","variant":"pecl_http"},{"key":"powershell","label":"PowerShell","variant":"RestMethod"},{"key":"python","label":"Python","variant":"http.client"},{"key":"python","label":"Python","variant":"Requests"},{"key":"r","label":"R","variant":"httr"},{"key":"r","label":"R","variant":"RCurl"},{"key":"ruby","label":"Ruby","variant":"Net::HTTP"},{"key":"shell","label":"Shell","variant":"Httpie"},{"key":"shell","label":"Shell","variant":"wget"},{"key":"swift","label":"Swift","variant":"URLSession"}],"languageOptions":[{"label":"C# - HttpClient","value":"csharp - HttpClient - C#"},{"label":"C# - RestSharp","value":"csharp - RestSharp - C#"},{"label":"cURL - cURL","value":"curl - cURL - cURL"},{"label":"Dart - http","value":"dart - http - Dart"},{"label":"Go - Native","value":"go - Native - Go"},{"label":"HTTP - HTTP","value":"http - HTTP - HTTP"},{"label":"Java - OkHttp","value":"java - OkHttp - Java"},{"label":"Java - Unirest","value":"java - Unirest - Java"},{"label":"JavaScript - Fetch","value":"javascript - Fetch - JavaScript"},{"label":"JavaScript - jQuery","value":"javascript - jQuery - JavaScript"},{"label":"JavaScript - XHR","value":"javascript - XHR - JavaScript"},{"label":"C - libcurl","value":"c - libcurl - C"},{"label":"NodeJs - Axios","value":"nodejs - Axios - NodeJs"},{"label":"NodeJs - Native","value":"nodejs - Native - NodeJs"},{"label":"NodeJs - Request","value":"nodejs - Request - NodeJs"},{"label":"NodeJs - Unirest","value":"nodejs - Unirest - NodeJs"},{"label":"Objective-C - NSURLSession","value":"objective-c - NSURLSession - Objective-C"},{"label":"OCaml - Cohttp","value":"ocaml - Cohttp - OCaml"},{"label":"PHP - cURL","value":"php - cURL - PHP"},{"label":"PHP - Guzzle","value":"php - Guzzle - PHP"},{"label":"PHP - HTTP_Request2","value":"php - HTTP_Request2 - PHP"},{"label":"PHP - pecl_http","value":"php - pecl_http - PHP"},{"label":"PowerShell - RestMethod","value":"powershell - RestMethod - PowerShell"},{"label":"Python - http.client","value":"python - http.client - Python"},{"label":"Python - Requests","value":"python - Requests - Python"},{"label":"R - httr","value":"r - httr - R"},{"label":"R - RCurl","value":"r - RCurl - R"},{"label":"Ruby - Net::HTTP","value":"ruby - Net::HTTP - Ruby"},{"label":"Shell - Httpie","value":"shell - Httpie - Shell"},{"label":"Shell - wget","value":"shell - wget - Shell"},{"label":"Swift - URLSession","value":"swift - URLSession - Swift"}],"layoutOptions":[{"value":"classic-single-column","label":"Single Column"},{"value":"classic-double-column","label":"Double Column"}],"versionOptions":[],"environmentOptions":[{"value":"0","label":"No Environment"},{"label":"sandbox","value":"168771-58fc52e8-6fd4-4ca9-9f82-c07acf67b886"}],"canonicalUrl":"https://documenter.gw.postman.com/view/metadata/RWaRMkMY"}