chore(docs): Updated API Reference (#3107)

* chore(docs): Generated API Reference

* small fix

Co-authored-by: olivermrbl <olivermrbl@users.noreply.github.com>
Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
This commit is contained in:
authored and GitHub committed 2023-01-25 10:28:11 +02:00
1 parent 0312eceda7
commit 4e82ec0734
3 files changed
+51 -12

No files matched your search

+17 -4
View File
@@ -18648,17 +18648,30 @@ components:
of `{api_token}`. This is where you must pass the API token. of `{api_token}`. This is where you must pass the API token.
If you're alternatively following along with the JS Client request If you're following along with the JS Client request samples, you must
samples, you must provide the `apiKey` option when creating the Medusa provide the `apiKey` option when creating the Medusa client:
client:
```js ```ts
const medusa = new Medusa({ baseUrl: MEDUSA_BACKEND_URL, maxRetries: 3, const medusa = new Medusa({ baseUrl: MEDUSA_BACKEND_URL, maxRetries: 3,
apiKey: '{api_token}' }) apiKey: '{api_token}' })
``` ```
If you're using Medusa React, you can pass the `apiKey` prop to
`MedusaProvider`:
```tsx
<MedusaProvider
apiKey='{api_token}'
//...
>
```
scheme: bearer scheme: bearer
cookie_auth: cookie_auth:
type: apiKey type: apiKey
+17 -4
View File
@@ -18648,17 +18648,30 @@ components:
of `{api_token}`. This is where you must pass the API token. of `{api_token}`. This is where you must pass the API token.
If you're alternatively following along with the JS Client request If you're following along with the JS Client request samples, you must
samples, you must provide the `apiKey` option when creating the Medusa provide the `apiKey` option when creating the Medusa client:
client:
```js ```ts
const medusa = new Medusa({ baseUrl: MEDUSA_BACKEND_URL, maxRetries: 3, const medusa = new Medusa({ baseUrl: MEDUSA_BACKEND_URL, maxRetries: 3,
apiKey: '{api_token}' }) apiKey: '{api_token}' })
``` ```
If you're using Medusa React, you can pass the `apiKey` prop to
`MedusaProvider`:
```tsx
<MedusaProvider
apiKey='{api_token}'
//...
>
```
scheme: bearer scheme: bearer
cookie_auth: cookie_auth:
type: apiKey type: apiKey
+17 -4
View File
@@ -543,17 +543,30 @@ components:
of `{api_token}`. This is where you must pass the API token. of `{api_token}`. This is where you must pass the API token.
If you're alternatively following along with the JS Client request If you're following along with the JS Client request samples, you must
samples, you must provide the `apiKey` option when creating the Medusa provide the `apiKey` option when creating the Medusa client:
client:
```js ```ts
const medusa = new Medusa({ baseUrl: MEDUSA_BACKEND_URL, maxRetries: 3, const medusa = new Medusa({ baseUrl: MEDUSA_BACKEND_URL, maxRetries: 3,
apiKey: '{api_token}' }) apiKey: '{api_token}' })
``` ```
If you're using Medusa React, you can pass the `apiKey` prop to
`MedusaProvider`:
```tsx
<MedusaProvider
apiKey='{api_token}'
//...
>
```
scheme: bearer scheme: bearer
cookie_auth: cookie_auth:
type: apiKey type: apiKey