{"activeVersionTag":"latest","latestAvailableVersionTag":"latest","collection":{"info":{"_postman_id":"1eb83c82-8f6f-4659-9d2f-c5d6d79130ed","name":"1. Core Practice API V2","description":"Welcome to the Core Practice API Integration! Join Core Practice community of dentist for more efficient collaboration, task automation and streamline workflows.\n\nThis documentation offers a well-defined route to begin integrating with the Core Practice API, directing you through the steps required to achieve certification for your integration. It details the Authentication process and how to gain access to essential practice data. This includes information on practice locations, calendar settings, appointment bookings and their availability, comprehensive reporting features, and patient records\n\n# 2\\. Getting Started Guide\n\nThis guide provides step-by-step instructions on how to get started with integrating Core Practice's functionalities. Follow the steps below to gain access, create your API keys, request support, and begin building your app.\n\n#### Step 1: Get Access to Sandbox Environment\n\nBefore you can start building with the Core Practice API, you'll need to gain access to our sandbox environment. This environment is designed to provide you with a safe space to test and develop your application without affecting real data or operations.\n\nTo request access to the sandbox environment, first contact our sales team to obtain an active API subscription. Once your subscription is confirmed, reach out to our customer support team and provide details about your project and intended use of the Core Practice API by completing the [Become a Core Practice Partner](https://form.jotform.com/Core_Support/become-a-core-practice-partner) form. Our team will review your request and, if approved, send an invitation to create a user account in the sandbox environment.\n\n#### Step 2: Create Sandbox API Key\n\nAPI keys are essential for authenticating and securing communication between your application and the Core Practice API. Follow these steps to create your API keys:\n\n- **Create Sandbox Account**: If your request has been accepted, you should receive an email to create a user account in the sandbox environment.\n    \n- **Navigate to Settings**: Log in to your Core Practice account and navigate to the `Settings` section.\n    \n- **Access API Keys**: Navigate to `Settings` > `INTEGRATION` and click on `API Keys`.\n    \n- **Create API Keys**: Click on the `Create API Keys` button. You will be prompted to enter a name for your key pair and select the permissions you require.\n    \n- **Save Key and Secret**: Ensure you save the Key and Secret in a safe place. These credentials are crucial for your application's access to the Core Practice API and cannot be retrieved if lost.\n    \n\n#### Step 3: Set Up Sandbox Subscription Key\n\nBefore using your API keys, you need to set up your sandbox subscription key:\n\n- **Create Core PracticeAccount:** Use this link to create a Core Practice account: [Sign up - Core Practice API Management - Developer Portal](https://core-syd-api01.developer.azure-api.net/signup).\n    \n- **Create Sandbox Subscription:** After logging in, navigate to [Products: Details - Core Practice API Management - Developer Portal](https://core-syd-api01.developer.azure-api.net/product#product=sandbox) to create your own sandbox subscription key (\\[your new production subscription name\\]) under sandbox Tier.\n    \n- **Save Subscription Key:** A subscription key will be generated—ensure you save both primary key and secondary key securely, as the primary key will be required for API authentication.\n    \n\n#### Step 4: Create Support Request\n\nTo activate your API key and set up your application's `redirect_uri`, you need to create a support request:\n\n- **Navigate to the support request form** at [Core Practice Support](https://support.corepractice.com.au/hc/en-us/requests/new).\n    \n- **Select \"Technical\"** as the category and specify that you \"need help with Core Practice API.\"\n    \n- **In your request, provide us with** the created `api key` and the **`redirect_uri`** for your application. This URI is where users will be redirected after authenticating with Core Practice.\n    \n\n#### View API Documentation and Start Building\n\nWith your API key activated and your development environment set up, you're ready to start building your application. Visit the Core Practice API documentation at [https://docs.corepractice.io](https://docs.corepractice.io) to find comprehensive guides\n\n# 3\\. Integration Checkpoints\n\nTo become certified, your integration with Core Practice must meet certain minimum requirements. These include establishing a secure OAuth flow for app adoption, creating a user-friendly connection setup page, adhering to branding guidelines, managing scopes efficiently, handling errors transparently, and ensuring data integrity.\n\nYour integration will be evaluated based on these checkpoints, so it is crucial to review and align your integration with them before requesting a production key.\n\n\\*Note: Additional requirements may apply, depending on the specific features of your integration.\n\n#### **Checkpoint 1: Activate Core Practice**\n\nAll partner applications **must** implement the official **Core Practice OAuth 2.0 Authorization Code Flow**. This ensures a secure, seamless “Connect to Core Practice” experience directly from your application.\n\n#### **Mandatory Requirements:**\n\n- You **must** initiate authentication via the official Core Practice OAuth endpoint.\n    \n- User consent and authorization **must** occur on Core Practice’s domain — never within your own interface.\n    \n- Redirect URIs must be pre-registered and HTTPS-secured.\n    \n- Upon successful authorization, your application **must securely store**:\n    \n    - The returned `refresh_token` (encrypted and server-side only)\n        \n    - The `access_token` (temporary and not persisted client-side)\n        \n- **Do not** request or store a user’s Core Practice username or password under any circumstance.\n    \n- The OAuth flow **must complete without manual intervention** from Core Practice support staff.\n    \n- Tokens must be exchanged and stored programmatically, not through copy-paste or manual entry.\n    \n\n#### **Checkpoint 2: Connection** Management Page\n\nEnsure you implement a setup page that allows users to connect to Core Practice, manage their settings for the integration, as well as disconnecting from Core Practice. Ideally, this should be made possible without assistance from your support or onboarding team.\n\n#### **Required Features:**\n\n- Display the name of the tenant and the URL that has been connected. The tenant name can be practice name or location name, the Core Practice URL (\\*.corepractice.io) can be obtained from the client upon integration request.\n    \n- Provide user with a button to connect to Core Practice.\n    \n- Show the status of connections with Core Practice for connection management. If status is disconnected, provide a button to reconnect to Core Practice(reinitiates OAuth flow).\n    \n- Include a button to disconnect the integration (revokes tokens and clears credentials).\n    \n- Core Practice can have multiple practice locations within a tenant instance. Your integration must explicitly define whether it supports **Single-location connections**, or **Multi-location selection.** If multi-location support is provided, your app must:\n    \n    - Prompt the user to select the active Practice Location post-authentication\n        \n    - Clearly display the selected location name and ID in your settings UI\n        \n    - Handle data synchronization appropriately per selected location\n        \n- When a user disconnects their Core Practice account:\n    \n    - All stored tokens (`access_token`, `refresh_token`) **must be deleted immediately**\n        \n    - Any scheduled sync jobs, background data pulls, or automated updates **must stop within 1 hour**\n        \n    - The disconnection event should be logged and auditable\n        \n- Core Practice reserves the right to **revoke your app’s credentials** if residual data access is detected after disconnection.\n    \n\n#### **Things to Avoid:**\n\n- Never request a user's Core Practice login details within your application, always use OAuth for authentication and let the user authorize the integration.\n    \n- Avoid using automatic processes to manage the Access Token lifecycle, including expiry and renewal. Each time you require a new Access Token, utilize the previously saved Refresh Token to exchange for a new Access Token and Refresh Token. You will need to save this Refresh Token for future use.\n    \n- **Do not reuse refresh tokens.** Refresh tokens are valid for up to 90 days. Any attempt to reuse a refresh token will result in the invalidation of all active tokens for security reasons.\n    \n- It is important to store the Refresh Token in a secure location; if it's compromised, it could allow anyone to generate new Access Tokens for that user with the same permissions.\n    \n- Avoid the use of pop-up windows or new tabs in the authentication process. Redirecting users to Core Practice in a pop-up window can be blocked by a pop-up blocker.\n    \n- Never show or store sensitive data like the access token, client ID, and client secret on the client side of the application (e.g., frontend of a web app or local configuration files for native apps).\n    \n\n#### **Checkpoint 3: Branding and Naming**\n\n- The application name must reflect the go-to-market name of your app or product and cannot include the word 'Core Practice.'\n    \n- Where possible, use the \"connect\" and \"disconnect\" buttons we've provided on our branding page and the Core Practice standard logo.\n    \n\n#### **Checkpoint 4: Scopes**\n\n- Only request the minimal scopes that you require to fulfill the intended use cases of your integration. Unexplained or ambiguous use of scopes will not be permitted.\n    \n- After certification, any significant changes to use cases and scopes should be communicated to Core Practice so that we can assist you in ensuring the integration continues to meet requirements.\n    \n\n#### **Checkpoint 5: Error Handling**\n\n- Errors happen, users may remove mapped locations, temporary connectivity issues may disrupt integrations, and various other potential problems might arise. It is essential to find a way to inform users when an error has occurred within your integration.\n    \n\n#### **Checkpoint 6: Data Integrity**\n\nYour integration is responsible for maintaining **accuracy, completeness, and consistency** of data exchanged with Core Practice.\n\nAll data retrieved from Core Practice must be represented faithfully in your application, and any data your app writes to Core Practice must be validated, structured, and verified as successfully created.\n\n#### **Requirements:**\n\n- **Validate incoming data** from Core Practice before processing or displaying it. Ensure correct field mapping, data types, and encoding.\n    \n- **Verify write operations** (e.g., appointment creation and updates, patient creation and updates) by confirming successful API responses and cross-checking object IDs or timestamps.\n    \n- Implement **transactional logic or rollback mechanisms** where possible to prevent partial updates if an operation fails midway.\n    \n- Use **Core Practice Ientifiers** consistently to avoid duplication or mismatched records.\n    \n- Regularly **reconcile data** between your app and Core Practice, especially after connectivity interruptions or version updates.\n    \n- Handle **data conflicts** (e.g., the same record modified in both systems) by defining a clear conflict resolution strategy and informing users when manual review is required.\n    \n\n# 4\\. Go Live Guide\n\nCongratulations on reaching the final steps of taking your Core Practice integration live! This guide will walk you through the necessary steps to activate your API key and configure your application for production use.\n\n**Step 1: Pass the Certification Requirements**\n\nBefore proceeding to the go-live phase, **ensure that your integration meets all** [Integration Checkpoints (1-6)](https://docs.corepractice.io/#3-certification-checkpoints) for your integration with Core Practice API.\n\nYour application must already demonstrate a complete OAuth connection flow, connection management page, proper scope handling, consistent data integrity, and transparent error handling.\n\n**Step 2: Provide a Demo Video**\n\nTo confirm your application’s readiness for production, submit a **demo video** showcasing the minimum required features and compliance with Core Practice integration standards.\n\n- **Activate Core Practice:**  \n    Show how users connect using the official Core Practice OAuth 2.0 flow — no manual credential entry, no pop-ups, secure redirect only.\n    \n- **Connection Status Setup Page**: Display the setup page with tenant name, Core Practice URL, connection status, and connect/reconnect/disconnect buttons.\n    \n- **Connect OAuth Flow**: Demonstrate full OAuth authentication, including token exchange and secure server-side storage of access and refresh tokens, showing how users will sign in with their Core Practice account to your application.\n    \n- **Disconnect Integration**: Show the process for a user to disconnect the integration, ensuring that all sensitive information is securely handled, all tokens are deleted, and the disconnection is clean and user-friendly.\n    \n- **Error Handling:** Illustrate how your app informs users of lost connections, removed locations, or other errors with clear messages.\n    \n- **Data Integrity:** Show that data from Core Practice is displayed accurately, that POST/PUT updates are successful without duplication, and how the app handles or prevents invalid data entry.\n    \n- **App Feature Demonstration**: Provide a thorough demo of your app's features, emphasizing how it integrates with Core Practice and adds value to the user experience.\n    \n\n**Step 3: Submit Core Practice go-live form and Provide Test Account**\n\n- Submit **Core Practice go-live form** via this link: [Go Live Approval Form](https://form.jotform.com/Core_Support/go-live-approval-form).\n    \n- Provide a **sandbox access/test account of your integration application** for Core Practice to test the Integration connection workflow as well as features in your demo video.\n    \n\n**Step 4: Submit Production Subscription Key**\n\n- **Log into Core PracticeAccount:** Use this link to log into Core Practice Developer Portal: [Sign up - Core Practice API Management - Developer Portal](https://core-syd-api01.developer.azure-api.net/signup).\n    \n- **Create Product Subscription:** After logging in, navigate to [Products: Details - Core Practice API Management - Developer Portal](https://core-syd-api01.developer.azure-api.net/product#product=standard-tier) to create your own production subscription key (\\[your new production subscription name\\]) under Standard Tier.\n    \n- **Save Subscription Key:** A production subscription key will be generated and submitted for Core Practice approval — ensure you save both primary key and secondary key securely, as the primary key will be required for API authentication in production.\n    \n\n**Step 5: Create Support Request**\n\n- Navigate to the support request form at [Core Practice Support](https://support.corepractice.com.au/hc/en-us/requests/new).\n    \n- Select \"Technical\" as the category and specify that you \"need help with Core Practice API.\"\n    \n- Include the link to your demo video, provide test account information for accessing your integration app, let us know you have submitted our go live aprroval form and production subscription key.\n    \n- Include the production `redirect_uri` for your application in your support request as well. This URI should point to your production environment, where users will be redirected after authentication.\n    \n\n**Step 6: Await Activation Confirmation**\n\nAfter submitting your support request with all the information required, wait for confirmation from the Core Practice team. We will review your submission and provide final approval for your application to go live.\n\nOnce you've received activation confirmation and addressed any feedback, your application will be ready for deployment to the production environment.\n\nAbout your production API key and Subscription key:\n\n- We will provide you with one unique API client_id and client_secret for all production environment integration with the same redirect_uri.\n    \n- This one production API key/Subscription key will be applied for each Core Pracice client who requests for your API integration activation.\n    \n- You will not need to provide this API key/Subscription key to your Core Practice client, it will be applied by Core Practice for the client during the integration request.\n    \n\n# 5\\. API Partner Certification Guide\n\nOnce your integration has successfully gone live, you can work towards becoming a certified Core Practice API Partner and having your application listed on the Core Practice Marketplace. This partnership program is designed to showcase proven integrations that deliver value to the Core Practice community.\n\n#### Eligibility Requirements:\n\nBefore you can apply to become a Core Practice API Partner, you must meet the following criteria:  \nSuccessful Client Integrations:\n\n- Your integration must have been successfully implemented with at least 5 Core Practice clients. These pilot clients should have live, fully functional integrations that demonstrate the reliability and value of your application.\n    \n- Production Readiness: Your application must have passed all Integration Checkpoints and received go-live approval from Core Practice.\n    \n- Once you have successfully integrated 5 pilot clients and wish to connect with additional Core Practice clients, you must apply for Core Practice API Partner certification before proceeding with further integrations.\n    \n\n#### Application Process:\n\nTo apply for Core Practice API Partner certification and marketplace listing, follow these steps:\n\n**Step 1: Verify Pilot Client Success**\n\nEnsure that you have at least 5 Core Practice clients with successful, live integrations. Be prepared to provide:\n\n- Client names or identifiers (with their permission)\n    \n- Integration dates\n    \n- Brief description of how each client is using your integration\n    \n\n**Step 2: Submit Partner Approval Form**\n\nComplete and submit the Core Practice [Partner Approval Form](https://form.jotform.com/Core_Support/partner-approval-form) with all required information about your application and company.\n\n**Step 3: Provide Marketing Content**\n\nTo be listed on the Core Practice Marketplace, you must provide the following marketing content: \"Benefits of Integrating\" and \"Getting Started is Easy\". For reference and inspiration for your marketplace listing content, review existing partner listings such as: [https://www.corepractice.com.au/marketplace/apps/stripe](https://www.corepractice.com.au/marketplace/apps/stripe).\n\n**Step 4: Create Support Request**\n\n- Navigate to the support request form at [Core Practice Support](https://support.corepractice.com.au/hc/en-us/requests/new).\n    \n- Select \"Technical\" as the category and specify that you \"need help with Core Practice API.\"\n    \n- Request for being Core Practice API partner, provide us with information required in Step 1-3.\n    \n\n**Step 5: Review and Approval**\n\nThe Core Practice team will review your application, verify your client integrations, and assess your submitted marketing contents. We may request additional information or modifications to ensure your marketplace listing meets our quality standards.\n\nOnce approved, your application will be listed on the Core Practice Marketplace at [https://www.corepractice.com.au/marketplace/apps](https://www.corepractice.com.au/marketplace/apps), making it discoverable to the entire Core Practice community.\n\n#### Partnership Benefits\n\nAs a certified Core Practice API Partner, you will receive:\n\n- Listing on the Core Practice Marketplace with your custom marketing content\n    \n- Increased visibility to thousands of dental practices using Core Practice\n    \n- Official partner badge and co-marketing opportunities\n    \n- Dedicated partner support from the Core Practice team\n    \n- Priority consideration for feature requests and API enhancements\n    \n\n# Authentication API","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","isPublicCollection":false,"owner":"110969","team":178686,"collectionId":"1eb83c82-8f6f-4659-9d2f-c5d6d79130ed","publishedId":"2sA3e1CAYQ","public":true,"publicUrl":"https://docs.corepractice.io","privateUrl":"https://go.postman.co/documentation/110969-1eb83c82-8f6f-4659-9d2f-c5d6d79130ed","customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"documentationLayout":"classic-double-column","customisation":{"metaTags":[{"name":"description","value":"Join Core Practice community of dentist for more efficient collaboration, task automation and streamline workflows."},{"name":"title","value":"Core Practice API Integration documentations!"}],"appearance":{"default":"light","themes":[{"name":"dark","logo":null,"colors":{"top-bar":"212121","right-sidebar":"303030","highlight":"FF6C37"}},{"name":"light","logo":null,"colors":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"}}]}},"version":"8.10.1","publishDate":"2026-04-27T23:16:39.000Z","activeVersionTag":"latest","documentationTheme":"light","metaTags":{"title":"Core Practice API Integration documentations!","description":"Join Core Practice community of dentist for more efficient collaboration, task automation and streamline workflows."},"logos":{"logoLight":null,"logoDark":null}},"statusCode":200},"environments":[{"name":"Sandbox Gateway V2","id":"dacd56f0-728b-415e-a9c8-766699ab9b81","owner":"110969","values":[{"key":"AUTHURL","value":"https://sandbox.corepractice.is","enabled":true,"type":"default"},{"key":"APIURL","value":"https://api.corepractice.io","enabled":true,"type":"default"},{"key":"YOURCLIENTID","value":"","enabled":true,"type":"default"},{"key":"YOURCLIENTSECRET","value":"","enabled":true,"type":"default"},{"key":"TENANTID","value":"sandbox.stg","enabled":true,"type":"default"},{"key":"SUBSCRIPTIONKEY","value":"","enabled":true,"type":"default"},{"key":"YOURACCESSTOKEN","value":"","enabled":true,"type":"default"},{"key":"YOURREFRESHTOKEN","value":"","enabled":true,"type":"default"},{"key":"LOCATIONID","value":"","enabled":true,"type":"default"},{"key":"CALENDARID","value":"","enabled":true,"type":"default"},{"key":"PATIENTID","value":"","enabled":true,"type":"default"},{"key":"CHARTID","value":"","enabled":true,"type":"default"},{"key":"YOURAPIKEY","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/0947328f898ae4679754548eb22c2324118305e31929812d89eebbe831f795ce","favicon":"https://res.cloudinary.com/postman/image/upload/v1624342657/team/vp3i5hobozayziwzverp.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"},{"label":"Sandbox Gateway V2","value":"110969-dacd56f0-728b-415e-a9c8-766699ab9b81"}],"canonicalUrl":"https://docs.corepractice.io/view/metadata/2sA3e1CAYQ"}