@remit/api-openapi-types 0.0.59 → 0.0.61

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/types.d.ts +38 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remit/api-openapi-types",
3
- "version": "0.0.59",
3
+ "version": "0.0.61",
4
4
  "type": "module",
5
5
  "main": "types.d.ts",
6
6
  "types": "types.d.ts",
package/types.d.ts CHANGED
@@ -239,7 +239,7 @@ distinguishable from a network failure without parsing prose.
239
239
  /**
240
240
  * Names a key of `AddressFlags` that a client may address in `PATCH /addresses/{addressId}`. `wellknown` is deliberately absent: it is server-owned, derived from engagement counters, and is never written or removed by a client.
241
241
  */
242
- export type AddressFlagKey = "trusted" | "blocked" | "muted" | "vip" | "junkOnly" | "category" | "autoArchive" | "unsubscribed";
242
+ export type AddressFlagKey = "trusted" | "blocked" | "muted" | "vip" | "junkOnly" | "category" | "autoArchive" | "unsubscribed" | "neverSpam";
243
243
  /**
244
244
  * Whether the header classifier has examined a message's body (issue #331). Persistence-level state on `Message`, deliberately off the wire: no response model carries it. It exists because `category` cannot answer this question — `uncategorized` is both the value a metadata-synced row starts at and the answer the classifier gives when it has nothing to say, so a guard reading `category` alone cannot tell "never examined" from "examined and declined" and re-reads the stored body on every sync pass forever.
245
245
  */
@@ -316,6 +316,10 @@ distinguishable from a network failure without parsing prose.
316
316
  * Content encoding/compression types for stored content
317
317
  */
318
318
  export type ContentEncoding = "none" | "gzip" | "zstd";
319
+ /**
320
+ * What the user has instructed about a sender's placement, resolved from AddressFlags at read time. An instruction, not a heuristic signal: it outranks every DKIM/DMARC/provider verdict. `SenderTrust` stays a separate axis and is unaffected.
321
+ */
322
+ export type SenderOverride = "none" | "blocked" | "neverSpam";
319
323
  /**
320
324
  * Known user-setting keys. Each maps, in the registry, to a required value kind and a zod schema. New keys are added deliberately by extending this enum and the registry — never as an ad-hoc column.
321
325
  */
@@ -4274,6 +4278,7 @@ either way and cannot tell which it received.
4274
4278
  export interface AddressFlags {
4275
4279
  trusted?: TrustedFlag;
4276
4280
  blocked?: BlockedFlag;
4281
+ neverSpam?: NeverSpamFlag;
4277
4282
  muted?: MutedFlag;
4278
4283
  vip?: VipFlag;
4279
4284
  wellknown?: WellknownFlag;
@@ -4326,6 +4331,28 @@ either way and cannot tell which it received.
4326
4331
  reason?: string;
4327
4332
  value: boolean;
4328
4333
  }
4334
+ /**
4335
+ * Sender is never spam: their mail is rescued from Junk whatever the authentication signals say. Mutually exclusive with `blocked` — the flag written last removes the other.
4336
+ */
4337
+ export interface NeverSpamFlag {
4338
+ /**
4339
+ * Timestamp when the flag was set
4340
+ */
4341
+ setAt: number;
4342
+ /**
4343
+ * Device/session/user identifier that set the flag (audit trail)
4344
+ */
4345
+ setBy?: string;
4346
+ /**
4347
+ * Optional auto-revoke timestamp
4348
+ */
4349
+ expiresAt?: number;
4350
+ /**
4351
+ * Free-text user note
4352
+ */
4353
+ reason?: string;
4354
+ value: boolean;
4355
+ }
4329
4356
  /**
4330
4357
  * Sender is VIP: priority surface and push escalation
4331
4358
  */
@@ -4532,6 +4559,10 @@ either way and cannot tell which it received.
4532
4559
  export interface UpdateAddressFlagsInput {
4533
4560
  trusted?: TrustedFlag | any;
4534
4561
  blocked?: BlockedFlag | any;
4562
+ /**
4563
+ * Setting this to `value: true` removes `blocked`, and setting `blocked` removes this one; the two cannot both stand
4564
+ */
4565
+ neverSpam?: NeverSpamFlag | any;
4535
4566
  muted?: MutedFlag | any;
4536
4567
  vip?: VipFlag | any;
4537
4568
  wellknown?: WellknownFlag | any;
@@ -6354,6 +6385,8 @@ declare namespace Paths {
6354
6385
  export type RequestBody = Components.Schemas.RenameMailboxInput;
6355
6386
  namespace Responses {
6356
6387
  export type $200 = void;
6388
+ export type $400 = void;
6389
+ export type $409 = void;
6357
6390
  export type $404 = void;
6358
6391
  export type $403 = void;
6359
6392
  export type $401 = void;
@@ -7279,7 +7312,7 @@ export interface OperationMethods {
7279
7312
  config?: AxiosRequestConfig
7280
7313
  ): OperationResponse<Paths.GetMailbox.Responses.$200>;
7281
7314
  /**
7282
- * renameMailbox
7315
+ * renameMailbox - Rename a folder, or dismiss a folder mutation that failed. `fullPath` records the rename target over the folder and everything under it; the folder keeps the path the mail server holds until the rename lands. A `fullPath` equal to the folder's current one is a dismissal: it clears a failed rename or delete and enqueues nothing. Refused with 400 for INBOX at either end, a name reserved for a system folder, and a name another folder already has; with 409 when a mutation is already in flight on the folder or on anything inside it.
7283
7316
  */
7284
7317
  'renameMailbox'(
7285
7318
  parameters?: Parameters<Paths.RenameMailbox.PathParameters> | null,
@@ -8065,7 +8098,7 @@ export interface PathsDictionary {
8065
8098
  config?: AxiosRequestConfig
8066
8099
  ): OperationResponse<Paths.GetMailbox.Responses.$200>;
8067
8100
  /**
8068
- * renameMailbox
8101
+ * renameMailbox - Rename a folder, or dismiss a folder mutation that failed. `fullPath` records the rename target over the folder and everything under it; the folder keeps the path the mail server holds until the rename lands. A `fullPath` equal to the folder's current one is a dismissal: it clears a failed rename or delete and enqueues nothing. Refused with 400 for INBOX at either end, a name reserved for a system folder, and a name another folder already has; with 409 when a mutation is already in flight on the folder or on anything inside it.
8069
8102
  */
8070
8103
  'patch'(
8071
8104
  parameters?: Parameters<Paths.RenameMailbox.PathParameters> | null,
@@ -8944,6 +8977,7 @@ export type Address = Components.Schemas.Address;
8944
8977
  export type AddressFlags = Components.Schemas.AddressFlags;
8945
8978
  export type TrustedFlag = Components.Schemas.TrustedFlag;
8946
8979
  export type BlockedFlag = Components.Schemas.BlockedFlag;
8980
+ export type NeverSpamFlag = Components.Schemas.NeverSpamFlag;
8947
8981
  export type VipFlag = Components.Schemas.VipFlag;
8948
8982
  export type WellknownFlag = Components.Schemas.WellknownFlag;
8949
8983
  export type JunkOnlyFlag = Components.Schemas.JunkOnlyFlag;
@@ -9076,6 +9110,7 @@ export type MessageKeywordFlag = Components.Schemas.MessageKeywordFlag;
9076
9110
  export type MailboxAttribute = Components.Schemas.MailboxAttribute;
9077
9111
  export type StorageType = Components.Schemas.StorageType;
9078
9112
  export type ContentEncoding = Components.Schemas.ContentEncoding;
9113
+ export type SenderOverride = Components.Schemas.SenderOverride;
9079
9114
  export type AccountSettingName = Components.Schemas.AccountSettingName;
9080
9115
  export type ConfigImportState = Components.Schemas.ConfigImportState;
9081
9116
  export type ConfigImportRefKind = Components.Schemas.ConfigImportRefKind;