You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .speakeasy/out.openapi.yaml
+34-11Lines changed: 34 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -11847,7 +11847,7 @@ paths:
11847
11847
description: |-
11848
11848
An array of payment methods that are allowed to be used for this payment link. When this parameter is not provided or is an empty array, all enabled payment methods will be available.
An array of payment methods that are allowed to be used for this payment link. When this parameter is not provided or is an empty array, all enabled payment methods will be available.
An array of payment methods that are allowed to be used for this payment link. When this parameter is not provided or is an empty array, all enabled payment methods will be available.
Link a new or existing organization to your OAuth application, in effect creating a new client. The response contains a `clientLink` where you should redirect your customer to.
26805
26805
26806
-
The `clientLink` URL behaves similar to the regular OAuth authorization URL. It supports the following parameters from the [Authorize](authorize) endpoint:
26806
+
## Redirecting the Customer
26807
26807
26808
-
* `client_id`
26809
-
* `state`
26810
-
* `approval_prompt`
26811
-
* `scope`
26808
+
The `clientLink` URL behaves similarly to a standard OAuth authorization URL. Therefore, after receiving the `clientLink` URL in the API response, you need to **append the following query parameters** *before* redirecting the customer:
26812
26809
26813
-
We recommend at least requesting the scopes `onboarding.read onboarding.write` this way.
26810
+
* `client_id` _string (required)_
26814
26811
26815
-
Error handling is also dealt with similar to the [Authorize](authorize) endpoint: the customer is redirected back to your app's redirect URL with the `error` and `error_description` parameters added to the URL.
26812
+
The client ID you received when you registered your OAuth app. The ID starts with `app_`. For example: `app_abc123qwerty`.
26813
+
26814
+
* `state` _string (required)_
26815
+
26816
+
A random string **generated by your app** to prevent CSRF attacks. This will be reflected in the `state` query parameter when the user returns to the `redirect_uri` after authorizing your app.
26817
+
26818
+
* `scope` _string (required)_
26819
+
26820
+
A space-separated list of permissions ('scopes') your app requires. See the [permissions list](https://docs.mollie.com/docs/connect-permissions) for more information about the available scopes.
26821
+
26822
+
We recommend at least : `onboarding.read onboarding.write`
26823
+
26824
+
* `approval_prompt` _string_
26825
+
26826
+
Can be set to `force` to force showing the consent screen to the merchant, *even when it is not necessary*. If you force an approval prompt and the user creates a new authorization, previously active authorizations will be revoked.
26827
+
26828
+
Possible values: `auto` `force` (default: `auto`)
26829
+
26830
+
### Example of a Complete Redirect URL
26831
+
26832
+
After adding the above url parameter your URL will look something like this and you can redirect your client to this page:
Error handling is also dealt with similar to the [Authorize](https://docs.mollie.com/reference/authorize) endpoint: the customer is redirected back to your app's redirect URL with the `error` and `error_description` parameters added to the URL.
26816
26839
26817
26840
> 🔑 Access with
26818
26841
>
@@ -37757,7 +37780,7 @@ components:
37757
37780
description: |-
37758
37781
An array of payment methods that are allowed to be used for this payment link. When this parameter is not provided or is an empty array, all enabled payment methods will be available.
0 commit comments