Organisations
Choose what your big imports draw
org, parts, whole, or both, for an import too big for one picture when the call does not say.
PUT
/user/importsTL;DR
| Question | Answer |
|---|---|
| What does it do? | Choose what your big imports draw. |
| What does it take? | A JSON body of type SetUserImportLargeBody. |
| What does it return? | Status 200 with a body of type UserImportLarge. |
| What can go wrong? | 400 the body is not valid; 401 not signed in; 403 the request came from an origin that may not make changes; 429 too many requests. Every failure uses the one error envelope. |
What it does
org, parts, whole, or both, for an import too big for one picture when the call does not say. It wins over the organisation's choice.
Request body
The body has the type SetUserImportLargeBody.
| Field | Type | Required | Description |
|---|---|---|---|
large | "org" | "parts" | "whole" | "both" | yes |
Responses
| Status | Meaning | Body |
|---|---|---|
| 200 | The choice now. | UserImportLarge |
| 400 | The body is not valid. | ErrorResponse |
| 401 | Not signed in. | ErrorResponse |
| 403 | The request came from an origin that may not make changes. | ErrorResponse |
| 429 | Too many requests. | ErrorResponse |
Response body
A 200 answer has the type UserImportLarge.
| Field | Type | Required | Description |
|---|---|---|---|
large | "org" | "parts" | "whole" | "both" | yes | What your imports too big for one readable picture draw on the hosted service when the call does not say: org (the organisation's choice, the default; both for a person in none), parts, whole, or both. |
See also
| Doc | Why |
|---|---|
| API reference | Every endpoint, and the error envelope |
| Schemas | Every request and response type |
| Tool reference | The operations as callable tools |