bulkit 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +49 -5
- package/dist/index.cjs +18 -4
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +54 -24
- package/dist/index.d.ts +54 -24
- package/dist/index.js +18 -4
- package/dist/index.js.map +1 -1
- package/package.json +17 -2
package/dist/index.d.cts
CHANGED
|
@@ -2071,6 +2071,15 @@ interface operations {
|
|
|
2071
2071
|
'application/json': components['schemas']['Error'];
|
|
2072
2072
|
};
|
|
2073
2073
|
};
|
|
2074
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2075
|
+
422: {
|
|
2076
|
+
headers: {
|
|
2077
|
+
[name: string]: unknown;
|
|
2078
|
+
};
|
|
2079
|
+
content: {
|
|
2080
|
+
'application/json': components['schemas']['Error'];
|
|
2081
|
+
};
|
|
2082
|
+
};
|
|
2074
2083
|
/** @description Too fast. RETRYABLE — `Retry-After` says when, and `X-RateLimit-*` say what the ceiling was. Distinct from 402: no upgrade is needed to make this exact call succeed. */
|
|
2075
2084
|
429: {
|
|
2076
2085
|
headers: {
|
|
@@ -2183,7 +2192,7 @@ interface operations {
|
|
|
2183
2192
|
'application/json': components['schemas']['Error'];
|
|
2184
2193
|
};
|
|
2185
2194
|
};
|
|
2186
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2195
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2187
2196
|
422: {
|
|
2188
2197
|
headers: {
|
|
2189
2198
|
[name: string]: unknown;
|
|
@@ -2364,7 +2373,7 @@ interface operations {
|
|
|
2364
2373
|
'application/json': components['schemas']['Error'];
|
|
2365
2374
|
};
|
|
2366
2375
|
};
|
|
2367
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2376
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2368
2377
|
413: {
|
|
2369
2378
|
headers: {
|
|
2370
2379
|
[name: string]: unknown;
|
|
@@ -2428,7 +2437,7 @@ interface operations {
|
|
|
2428
2437
|
/**
|
|
2429
2438
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
2430
2439
|
*
|
|
2431
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
2440
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
2432
2441
|
*
|
|
2433
2442
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
2434
2443
|
*/
|
|
@@ -2488,7 +2497,7 @@ interface operations {
|
|
|
2488
2497
|
'application/json': components['schemas']['Error'];
|
|
2489
2498
|
};
|
|
2490
2499
|
};
|
|
2491
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2500
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2492
2501
|
413: {
|
|
2493
2502
|
headers: {
|
|
2494
2503
|
[name: string]: unknown;
|
|
@@ -2506,7 +2515,7 @@ interface operations {
|
|
|
2506
2515
|
'application/json': components['schemas']['Error'];
|
|
2507
2516
|
};
|
|
2508
2517
|
};
|
|
2509
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2518
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2510
2519
|
422: {
|
|
2511
2520
|
headers: {
|
|
2512
2521
|
[name: string]: unknown;
|
|
@@ -2642,7 +2651,16 @@ interface operations {
|
|
|
2642
2651
|
PublicMediaController_completeUpload: {
|
|
2643
2652
|
parameters: {
|
|
2644
2653
|
query?: never;
|
|
2645
|
-
header?:
|
|
2654
|
+
header?: {
|
|
2655
|
+
/**
|
|
2656
|
+
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
2657
|
+
*
|
|
2658
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
2659
|
+
*
|
|
2660
|
+
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
2661
|
+
*/
|
|
2662
|
+
'Idempotency-Key'?: string;
|
|
2663
|
+
};
|
|
2646
2664
|
path: {
|
|
2647
2665
|
/** @description The upload session id. */
|
|
2648
2666
|
id: string;
|
|
@@ -2714,6 +2732,15 @@ interface operations {
|
|
|
2714
2732
|
'application/json': components['schemas']['Error'];
|
|
2715
2733
|
};
|
|
2716
2734
|
};
|
|
2735
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2736
|
+
422: {
|
|
2737
|
+
headers: {
|
|
2738
|
+
[name: string]: unknown;
|
|
2739
|
+
};
|
|
2740
|
+
content: {
|
|
2741
|
+
'application/json': components['schemas']['Error'];
|
|
2742
|
+
};
|
|
2743
|
+
};
|
|
2717
2744
|
/** @description Too fast. RETRYABLE — `Retry-After` says when, and `X-RateLimit-*` say what the ceiling was. Distinct from 402: no upgrade is needed to make this exact call succeed. */
|
|
2718
2745
|
429: {
|
|
2719
2746
|
headers: {
|
|
@@ -3099,7 +3126,7 @@ interface operations {
|
|
|
3099
3126
|
/**
|
|
3100
3127
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3101
3128
|
*
|
|
3102
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3129
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3103
3130
|
*
|
|
3104
3131
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3105
3132
|
*/
|
|
@@ -3159,7 +3186,7 @@ interface operations {
|
|
|
3159
3186
|
'application/json': components['schemas']['Error'];
|
|
3160
3187
|
};
|
|
3161
3188
|
};
|
|
3162
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3189
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3163
3190
|
413: {
|
|
3164
3191
|
headers: {
|
|
3165
3192
|
[name: string]: unknown;
|
|
@@ -3168,7 +3195,7 @@ interface operations {
|
|
|
3168
3195
|
'application/json': components['schemas']['Error'];
|
|
3169
3196
|
};
|
|
3170
3197
|
};
|
|
3171
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3198
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3172
3199
|
422: {
|
|
3173
3200
|
headers: {
|
|
3174
3201
|
[name: string]: unknown;
|
|
@@ -3301,7 +3328,7 @@ interface operations {
|
|
|
3301
3328
|
/**
|
|
3302
3329
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3303
3330
|
*
|
|
3304
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3331
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3305
3332
|
*
|
|
3306
3333
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3307
3334
|
*/
|
|
@@ -3382,7 +3409,7 @@ interface operations {
|
|
|
3382
3409
|
'application/json': components['schemas']['Error'];
|
|
3383
3410
|
};
|
|
3384
3411
|
};
|
|
3385
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3412
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3386
3413
|
413: {
|
|
3387
3414
|
headers: {
|
|
3388
3415
|
[name: string]: unknown;
|
|
@@ -3391,7 +3418,7 @@ interface operations {
|
|
|
3391
3418
|
'application/json': components['schemas']['Error'];
|
|
3392
3419
|
};
|
|
3393
3420
|
};
|
|
3394
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3421
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3395
3422
|
422: {
|
|
3396
3423
|
headers: {
|
|
3397
3424
|
[name: string]: unknown;
|
|
@@ -3586,7 +3613,7 @@ interface operations {
|
|
|
3586
3613
|
'application/json': components['schemas']['Error'];
|
|
3587
3614
|
};
|
|
3588
3615
|
};
|
|
3589
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3616
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3590
3617
|
422: {
|
|
3591
3618
|
headers: {
|
|
3592
3619
|
[name: string]: unknown;
|
|
@@ -3650,7 +3677,7 @@ interface operations {
|
|
|
3650
3677
|
/**
|
|
3651
3678
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3652
3679
|
*
|
|
3653
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3680
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3654
3681
|
*
|
|
3655
3682
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3656
3683
|
*/
|
|
@@ -3733,7 +3760,7 @@ interface operations {
|
|
|
3733
3760
|
'application/json': components['schemas']['Error'];
|
|
3734
3761
|
};
|
|
3735
3762
|
};
|
|
3736
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3763
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3737
3764
|
422: {
|
|
3738
3765
|
headers: {
|
|
3739
3766
|
[name: string]: unknown;
|
|
@@ -3875,7 +3902,7 @@ interface operations {
|
|
|
3875
3902
|
/**
|
|
3876
3903
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3877
3904
|
*
|
|
3878
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3905
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3879
3906
|
*
|
|
3880
3907
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3881
3908
|
*/
|
|
@@ -3952,7 +3979,7 @@ interface operations {
|
|
|
3952
3979
|
'application/json': components['schemas']['Error'];
|
|
3953
3980
|
};
|
|
3954
3981
|
};
|
|
3955
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3982
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3956
3983
|
422: {
|
|
3957
3984
|
headers: {
|
|
3958
3985
|
[name: string]: unknown;
|
|
@@ -4589,7 +4616,7 @@ interface operations {
|
|
|
4589
4616
|
/**
|
|
4590
4617
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
4591
4618
|
*
|
|
4592
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4619
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4593
4620
|
*
|
|
4594
4621
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
4595
4622
|
*/
|
|
@@ -4640,7 +4667,7 @@ interface operations {
|
|
|
4640
4667
|
'application/json': components['schemas']['Error'];
|
|
4641
4668
|
};
|
|
4642
4669
|
};
|
|
4643
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4670
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4644
4671
|
422: {
|
|
4645
4672
|
headers: {
|
|
4646
4673
|
[name: string]: unknown;
|
|
@@ -4773,7 +4800,7 @@ interface operations {
|
|
|
4773
4800
|
/**
|
|
4774
4801
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
4775
4802
|
*
|
|
4776
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4803
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4777
4804
|
*
|
|
4778
4805
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
4779
4806
|
*/
|
|
@@ -4836,7 +4863,7 @@ interface operations {
|
|
|
4836
4863
|
'application/json': components['schemas']['Error'];
|
|
4837
4864
|
};
|
|
4838
4865
|
};
|
|
4839
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4866
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4840
4867
|
422: {
|
|
4841
4868
|
headers: {
|
|
4842
4869
|
[name: string]: unknown;
|
|
@@ -5068,7 +5095,7 @@ interface operations {
|
|
|
5068
5095
|
/**
|
|
5069
5096
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
5070
5097
|
*
|
|
5071
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
5098
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
5072
5099
|
*
|
|
5073
5100
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
5074
5101
|
*/
|
|
@@ -5118,7 +5145,7 @@ interface operations {
|
|
|
5118
5145
|
'application/json': components['schemas']['Error'];
|
|
5119
5146
|
};
|
|
5120
5147
|
};
|
|
5121
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
5148
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
5122
5149
|
422: {
|
|
5123
5150
|
headers: {
|
|
5124
5151
|
[name: string]: unknown;
|
|
@@ -5361,6 +5388,9 @@ declare class Media extends APIResource {
|
|
|
5361
5388
|
/**
|
|
5362
5389
|
* Upload a large video through an upload session: start it, PUT every part to its
|
|
5363
5390
|
* signed URL, then complete it. The session is aborted if any step fails.
|
|
5391
|
+
*
|
|
5392
|
+
* An `idempotencyKey` passed here is split per step (`<key>:start`, `<key>:complete`),
|
|
5393
|
+
* since the API holds a key to one route. Keep it under 246 characters so both fit.
|
|
5364
5394
|
*/
|
|
5365
5395
|
uploadMultipart(file: Uploadable, params?: MultipartUploadParams, options?: RequestOptions): Promise<MediaItem>;
|
|
5366
5396
|
/** Delete a file from the media library. */
|
|
@@ -5705,7 +5735,7 @@ export declare class WebhookVerificationError extends BulkitError {
|
|
|
5705
5735
|
}
|
|
5706
5736
|
//#endregion
|
|
5707
5737
|
//#region src/version.d.ts
|
|
5708
|
-
export declare const VERSION = "0.1.
|
|
5738
|
+
export declare const VERSION = "0.1.1";
|
|
5709
5739
|
//#endregion
|
|
5710
5740
|
export type { APIResponse, Attachment, Channel, ChannelCapabilities, ClientOptions, Comment, CommentListParams, CommentReply, CommentReplyParams, ErrorCode, Fetch, FieldError, HeadersLike, IssuedWebhookEndpoint, MediaItem, MediaUpload, MediaUploadParams, MediaUploadPart, MediaUploadStartParams, MultipartUploadParams, OptionChoices, OptionChoicesParams, Platform, PlatformLimits, Post, PostBlock, PostChannel, PostCreateBlock, PostCreateChannel, PostCreateParams, PostListParams, PostMetrics, PostReviseParams, PostStatus, PostType, RateLimitInfo, RequestOptions, RetractResult, ReviseResult, Stats, StatsInsights, StatsInsightsParams, StatsParams, Tag, Uploadable, Usage, UsageMetric, VerifyWebhookOptions, WebhookChannelData, WebhookCreateParams, WebhookDelivery, WebhookDeliveryListParams, WebhookEndpoint, WebhookEvent, WebhookEventType, WebhookPostData, WebhookTestResult, WebhookUpdateParams };
|
|
5711
5741
|
//# sourceMappingURL=index.d.cts.map
|
package/dist/index.d.ts
CHANGED
|
@@ -2071,6 +2071,15 @@ interface operations {
|
|
|
2071
2071
|
'application/json': components['schemas']['Error'];
|
|
2072
2072
|
};
|
|
2073
2073
|
};
|
|
2074
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2075
|
+
422: {
|
|
2076
|
+
headers: {
|
|
2077
|
+
[name: string]: unknown;
|
|
2078
|
+
};
|
|
2079
|
+
content: {
|
|
2080
|
+
'application/json': components['schemas']['Error'];
|
|
2081
|
+
};
|
|
2082
|
+
};
|
|
2074
2083
|
/** @description Too fast. RETRYABLE — `Retry-After` says when, and `X-RateLimit-*` say what the ceiling was. Distinct from 402: no upgrade is needed to make this exact call succeed. */
|
|
2075
2084
|
429: {
|
|
2076
2085
|
headers: {
|
|
@@ -2183,7 +2192,7 @@ interface operations {
|
|
|
2183
2192
|
'application/json': components['schemas']['Error'];
|
|
2184
2193
|
};
|
|
2185
2194
|
};
|
|
2186
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2195
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2187
2196
|
422: {
|
|
2188
2197
|
headers: {
|
|
2189
2198
|
[name: string]: unknown;
|
|
@@ -2364,7 +2373,7 @@ interface operations {
|
|
|
2364
2373
|
'application/json': components['schemas']['Error'];
|
|
2365
2374
|
};
|
|
2366
2375
|
};
|
|
2367
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2376
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2368
2377
|
413: {
|
|
2369
2378
|
headers: {
|
|
2370
2379
|
[name: string]: unknown;
|
|
@@ -2428,7 +2437,7 @@ interface operations {
|
|
|
2428
2437
|
/**
|
|
2429
2438
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
2430
2439
|
*
|
|
2431
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
2440
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
2432
2441
|
*
|
|
2433
2442
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
2434
2443
|
*/
|
|
@@ -2488,7 +2497,7 @@ interface operations {
|
|
|
2488
2497
|
'application/json': components['schemas']['Error'];
|
|
2489
2498
|
};
|
|
2490
2499
|
};
|
|
2491
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2500
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
2492
2501
|
413: {
|
|
2493
2502
|
headers: {
|
|
2494
2503
|
[name: string]: unknown;
|
|
@@ -2506,7 +2515,7 @@ interface operations {
|
|
|
2506
2515
|
'application/json': components['schemas']['Error'];
|
|
2507
2516
|
};
|
|
2508
2517
|
};
|
|
2509
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2518
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2510
2519
|
422: {
|
|
2511
2520
|
headers: {
|
|
2512
2521
|
[name: string]: unknown;
|
|
@@ -2642,7 +2651,16 @@ interface operations {
|
|
|
2642
2651
|
PublicMediaController_completeUpload: {
|
|
2643
2652
|
parameters: {
|
|
2644
2653
|
query?: never;
|
|
2645
|
-
header?:
|
|
2654
|
+
header?: {
|
|
2655
|
+
/**
|
|
2656
|
+
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
2657
|
+
*
|
|
2658
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
2659
|
+
*
|
|
2660
|
+
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
2661
|
+
*/
|
|
2662
|
+
'Idempotency-Key'?: string;
|
|
2663
|
+
};
|
|
2646
2664
|
path: {
|
|
2647
2665
|
/** @description The upload session id. */
|
|
2648
2666
|
id: string;
|
|
@@ -2714,6 +2732,15 @@ interface operations {
|
|
|
2714
2732
|
'application/json': components['schemas']['Error'];
|
|
2715
2733
|
};
|
|
2716
2734
|
};
|
|
2735
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
2736
|
+
422: {
|
|
2737
|
+
headers: {
|
|
2738
|
+
[name: string]: unknown;
|
|
2739
|
+
};
|
|
2740
|
+
content: {
|
|
2741
|
+
'application/json': components['schemas']['Error'];
|
|
2742
|
+
};
|
|
2743
|
+
};
|
|
2717
2744
|
/** @description Too fast. RETRYABLE — `Retry-After` says when, and `X-RateLimit-*` say what the ceiling was. Distinct from 402: no upgrade is needed to make this exact call succeed. */
|
|
2718
2745
|
429: {
|
|
2719
2746
|
headers: {
|
|
@@ -3099,7 +3126,7 @@ interface operations {
|
|
|
3099
3126
|
/**
|
|
3100
3127
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3101
3128
|
*
|
|
3102
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3129
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3103
3130
|
*
|
|
3104
3131
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3105
3132
|
*/
|
|
@@ -3159,7 +3186,7 @@ interface operations {
|
|
|
3159
3186
|
'application/json': components['schemas']['Error'];
|
|
3160
3187
|
};
|
|
3161
3188
|
};
|
|
3162
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3189
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3163
3190
|
413: {
|
|
3164
3191
|
headers: {
|
|
3165
3192
|
[name: string]: unknown;
|
|
@@ -3168,7 +3195,7 @@ interface operations {
|
|
|
3168
3195
|
'application/json': components['schemas']['Error'];
|
|
3169
3196
|
};
|
|
3170
3197
|
};
|
|
3171
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3198
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3172
3199
|
422: {
|
|
3173
3200
|
headers: {
|
|
3174
3201
|
[name: string]: unknown;
|
|
@@ -3301,7 +3328,7 @@ interface operations {
|
|
|
3301
3328
|
/**
|
|
3302
3329
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3303
3330
|
*
|
|
3304
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3331
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3305
3332
|
*
|
|
3306
3333
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3307
3334
|
*/
|
|
@@ -3382,7 +3409,7 @@ interface operations {
|
|
|
3382
3409
|
'application/json': components['schemas']['Error'];
|
|
3383
3410
|
};
|
|
3384
3411
|
};
|
|
3385
|
-
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3412
|
+
/** @description `payload_too_large` — an upload past the per-kind ceiling (10 MB for images, 100 MB for video and documents, 5 MB for subtitle files), or a JSON body past the one a request may carry. A larger video goes through `POST /media/uploads`, where the ceiling is the plan’s video cap instead and going over it is a 402. A limit on the resource, not on the plan: a bigger plan does not raise it. */
|
|
3386
3413
|
413: {
|
|
3387
3414
|
headers: {
|
|
3388
3415
|
[name: string]: unknown;
|
|
@@ -3391,7 +3418,7 @@ interface operations {
|
|
|
3391
3418
|
'application/json': components['schemas']['Error'];
|
|
3392
3419
|
};
|
|
3393
3420
|
};
|
|
3394
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3421
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3395
3422
|
422: {
|
|
3396
3423
|
headers: {
|
|
3397
3424
|
[name: string]: unknown;
|
|
@@ -3586,7 +3613,7 @@ interface operations {
|
|
|
3586
3613
|
'application/json': components['schemas']['Error'];
|
|
3587
3614
|
};
|
|
3588
3615
|
};
|
|
3589
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3616
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3590
3617
|
422: {
|
|
3591
3618
|
headers: {
|
|
3592
3619
|
[name: string]: unknown;
|
|
@@ -3650,7 +3677,7 @@ interface operations {
|
|
|
3650
3677
|
/**
|
|
3651
3678
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3652
3679
|
*
|
|
3653
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3680
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3654
3681
|
*
|
|
3655
3682
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3656
3683
|
*/
|
|
@@ -3733,7 +3760,7 @@ interface operations {
|
|
|
3733
3760
|
'application/json': components['schemas']['Error'];
|
|
3734
3761
|
};
|
|
3735
3762
|
};
|
|
3736
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3763
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3737
3764
|
422: {
|
|
3738
3765
|
headers: {
|
|
3739
3766
|
[name: string]: unknown;
|
|
@@ -3875,7 +3902,7 @@ interface operations {
|
|
|
3875
3902
|
/**
|
|
3876
3903
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
3877
3904
|
*
|
|
3878
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3905
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
3879
3906
|
*
|
|
3880
3907
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
3881
3908
|
*/
|
|
@@ -3952,7 +3979,7 @@ interface operations {
|
|
|
3952
3979
|
'application/json': components['schemas']['Error'];
|
|
3953
3980
|
};
|
|
3954
3981
|
};
|
|
3955
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3982
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
3956
3983
|
422: {
|
|
3957
3984
|
headers: {
|
|
3958
3985
|
[name: string]: unknown;
|
|
@@ -4589,7 +4616,7 @@ interface operations {
|
|
|
4589
4616
|
/**
|
|
4590
4617
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
4591
4618
|
*
|
|
4592
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4619
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4593
4620
|
*
|
|
4594
4621
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
4595
4622
|
*/
|
|
@@ -4640,7 +4667,7 @@ interface operations {
|
|
|
4640
4667
|
'application/json': components['schemas']['Error'];
|
|
4641
4668
|
};
|
|
4642
4669
|
};
|
|
4643
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4670
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4644
4671
|
422: {
|
|
4645
4672
|
headers: {
|
|
4646
4673
|
[name: string]: unknown;
|
|
@@ -4773,7 +4800,7 @@ interface operations {
|
|
|
4773
4800
|
/**
|
|
4774
4801
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
4775
4802
|
*
|
|
4776
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4803
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
4777
4804
|
*
|
|
4778
4805
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
4779
4806
|
*/
|
|
@@ -4836,7 +4863,7 @@ interface operations {
|
|
|
4836
4863
|
'application/json': components['schemas']['Error'];
|
|
4837
4864
|
};
|
|
4838
4865
|
};
|
|
4839
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4866
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
4840
4867
|
422: {
|
|
4841
4868
|
headers: {
|
|
4842
4869
|
[name: string]: unknown;
|
|
@@ -5068,7 +5095,7 @@ interface operations {
|
|
|
5068
5095
|
/**
|
|
5069
5096
|
* @description Send one on every write. A retry carrying the same key returns the FIRST response instead of doing the work twice — without it, a client that times out and retries schedules the post a second time, and the first is already queued.
|
|
5070
5097
|
*
|
|
5071
|
-
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key with a different body is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
5098
|
+
* Any string up to 255 characters; a UUID per logical operation is the usual choice. Keys are scoped to your workspace and honoured for 24 hours. The same key on a different route or id, or with a different body, is a `422`; a request still running under this key is a `409 request_in_progress`.
|
|
5072
5099
|
*
|
|
5073
5100
|
* What a FAILED request does to its key depends on whether it could have changed anything. A `4xx` releases it — every one of them is raised before we write a thing, so fix the input and retry with the same key. A `5xx` pins it, and the retry replays that failure instead of doing the work: a write is several posts and several workflows, so a fault partway through leaves some of them done, and a fresh attempt would publish those a second time. Read `GET /posts/{id}` to see what exists, then continue with a new key.
|
|
5074
5101
|
*/
|
|
@@ -5118,7 +5145,7 @@ interface operations {
|
|
|
5118
5145
|
'application/json': components['schemas']['Error'];
|
|
5119
5146
|
};
|
|
5120
5147
|
};
|
|
5121
|
-
/** @description This `Idempotency-Key` was already used with a different request body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
5148
|
+
/** @description This `Idempotency-Key` was already used with a different request: another route, another id or another body (`error.field` is `Idempotency-Key`). Replaying the stored response would silently discard what you just asked for, so it is refused instead. `platform_refused`: the platform understood the call and said no, in the words of the message (comments turned off on the post, a locked thread, an app access level that can’t search). The same call will be refused again. */
|
|
5122
5149
|
422: {
|
|
5123
5150
|
headers: {
|
|
5124
5151
|
[name: string]: unknown;
|
|
@@ -5361,6 +5388,9 @@ declare class Media extends APIResource {
|
|
|
5361
5388
|
/**
|
|
5362
5389
|
* Upload a large video through an upload session: start it, PUT every part to its
|
|
5363
5390
|
* signed URL, then complete it. The session is aborted if any step fails.
|
|
5391
|
+
*
|
|
5392
|
+
* An `idempotencyKey` passed here is split per step (`<key>:start`, `<key>:complete`),
|
|
5393
|
+
* since the API holds a key to one route. Keep it under 246 characters so both fit.
|
|
5364
5394
|
*/
|
|
5365
5395
|
uploadMultipart(file: Uploadable, params?: MultipartUploadParams, options?: RequestOptions): Promise<MediaItem>;
|
|
5366
5396
|
/** Delete a file from the media library. */
|
|
@@ -5705,7 +5735,7 @@ export declare class WebhookVerificationError extends BulkitError {
|
|
|
5705
5735
|
}
|
|
5706
5736
|
//#endregion
|
|
5707
5737
|
//#region src/version.d.ts
|
|
5708
|
-
export declare const VERSION = "0.1.
|
|
5738
|
+
export declare const VERSION = "0.1.1";
|
|
5709
5739
|
//#endregion
|
|
5710
5740
|
export type { APIResponse, Attachment, Channel, ChannelCapabilities, ClientOptions, Comment, CommentListParams, CommentReply, CommentReplyParams, ErrorCode, Fetch, FieldError, HeadersLike, IssuedWebhookEndpoint, MediaItem, MediaUpload, MediaUploadParams, MediaUploadPart, MediaUploadStartParams, MultipartUploadParams, OptionChoices, OptionChoicesParams, Platform, PlatformLimits, Post, PostBlock, PostChannel, PostCreateBlock, PostCreateChannel, PostCreateParams, PostListParams, PostMetrics, PostReviseParams, PostStatus, PostType, RateLimitInfo, RequestOptions, RetractResult, ReviseResult, Stats, StatsInsights, StatsInsightsParams, StatsParams, Tag, Uploadable, Usage, UsageMetric, VerifyWebhookOptions, WebhookChannelData, WebhookCreateParams, WebhookDelivery, WebhookDeliveryListParams, WebhookEndpoint, WebhookEvent, WebhookEventType, WebhookPostData, WebhookTestResult, WebhookUpdateParams };
|
|
5711
5741
|
//# sourceMappingURL=index.d.ts.map
|