This Open API specification serves as a standardized framework for describing and defining the capabilities of the AirPay. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Airline. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Air Transat. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
**Proprietário:** [Agrotis](https://www.agrotis.com.br/) **Sistema:** Agrotis Plataforma **Módulo:** [Produção Rural](https://www.agrotis.com.br/solucoes/producao-rural/) **Descrição:** Documentação básica das API's para sincronização de dados e operações. **ATENÇÃO!** Por questões de segurança e performance, atualmente **há um limite de 5 requisições por segundo, por IP de origem**.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Agriconecta. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
# Adyen Webhooks Webhooks are an essential feature of the Adyen platform. They deliver events like payment outcome, new chargebacks, availability of a report, updates on merchant onboarding, and so on, and therefore it is important to ensure they can be received, consumed and tested during the development of your specific Adyen integration. This collection contains several examples of the webhooks delivered by Adyen. ## How to use it ### Fork Fork the collection in your own private workspace ### Config Define the collection variables: - `baseUrl`: url of the webhook handler (i.e localhost:8080) - `path`: path of the webhoon handler (i.e. /api/webhooks/notifications) - `YOUR_MERCHANT_ACCOUNT`: your merchant account (if applicable) - `YOUR_BALANCE_PLATFORM`: your balance platform (if applicable) - `YOUR_LEGAL_ENTITY`: your legal entity (if applicable) - `HMAC_KEY`: HMAC key to sign the payload Ignore the Collection variable `HMAC_SIGNATURE` (it is calculated when sending the request) ### Send Send the requests to your application ## Report an issue Let us know about problems or improvements by creating a [GitHub](https://github.com/adyen/adyen-postman) issue. ## References [Webhooks](https://docs.adyen.com/development-resources/webhooks) on Adyen docs Consuming webhooks [blog](https://www.adyen.com/blog/consuming-webhooks) and [video](https://www.youtube.com/watch?v=pwR4A4KLVuI&t=447s)
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Aeroprime KCX Integration. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
API for Aegis Eternal
The Test Cards API provides endpoints for generating custom test card numbers. For more information, refer to [Custom test cards](https://docs.adyen.com/development-resources/testing/create-test-cards) documentation.
The Recurring APIs allow you to manage and remove your tokens or saved payment details. Tokens should be created with validation during a payment request. For more information, refer to our [Tokenization documentation](https://docs.adyen.com/developers/features/tokenization). ## Authentication To connect to the Recurring API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/developers/user-management/how-to-get-the-web-service-ws-user-password). Then use its credentials to authenticate your request, for example: ``` curl -U "ws@Company.YourCompany":"YourWsPassword" \ -H "Content-Type: application/json" \ ... ``` Note that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/developers/development-resources/live-endpoints). ## Versioning Recurring API supports versioning of its endpoints through a v Contact Support: Name: No Contact Email: email@example.com
A set of API endpoints to manage stored value products.
The Recurring APIs allow you to manage and remove your tokens or saved payment details. Tokens should be created with validation during a payment request. For more information, refer to our [Tokenization documentation](https://docs.adyen.com/online-payments/tokenization). ## Authentication You need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API. If using an API key, add an `X-API-Key` header with the API key as the value, for example: ``` curl -H "Content-Type: application/json" \n-H "X-API-Key: YOUR_API_KEY" \n... ``` Alternatively, you can use the username and password to connect to the API using basic authentication, for example: ``` curl -U "ws@Company.YOUR_COMPANY_ACCOUNT":"YOUR_BASIC_AUTHENTICATION_PASSWORD" \n-H "Content-Type: application/json" \n... ``` ## Versioning Recurring API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``` https://pal-test.adyen.com/pal/servlet/Recurring/v68/disable ``` ## Going live To authenticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area. The live endpoint URLs contain a prefix which is unique to your company account: ``` https://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/Recurring/v68/disable ``` Get your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.
A set of API endpoints that allow you to store payout details, confirm, or decline a payout. For more information, refer to [Online payouts](https://docs.adyen.com/checkout/online-payouts). Contact Support: Name: No Contact Email: email@example.com
A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods. To learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration). ## Authentication To connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/user-management/how-to-get-the-web-service-ws-user-password). Then use its credentials to authenticate your request, for example: ``` curl -U "ws@Company.YourCompany":"YourWsPassword" \ -H "Content-Type: application/json" \ ... ``` Note that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints). ## Versioning Payments Contact Support: Name: No Contact Email: email@example.com
The MarketPay Funding API provides endpoints for managing the funds in MarketPay accounts. These management operations include actions such as the transfer of funds from one account to another, the payout of funds to an account holder, and the retrieval of balances in an account. For further information on MarketPay fund management, please visit the [MarketPay documentation](https://docs.adyen.com/developers/marketpay). ## Authentication To connect to the MarketPay API, you must use basic authentication credentials of your web service user. If you don't have one, please contact the [Adyen Support Team](https://support.adyen.com/hc/en-us/requests/new). Then use its credentials to authenticate your request, for example: ``` curl -U "ws@MarketPlace.YourMarketPlace":"YourWsPassword" \ -H "Content-Type: application/json" \ ... ``` Note that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/developers/development-re Contact Support: Name: No Contact Email: email@example.com
The MarketPay Notification Configuration API provides endpoints for configuration a subscription to a marketplace's MarketPay-related notifications. Notifications are sent upon the occurrence of certain events (such as a KYC check completion or a payout completion), and the subscription to these notifications dictates to where they are sent. For further information on MarketPay notifications, please visit the [MarketPay documentation](https://docs.adyen.com/marketpay). ## Authentication To connect to the MarketPay API, you must use basic authentication credentials of your web service user. If you don't have one, please contact the [Adyen Support Team](https://support.adyen.com/hc/en-us/requests/new). Then use its credentials to authenticate your request, for example: ``` curl -U "ws@MarketPlace.YourMarketPlace":"YourWsPassword" \ -H "Content-Type: application/json" \ ... ``` Note that when going live, you need to generate new web service user credentials to access the [live endpoints Contact Support: Name: No Contact Email: email@example.com
The MarketPay Funding API provides endpoints for managing the funds in MarketPay accounts. These management operations include actions such as the transfer of funds from one account to another, the payout of funds to an account holder, and the retrieval of balances in an account. For further information on MarketPay fund management, please visit the [MarketPay documentation](https://docs.adyen.com/marketpay). ## Authentication To connect to the MarketPay API, you must use basic authentication credentials of your web service user. If you don't have one, please contact the [Adyen Support Team](https://support.adyen.com/hc/en-us/requests/new). Then use its credentials to authenticate your request, for example: ``` curl -U "ws@MarketPlace.YourMarketPlace":"YourWsPassword" \ -H "Content-Type: application/json" \ ... ``` Note that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints Contact Support: Name: No Contact Email: email@example.com
The MarketPay Account API provides endpoints for managing MarketPay account-related entities. These related entities include account holders, accounts, bank accounts, shareholders, and KYC-related documents. The management operations include actions such as creation, retrieval, updating, and deletion of them. For further information on MarketPay API, visit the [MarketPay documentation](https://docs.adyen.com/developers/marketpay/marketpay-overview). ## Authentication To connect to the MarketPay API, you must use basic authentication credentials of your web service user. If you don't have one, please contact the [Adyen Support Team](https://support.adyen.com/hc/en-us/requests/new). Then use its credentials to authenticate your request, for example: ``` curl -U "ws@Company.YourCompany":"YourWsPassword" \ -H "Content-Type: application/json" \ ... ``` Note that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/dev Contact Support: Name: No Contact Email: email@example.com
Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort). This API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments). ## Authentication Each request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example: ``` curl -H "Content-Type: application/json" \n-H "X-API-Key: YOUR_API_KEY" \n... ``` ## Versioning Checkout API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``` https://checkout-test.adyen.com/v71/payments ``` ## Going live To access the live endpoints, you need an API key from your live Customer Area. The live endpoint URLs contain a prefix which is unique to your company account, for example: ``` https://{PREFIX}-checkout-live.adyenpayments.com/checkout/v71/payments ``` Get your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**. When preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place. ## Release notes Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=71) to find out what changed in this version!
Adyen Data Protection API provides a way for you to process [Subject Erasure Requests](https://gdpr-info.eu/art-17-gdpr/) as mandated in GDPR. Use our API to submit a request to delete shopper's data, including payment details and other related information (for example, delivery address or shopper email).## Authentication Each request to the Data Protection API must be signed with an API key. Get your API Key from your Customer Area, as described in [How to get the API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key). Then set this key to the `X-API-Key` header value, for example: ``` curl -H "Content-Type: application/json" \n-H "X-API-Key: Your_API_key" \n... ``` Note that when going live, you need to generate a new API Key to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints). ## Versioning Data Protection Service API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``` https://ca-test.adyen.com/ca/services/DataProtectionService/v1/requestSubjectErasure ```
A web service containing utility functions available for merchants integrating with Checkout APIs. ## Authentication Each request to the Checkout Utility API must be signed with an API key. For this, obtain an API Key from your Customer Area, as described in [How to get the Checkout API key](https://docs.adyen.com/developers/user-management/how-to-get-the-checkout-api-key). Then set this key to the `X-API-Key` header value, for example: ``` curl -H "Content-Type: application/json" \ -H "X-API-Key: Your_Checkout_API_key" \ ... ``` Note that when going live, you need to generate a new API Key to access the [live endpoints](https://docs.adyen.com/developers/api-reference/live-endpoints). ## Versioning Checkout API supports versioning of its endpoints through a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``` https://checkout-test.adyen.com/v1/originKeys ``` Contact Support: Name: No Contact Email: email@example.com
The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN. ## Authentication You need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API. If using an API key, add an `X-API-Key` header with the API key as the value, for example: ``` curl -H "Content-Type: application/json" \n-H "X-API-Key: YOUR_API_KEY" \n... ``` Alternatively, you can use the username and password to connect to the API using basic authentication, for example: ``` curl -U "ws@Company.YOUR_COMPANY_ACCOUNT":"YOUR_BASIC_AUTHENTICATION_PASSWORD" \n-H "Content-Type: application/json" \n... ``` ## Versioning The BinLookup API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``` https://pal-test.adyen.com/pal/servlet/BinLookup/v54/get3dsAvailability ```## Going live To authneticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area. The live endpoint URLs contain a prefix which is unique to your company account: ``` https://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v54/get3dsAvailability ``` Get your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.
The Adobe Analytics 2.0 APIs allow you to directly call Adobe's servers to perform almost any action that you can perform in the user interface. You can create reports to explore, get insights, or answer important questions about your data. You can also manage components of Adobe Analytics, such as the creation of segments or calculated metrics.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Admedia. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
The Balance Control API lets you transfer funds between merchant accounts that belong to the same legal entity and are under the same company account. ## Authentication To connect to the Balance Control API, you must authenticate your requests with an [API key or basic auth username and password](https://docs.adyen.com/development-resources/api-authentication). To learn how you can generate these, see [API credentials](https://docs.adyen.com/development-resources/api-credentials).Here is an example of authenticating a request with an API key: ``` curl -H "X-API-Key: Your_API_key" \n-H "Content-Type: application/json" \n... ``` Note that when going live, you need to generate API credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints). ## Versioning The Balance Control API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number. For example: ``` https://pal-test.adyen.com/pal/servlet/BalanceControl/v1/balanceTransfer ```
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Adjust API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
Alerts Management API enables activation, inspection, and removal of alerts generated by Acronis Cyber Protection. Tasks and Activities Management API enables inspection of tasks and activities performed by Acronis Cyber Protection. Usage Guides https://developer.acronis.com/doc/tasks/v2/guide/index Full References https://developer.acronis.com/doc/alerts/v1/reference/index#/http/getting-started https://developer.acronis.com/doc/tasks/v2/reference/index#/http/getting-started Blog Post https://developer.acronis.com/blog/posts/some-technical-aspects-of-the-integration-of-ateras-powerful-psa-and-rmm-suite-with-acronis-cyber-cloud/ Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Acronis Vault Manager API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This interface enables partner administrators to programmatically leverage all the following functionality of the platform: * View information about available resources. * View information about protection plans and policies. * Create/update/delete a protection plan. * Apply/revoke a protection plan to/from resources. * Enable and disable specific policies. Usage Guide https://developer.acronis.com/doc/resource-policy-management/v4/guide/index Full Reference https://developer.acronis.com/doc/resource-policy-management/v4/reference/index#/http/getting-started Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Actitime API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Actitime API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Acronis Vault Manager API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
Alerts Management API enables activation, inspection, and removal of alerts generated by Acronis Cyber Protection. Tasks and Activities Management API enables inspection of tasks and activities performed by Acronis Cyber Protection. Usage Guides https://developer.acronis.com/doc/tasks/v2/guide/index Full References https://developer.acronis.com/doc/alerts/v1/reference/index#/http/getting-started https://developer.acronis.com/doc/tasks/v2/reference/index#/http/getting-started Blog Post https://developer.acronis.com/blog/posts/some-technical-aspects-of-the-integration-of-ateras-powerful-psa-and-rmm-suite-with-acronis-cyber-cloud/ Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Acronis Alert Manager API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This interface enables partner administrators to programmatically leverage all the following functionality of the platform: * View information about available resources. * View information about protection plans and policies. * Create/update/delete a protection plan. * Apply/revoke a protection plan to/from resources. * Enable and disable specific policies. Usage Guide https://developer.acronis.com/doc/resource-policy-management/v4/guide/index Full Reference https://developer.acronis.com/doc/resource-policy-management/v4/reference/index#/http/getting-started Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Enables notarization, electronic signature, and authenticity verification of files and JSON objects of any size by using the Ethereum blockchain. Usage Guide https://developer.acronis.com/doc/notary/v2/guide/index Full Reference https://developer.acronis.com/doc/notary/v2/reference/index#/http/getting-started Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Provides access to secure content management features for use in your own product, including automation of file storage, sync, share, and search. Full Reference https://developer.acronis.com/doc/files/v1/reference/index#/http/getting-started Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Enables notarization, electronic signature, and authenticity verification of files and JSON objects of any size by using the Ethereum blockchain. Usage Guide https://developer.acronis.com/doc/notary/v2/guide/index Full Reference https://developer.acronis.com/doc/notary/v2/reference/index#/http/getting-started Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Automates provisioning and usage reporting of Acronis Cyber Cloud services for your customers, and serves as an identity and access management framework. Usage Guide https://developer.acronis.com/doc/account-management/v2/guide/index Full Reference https://developer.acronis.com/doc/account-management/v2/reference/index#/http/getting-started Blog Post https://developer.acronis.com/blog/posts/prototyping-acronis-cyber-platform-api-solutions-with-postman-account-management/ Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Provides access to secure content management features for use in your own product, including automation of file storage, sync, share, and search. Full Reference https://developer.acronis.com/doc/files/v1/reference/index#/http/getting-started Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Provides information about agents registered in Acronis Cyber Protection and their endpoints. Full Reference https://developer.acronis.com/doc/alerts/v1/reference/index#/http/getting-started Blog Post https://developer.acronis.com/blog/posts/automate-acronis-agent-installations/ Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Provides information about agents registered in Acronis Cyber Protection and their endpoints. Full Reference https://developer.acronis.com/doc/alerts/v1/reference/index#/http/getting-started Blog Post https://developer.acronis.com/blog/posts/automate-acronis-agent-installations/ Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
Automates provisioning and usage reporting of Acronis Cyber Cloud services for your customers, and serves as an identity and access management framework. Usage Guide https://developer.acronis.com/doc/account-management/v2/guide/index Full Reference https://developer.acronis.com/doc/account-management/v2/reference/index#/http/getting-started Blog Post https://developer.acronis.com/blog/posts/prototyping-acronis-cyber-platform-api-solutions-with-postman-account-management/ Copyright © 2019-2021 Acronis International GmbH. This is distributed under MIT license.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Acronis Alert Manager API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This is a generated connector for [Ably REST API v1.1.0](https://ably.com/documentation/rest-api) OpenAPI specification. The [Ably REST API](https://www.ably.io/documentation/rest-api) provides a way for a wide range of server and client devices to communicate with the Ably service over REST. The REST API does not provide a realtime long-lived connection to Ably, but in all other respects is a simple subset of the full [realtime messaging API](https://ably.com/documentation/realtime).
This is a generated connector for [Ably REST API v1.1.0](https://ably.com/documentation/rest-api) OpenAPI specification. The [Ably REST API](https://www.ably.io/documentation/rest-api) provides a way for a wide range of server and client devices to communicate with the Ably service over REST. The REST API does not provide a realtime long-lived connection to Ably, but in all other respects is a simple subset of the full [realtime messaging API](https://ably.com/documentation/realtime).
Accredo Web Service
Standardisierte Geschäftsobjekte zur Übertragung als Datenpakete über den Datenhub
The ABLSoft Radar API exposes selected pieces of information via a standardized programmatic interface. This is an enterprise API and it is assumed that prior to use of the Radar API your company has access or permission to access an existing Radar system. If you do not have access to an instance of Radar please contact your ABLSoft representative for more information. If you have access to a Radar system, but cannot consume the API contact your ABLSoft representative for information on enabling these services. These examples serve as a starting point to familiarize yourself with some of the capabilities of the ABLSoft Radar API. Custom API's and changes to the existing API's can be provided upon request. Contact your ABLSoft representative if you do not see your desired API available. If you have technical questions about the API please email your questions to techsupport@ablsoft.com. The API is accessed by making HTTP requests to a specific endpoint URL, in which GET or POST variables contain information about what you wish to access. Every endpoint is accessed via an SSL-enabled HTTPS (port 443) using OAuth2, Radar currently supports the OAuth2 Password Grant Type. Application developers must first obtain their CLIENT ID and SECRET CODE. This along with a valid username, password and appropriate security role to the specific Radar instance is required in order to obtain a unique OAuth2 token. To receive your assigned credentials, please contact technical support or your companies system administrator. Because all transactions are secured using the OAuth2 protocol, a valid token must first be obtained by passing the correct authentication credentials to the Radar application server. Upon successfully validating the credentials, the Radar system will return a unique OAuth2 token. This token can then be used repeatedly by the calling application to access Radar resources. Applications should store the token for later use to avoid repeating the user id and password steps in the future. Tokens expire after 1 hours; use the refresh token, or a previously generated refresh token, to retrieve a new access token when the first token expires. First, use the GET refresh token service along with your Radar credentials, retrieve the refresh token. Request: <code>$ curl --user MYCLIENTID:MYSECRETCODE https://mycompany.ablsoft.com/restapi/oauth/token -d username=myID -d password=myPWD -d grant_type=password</code> Response: <code>{"access_token":"bc156287-4662-4d5e-8c9d-51be256bda7d","token_type":"bear er","refresh_token":"368b1c65-d7a4-4eb3-9b23-c161df7262cb","expires_in":359 9,"scope":"read write"</code> Next, use the previously obtained refresh token to generate an access token. Request: <code>curl --user MYCLIENTID:MYSECRETCODE https://mycompany.ablsoft.com/restapi/oauth/token -d grant_type=refresh_token -d refresh_token=368b1c65-d7a4-4eb3-9b23-c161df7262cb</code> This access token will be used for authorization for all other API requests. As mentioned earlier, each client application must have its own unique login id and password to interface with the Radar API. The ID assigned is also tied to a security role that determines what resources the application will have access to. If you do not have access to a specific resource, contact your ABLSoft representative. To interface with a Radar web service, an HTTPS request must be formatted with the appropriate parameters as expected by the method in question. Radar web services return JSON objects by default. Depending on the method called, the JSON returned could either be a list or a single object. ABLSoft recommends testing API connectivity using the <a href="https://www.getpostman.com/docs/v6/">Postman client</a>.
Accredo Web Service