forked from loafle/openapi-generator-original

julien Lengrand-Lambert f1fcceb375

Major Jetbrains HTTP Client upgrade. Move to BETA (#15779 )

* Add notes to requests for better readability

* Adds extra configs for jetbrains http client for testing

* Adding new sample data

* Changes

* Setting up test infrastructure

* Adds body to requests.

* Fixing some bugs in map traversal

It'd be much better to use a proper library for this though

* Adding secret file to gitignore

* Adds github spec, for complex example.

Add null check to avoid errors in example extraction

* Add support for custom variables in request body

* Add support for all basic Auth headers

* Not sure whaet happened with my api mustache file

* Add support for custom headers

* Fixes empty lines issue

* Adds support for Accept header

* Adding many tests, deleting experiment files

* Updates generator doc

* Completes README file with extra information

* Runs generate-samples and export docs

* Running sample generation

* Adding missing files to samples

* Removing forgotten stdout statements

* Ignore one test making the docker image generation fail

2024-03-09 16:56:26 +08:00

2.8 KiB

Raw Blame History

Checkout Basic - Jetbrains API Client

General API description

Checkout Basic

API basepath : https://checkout-test.adyen.com/v71
Version : 1.0.0

Documentation for API Endpoints

All URIs are relative to https://checkout-test.adyen.com/v71, but will link to the .http file that contains the endpoint definition. There may be multiple requests for a single endpoint, one for each example described in the OpenAPI specification.

Class	Method	HTTP request	Description
PaymentsApi	getPaymentMethodById	GET /paymentMethods/{id}	Get payment method by id
PaymentsApi	getPaymentMethods	GET /paymentMethods	Get payment methods
PaymentsApi	postMakePayment	POST /payments	Make a payment

Usage

Prerequisites

You need IntelliJ to be able to run those queries. More information can be found here. You may have some luck running queries using the Code REST Client as well, but your mileage may vary.

Variables and Environment files

Generally speaking, you want queries to be specific using custom variables. All variables in the .http files have the `` format.
You can create public or private environment files to dynamically replace the variables at runtime.

Note: don't commit private environment files! They typically will contain sensitive information like API Keys.

Customizations

If you have control over the generation of the files here, there are two main things you can do

Select elements to replace as variables during generation. The process is case-sensitive. For example, API_KEY ->
- For this, run the generation with the bodyVariables property, followed by a "-" separated list of variables
- Example: --additional-properties bodyVariables=YOUR_MERCHANT_ACCOUNT-YOUR_COMPANY_ACCOUNT-YOUR_BALANCE_PLATFORM
Add custom headers to all requests. This can be useful for example if your specifications are missing security schemes.
- For this, run the generation with the customHeaders property, followed by a "&" separated list of variables
- Example : --additional-properties=customHeaders="Cookie:X-API-KEY="&"Accept-Encoding=gzip"

This client was generated by the jetbrains-http-client generator of OpenAPI Generator

2.8 KiB Raw Blame History