@pidgeon-ai/sdk 1.50.0 → 1.51.0

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/dist/index.d.cts CHANGED
@@ -5717,7 +5717,12 @@ type MessagesRawData = {
5717
5717
  path: {
5718
5718
  id: string;
5719
5719
  };
5720
- query?: never;
5720
+ query?: {
5721
+ /**
5722
+ * original: only the header section of the message as it arrived, with no body, so its DKIM signatures (the agent declaration’s among them) can be checked, as /verify does. 404 when the original is no longer kept.
5723
+ */
5724
+ headers?: 'original';
5725
+ };
5721
5726
  url: '/messages/{id}/raw';
5722
5727
  };
5723
5728
  type MessagesRawErrors = {
@@ -10740,7 +10745,7 @@ declare const messagesForward: <ThrowOnError extends boolean = false>(options: O
10740
10745
  /**
10741
10746
  * The message as MIME
10742
10747
  *
10743
- * `message/rfc822`, not JSON. An API key gets the message rebuilt from the stored message, with a canary token in its text (/docs/firewall): the original bytes cannot carry one, so `X-Pidgeon-Reconstructed` is `true` and a rebuild cannot verify DKIM. The message’s `authentication` is our check of the original’s signatures.
10748
+ * `message/rfc822`, not JSON. An API key gets the message rebuilt from the stored message, with a canary token in its text (/docs/firewall): the original bytes cannot carry one, so `X-Pidgeon-Reconstructed` is `true` and a rebuild cannot verify DKIM. The message’s `authentication` is our check of the original’s signatures. `headers=original` returns only the original’s header section, for any caller: the signed agent declaration, checkable as /verify checks it, with no body to stamp.
10744
10749
  */
10745
10750
  declare const messagesRaw: <ThrowOnError extends boolean = false>(options: Options<MessagesRawData, ThrowOnError>) => RequestResult<MessagesRawResponses, MessagesRawErrors, ThrowOnError>;
10746
10751
  /**
package/dist/index.d.ts CHANGED
@@ -5717,7 +5717,12 @@ type MessagesRawData = {
5717
5717
  path: {
5718
5718
  id: string;
5719
5719
  };
5720
- query?: never;
5720
+ query?: {
5721
+ /**
5722
+ * original: only the header section of the message as it arrived, with no body, so its DKIM signatures (the agent declaration’s among them) can be checked, as /verify does. 404 when the original is no longer kept.
5723
+ */
5724
+ headers?: 'original';
5725
+ };
5721
5726
  url: '/messages/{id}/raw';
5722
5727
  };
5723
5728
  type MessagesRawErrors = {
@@ -10740,7 +10745,7 @@ declare const messagesForward: <ThrowOnError extends boolean = false>(options: O
10740
10745
  /**
10741
10746
  * The message as MIME
10742
10747
  *
10743
- * `message/rfc822`, not JSON. An API key gets the message rebuilt from the stored message, with a canary token in its text (/docs/firewall): the original bytes cannot carry one, so `X-Pidgeon-Reconstructed` is `true` and a rebuild cannot verify DKIM. The message’s `authentication` is our check of the original’s signatures.
10748
+ * `message/rfc822`, not JSON. An API key gets the message rebuilt from the stored message, with a canary token in its text (/docs/firewall): the original bytes cannot carry one, so `X-Pidgeon-Reconstructed` is `true` and a rebuild cannot verify DKIM. The message’s `authentication` is our check of the original’s signatures. `headers=original` returns only the original’s header section, for any caller: the signed agent declaration, checkable as /verify checks it, with no body to stamp.
10744
10749
  */
10745
10750
  declare const messagesRaw: <ThrowOnError extends boolean = false>(options: Options<MessagesRawData, ThrowOnError>) => RequestResult<MessagesRawResponses, MessagesRawErrors, ThrowOnError>;
10746
10751
  /**