{"activeVersionTag":"latest","latestAvailableVersionTag":"latest","collection":{"info":{"_postman_id":"1f6bf01f-a106-4deb-a284-eb781e99e155","name":"Sovtes Public API v2.9.9","description":"The Sovtes API enables secure integration between the Sovtes freight collaboration platform and your ERP, TMS, CRM, WMS, accounting, or internal operational systems.\n\nThe API provides access to operational workflows including:\n\n- routes and tenders\n    \n- transport assignments\n    \n- carriers and partners\n    \n- vehicles and drivers\n    \n- messages and activity logs\n    \n- status updates and event notifications\n    \n\n# About Sovtes 🇺🇦\n\nSovtes is a freight collaboration platform developed for operational logistics workflows including transport procurement, carrier collaboration, fleet coordination and transport execution.\n\nTo request access to the platform, contact our sales team at [https://web.sovtes.ua](https://web.sovtes.ua).\n\nSovtes is developed by a Ukrainian team. We continue to support humanitarian initiatives in Ukraine: [https://u24.gov.ua/](https://u24.gov.ua/)\n\n## Support\n\nEmail: [office@sovtes.ua](https://mailto:office@sovtes.ua)  \nPhone number: +38 044 334 70 29\n\nFor incident reports, include endpoint, request, response, timestamp and error details where possible.\n\n### Scheduled maintenance window\n\nThe platform performs scheduled maintenance daily **between 02:00 and 03:00 Europe/Kyiv time**. Temporary API unavailability may occur during this period. Scheduled synchronisation and batch integrations should avoid this window where possible.\n\n# User types\n\nThe following user types are supported.\n\n| Role | Description | API Coverage |\n| --- | --- | --- |\n| **Shipper** | Organisation that orders transport, creates routes and tenders. | ✅ Supported |\n| **Carrier** | Organisation that proposes vehicles, participates in tenders and executes transport operations. | ✅ Supported |\n| **Forwarder** | Oversight role operating above shipper and carrier workflows. | ⌛ Planned |\n| **Admin** | Internal administrative role. | Not supported |\n| **Accountant** | Limited operational role associated with shipper organisations. | Not supported |\n| **Warehouser** | Operational role responsible for warehouse and yard activities during vehicle arrival and departure. | Not supported |\n\nRole-based access control is planned for 2027.\n\n## User Groups\n\nUsers may belong to cross-account user groups configured by an administrator (see Account / Account Switching folder). User groups allow quick account switching between related operational contexts.\n\nTypical use case:\n\n- a company operating both as **shipper** and **carrier**\n    \n- a shipper organisation operating its own fleet\n    \n- shared operational management across multiple accounts\n    \n\n# Getting started\n\nTo access the API, you must:\n\n- have an active Sovtes account\n    \n- have API access enabled for your organisation\n    \n- obtain the required integration settings from: `Settings → API`\n    \n\n## Authentication\n\nAPI access uses standard Sovtes user authentication. Successful authentication returns an access token valid for **10 hours**, which must be supplied with subsequent API requests. Expired tokens require re-authentication.\n\nAdditional integration parameters, including an integration token and a MAC signing key are available in: `Settings → API`.\n\n### Session behaviour\n\nSuccessful authentication invalidates existing active sessions associated with the same user account.\n\nThis applies across:\n\n- API sessions\n    \n- Android app sessions\n    \n- mobile web app sessions\n    \n- classic web app sessions\n    \n- V3 web app sessions\n    \n\nIntegrations should avoid sharing interactive user credentials across multiple concurrent systems where uninterrupted session continuity is required.\n\nTo assign a manager or operational owner during creation, provide the user's email address in the `userclient_email` field when calling:\n\n- `POST createRoute`\n    \n- `POST createTender`\n    \n\n## Base URLs\n\nSandbox environment: `https://test.sovtes.ua`  \nProduction environment: `https://sovtes.ua`\n\n## Language support\n\nPrimary platform languages: English (`en`) and Ukrainian (`ua`).\n\nAdditional localisations are available for selected modules. Coverage and terminology consistency may vary.\n\nThe `Language` request header is required throughout the API. By default, responses use the language configured for the authenticated platform user. The `Language` header acts as a fallback mechanism and is primarily used when user language information cannot be resolved, for example during authentication failures or invalid token scenarios.\n\n## Rate limiting\n\nAuthentication endpoints are protected against excessive request activity. Excessive authentication behaviour may result in IP address being blocked.\n\nAPI requests are limited to 300 requests per minute per access token and IP address. If the limit is exceeded, the API returns `429 Too Many Requests` with a `Retry-After` header indicating when requests can be resumed.\n\n| Code | Meaning |\n| --- | --- |\n| `429 Too Many Requests` | Request activity limit exceeded |\n| `403 Forbidden` | Access temporarily restricted or blocked |\n\n## Typical shipper integration flow\n\nHere is an example of a typical tender procurement workflow:\n\n| Step | Operation | Endpoint |\n| --- | --- | --- |\n| 1 | Create tender | `POST createTender` |\n| 2 | Retrieve carrier bids | `GET getPricequotes` |\n| 3 | Select winning bid | `POST pickTenderWinner` |\n| 4 | Publish route for winning carrier | `POST publishTenderChild` |\n| 5 | Confirm carrier assignment | `POST ratifyOperator` |\n| 6 | Retrieve assigned driver and vehicle details | `GET getRouteFleet` |\n\nWinner selection, child route publication and assignment confirmation may alternatively be performed automatically via platform settings.\n\n# API status\n\n⚠️ This API and this documentation are currently under active development. Minor inconsistencies between documentation and platform behaviour may exist during ongoing platform updates.\n\n## API versioning and compatibility\n\nSovtes API v2 follows a backwards-compatible versioning approach.\n\nMinor platform releases may introduce:\n\n- new endpoints\n    \n- additional response fields\n    \n- optional parameters\n    \n- new event types\n    \n- additional operational workflows\n    \n\nExisting integrations are designed to continue operating without modification wherever possible. Breaking changes are avoided within the same major API version.\n\n## Previous API versions\n\nDocumentation for previous API generations is available for organisations maintaining historical integrations.\n\n- API v1.5 Documentation: [https://sovt.es/dF5](https://sovt.es/dF5)\n    \n- API v1.0m Documentation: [https://sovt.es/mknzv](https://sovt.es/mknzv)\n    \n- Legacy XML API v0.9 Documentation: [https://sovt.es/tDP](https://sovt.es/tDP)\n    \n\n# Webhooks\n\nSovtes supports outbound webhook notifications for operational events within the platform. If permitted by your subscription configuration, webhook events can be delivered to a user-defined HTTPS endpoint.\n\nWebhook configuration is available in: `Settings → API` and `Settings → Notifications`.\n\n## Webhook behaviour\n\nWebhook payloads notify your system that an event has occurred. Webhook payloads intentionally do not contain full operational content.\n\nFor example:\n\n- if a new document is added, the webhook will notify your system that a new document exists\n    \n- the actual document content must then be retrieved via the REST API\n    \n\nThis approach helps maintain predictable payload structures and reduces unnecessary data transfer.\n\n## Example webhook payload\n\n``` json\n{\n  \"body\": {\n    \"moment\": \"2025-05-10 19:15:04\",\n    \"event\": 12,\n    \"message\": \"Attention! New message received in route #12345-05-25 (Ukraine -> Germany).\",\n    \"route\": {\n      \"periodic\": \"12345-05-25\",\n      \"apicode\": \"880-19100-052025\",\n      \"guiurl\": \"https://sovtes.ua/a/index.php?p=view&id=12345-05-25&m=shipping\",\n      \"apiurl\": \"https://sovtes.ua/a/v2/rest/public/singleRoute?route=12345-05-25\"\n    }\n  },\n  \"signature\": \"d0c80fc9279b63f93a5b03g1d8a833de719f5766b30aad718ac58a39bbfa63c7\"\n}\n\n ```\n\nPayload fields:\n\n- `body.moment` Timestamp of the event in the application timezone. Default timezone: Europe/Kyiv.\n    \n- `body.event` Internal identifier of the event type. See _Event reference_ below.\n    \n- `body.message` Human-readable event description.\n    \n- `body.route` Contains route or tender references associated with the event, including: platform route reference, external API identifier, web application URL, API endpoint for detailed retrieval\n    \n- `signature` SHA-256 MAC signature generated from the entire `body` object using your MAC signing key. The signature should always be verified on your side to ensure: payload authenticity, payload integrity, and request source validation. Your MAC signing key is available in: `Settings → API`\n    \n\n## Event reference\n\nEvents for shippers:\n\n| ID | Event |\n| --- | --- |\n| 2 | Transport proposal received |\n| 3 | Tender bid received |\n| 114 | Carrier accepted counteroffer |\n| 115 | Carrier declined counteroffer |\n| 107 | Tender ended |\n| 18 | Carrier confirmed assignment |\n| 8 | Selected carrier refused route execution |\n| 106 | Winning carrier refused transport execution |\n| 10 | Vehicle arrived at loading |\n| 19 | Warehouse confirmed loading |\n| 12 | Route updates requested |\n| 13 | New route message received |\n| 101 | Vehicle arrived at customs |\n| 102 | Vehicle cleared customs |\n| 103 | Vehicle arrived at the border |\n| 104 | Vehicle crossed the border |\n| 15 | Vehicle arrived at unloading |\n| 20 | Warehouse confirmed unloading |\n| 120 | Carrier confirmed unloading |\n| 25 | Partner uploaded a document to the route |\n| 113 | Delivery accepted with issues |\n\nEvents for carriers:\n\n| ID | Event |\n| --- | --- |\n| 1 | New route available |\n| 29 | New private tender received |\n| 30 | New open tender received |\n| 108 | Tender scheduled |\n| 23 | New route available under your tender |\n| 26 | Route price updated |\n| 105 | New route published exclusively for you |\n| 4 | Another carrier placed a lower bid |\n| 5 | Customer selected your bid |\n| 6 | Customer approved your transport proposal |\n| 7 | Customer declined your transport proposal |\n| 9 | Time for loading |\n| 11 | Vehicle loaded |\n| 12 | Route updated |\n| 13 | New route message received |\n| 14 | Time for unloading |\n| 16 | Vehicle unloaded |\n| 109 | Customer extended the tender |\n| 121 | Tender starting bid updated |\n| 22 | Tender you won has been completed |\n| 25 | Partner uploaded a document to the route |\n| 110 | Customer approved vehicle replacement |\n| 111 | Driver delayed at unloading |\n| 112 | Driver confirmed route completion |\n| 113 | Delivery accepted with issues |\n\n# Response codes\n\nThe API uses standard HTTP response codes to indicate the result of a request.\n\n## Success responses\n\n| Code | Meaning |\n| --- | --- |\n| `200 OK` | Request completed successfully |\n| `201 Created` | Resource created successfully |\n| `202 Accepted` | Request accepted and awaiting further action |\n| `204 No Content` | Request completed successfully with no response body |\n\n## Error responses\n\n| Code | Meaning |\n| --- | --- |\n| `400 Bad Request` | Invalid request data or validation failure |\n| `401 Unauthorized` | Missing or invalid authentication token |\n| `402 Payment Required` | An outstanding invoice is past due |\n| `403 Forbidden` | Access denied by scopes, ownership etc |\n| `406 Not Acceptable` | Request could not be processed in the requested format |\n| `424 Failed Dependency` | Upstream dependency or internal processing failure |\n| `429 Too Many Requests` | Request rate limit exceeded or too many login attempts |\n\n### Error response format\n\nError responses are returned in JSON format.\n\n``` json\n{\n  \"status\": \"error\",\n  \"message\": \"Invalid token\"\n}\n\n ```\n\n### Error response fields\n\n| Field | Type | Description |\n| --- | --- | --- |\n| `status` | string | Response status (`error`) |\n| `message` | string | Human-readable error description |\n\n### `Data is corrupt` error\n\n`POST createRoute` and `POST createTender` may return `ERROR: Data is corrupt` when the MAC signature is calculated incorrectly. Verify MAC generation on your side, including correct handling of quotation marks, character escaping, whitespace and unexpected special characters.\n\n# Changelog\n\n| Version | Release Date | Highlights |\n| --- | --- | --- |\n| **v2.9.99130** | 05 Oct 2026 | Expanded APIs for route updates, route publication, tenders, cooperation and external functions, with improved validation, data handling, and API reliability. |\n| **v2.9.99129** | 14 Sep 2026 | Expanded APIs for checkpoints, tenders, invitations and route workflows, with improved validation, access control, rate limiting, timezone handling, and API reliability. |\n| **v2.9.99128** | 31 Aug 2026 | Expanded APIs for tachograph data, route checkpoints, carrier invitations and vehicle data, alongside backend reliability and security improvements. |\n| **v2.9.99127** | 18 Aug 2026 | Expanded APIs for routes, locations, partners, accounting integrations, and other operational workflows. |\n| **v2.9.99126** | 03 Aug 2026 | Improved container tracking capabilities, expanded eCMR integration, enhanced APIs, and improved platform stability and operational workflows. |\n| **v2.9.99125** | 21 July 2026 | Performance and reliability improvements across route creation, tender processing, APIs, and eCMR workflows. |\n| **v2.9.99124** | 08 July 2026 | Enhanced platform stability with improvements to eCMR, tender management, APIs, notifications, and operational workflows. |\n| **v2.9.99123** | 22 June 2026 | Major platform security upgrade, delivering improved performance, expanded APIs, and extensive stability enhancements across tender, route, and transport workflows. |\n| **v2.9.99122** | 24 Apr 2026 | Route deletion compatibility, tender extension accuracy |\n| **v2.9.99121** | 17 Apr 2026 | Billing grace-period support, tender archive corrections, reference data consistency, customs data retention |\n| **v2.9.99120** | 7 Apr 2026 | Improved route time accuracy, blind tender bid counts, expanded location search, more reliable sorting |\n| **v2.9.99119** | 20 Mar 2026 | Stronger data validation, cleaner tender results, better winner chronology, expanded checkpoint details |\n| **v2.9.99118** | 12 Mar 2026 | Consistent timezone handling, message count visibility, better checkpoint tracking, blind tender note fixes |\n| **v2.9.99117** | 20 Feb 2026 | Miles-based distance support, more accurate route distance, safer token sessions, stronger tender privacy |\n| **v2.9.99116** | 9 Feb 2026 | Flexible profile settings, reliable document downloads, improved tender statuses, stronger access controls |\n| **v2.9.99115** | 25 Jan 2026 | Payment status visibility, smoother invite acceptance, more reliable uploads, more accurate route pricing |\n| **v2.9.99114** | 20 Jan 2026 | Payment request workflows, invoice and tariff tools, online payment support, profile and message updates |\n| **v2.9.99113** | 26 Dec 2025 | Webhook and notification controls, vehicle and geography tools, Telegram connection options, payment request exports |\n| **v2.9.99112** | 17 Dec 2025 | User and document setup, company profile controls, partner access management, feedback and service agreement |\n| **v2.9.99111** | 2 Dec 2025 | Partner discovery and invites, route and tender search, route change workflows, arrival estimate support |\n| **v2.9.99110** | 18 Nov 2025 | Application file downloads, partner workflow fixes, clearer award traceability, Sigfox integration |\n| **v2.9.99108** | 17 Oct 2025 | Proof-of-delivery support, open partner discovery, vehicle record updates, clearer route action labels |\n| **v2.9.99107** | 2 Oct 2025 | Accurate tender ownership, cleaner text presentation, improved opt-out handling |\n| **v2.9.99106** | 22 Sep 2025 | Stronger tender confidentiality, more reliable route lists, settings-driven behaviour, general stability improvements |\n| **v2.9.99105** | 12 Sep 2025 | Partner detail access, fleet management improvements, document add/remove support, customer-specific behaviour |\n| **v2.9.99104** | 29 Jul 2025 | Route detail enhancements, route action visibility, fleet endpoint expansion |\n| **v2.9.99103** | 21 Jul 2025 | Route grouping support, better workload organisation |\n| **v2.9.99102** | 1 Jul 2025 | Richer route detail views, more secure blind tenders, improved bookmarked tenders, better password recovery |\n| **v2.9.99101** | 16 Jun 2025 | Friendlier error messages, tender bookmarking, better bid history, token-based sign-in |\n| **v2.9.97** | 11 Jun 2025 | Current tender visibility, duplicate order prevention, tighter carrier privacy, more accurate pricing views |\n| **v2.9.99100** | 28 May 2025 | Updated tender groupings, richer route detail responses, tender deadline visibility, tender bookmarking |\n| **v2.9.99** | 12 May 2025 | New routing endpoints, distance detail visibility, better address handling, more reliable location logic |\n| **v2.9.98** | 21 Apr 2025 | Customs workflow improvements, surcharge and penalty support, clearer route deletion errors, sign-in response consistency |\n| **v2.9.96** | 28 Mar 2025 | Stronger order audit trail, safer shipment status handling |\n| **v2.9.95** | 29 Jan 2025 | Richer route list context, better booking visibility |\n| **v2.9.94** | 20 Jan 2025 | Correct tender contacts, cleaner partner communication |\n| **v2.9.93** | 13 Jan 2025 | Tender restart refinements, more accurate child budgets, legacy route creation fixes, vehicle type data support |\n| **v2.9.91** | 20 Nov 2024 | Expanded route chronology, lookup by API code |\n| **v2.9.52** | 11 Oct 2024 | Tender winner visibility, carrier details in results |\n| **v2.9.4** | 18 Sep 2024 | Recipient lookup support, simpler message addressing |\n| **v2.9.2** | 21 Aug 2024 | New companies in filters, better partner discoverability |","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","isPublicCollection":false,"owner":"1387425","team":1011257,"collectionId":"1f6bf01f-a106-4deb-a284-eb781e99e155","publishedId":"TVem9oaa","public":true,"publicUrl":"https://apidocs.sovtes.ua","privateUrl":"https://go.postman.co/documentation/1387425-1f6bf01f-a106-4deb-a284-eb781e99e155","customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"EF5B25"},"documentationLayout":"classic-double-column","customisation":null,"version":"8.12.8","publishDate":"2022-10-04T22:32:49.000Z","activeVersionTag":"latest","documentationTheme":"light","metaTags":{},"logos":{}},"statusCode":200},"environments":[],"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/c5cd3951733280c743f6a9fa98db279b6db6e28198c36ba16931315b328a2e90","favicon":"https://sovtes.ua/favicon.ico"},"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"}],"canonicalUrl":"https://apidocs.sovtes.ua/view/metadata/TVem9oaa"}