1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
//! Per-request authentication and header options.
//!
//! Every request method takes a [`RequestOptions`] value, which decides how
//! the request authenticates and which extra headers are attached. The
//! default is no authentication; [`RequestOptions::bearer`] reproduces the
//! classic `Authorization: Bearer <token>` behavior of OpenAI and most
//! compatible providers.
//!
//! # Examples
//!
//! Plain OpenAI-style bearer auth:
//!
//! ```
//! use openai_interface::rest::RequestOptions;
//!
//! let options = RequestOptions::bearer("sk-...");
//! # assert!(matches!(options.auth, openai_interface::rest::Auth::Bearer(_)));
//! ```
//!
//! Azure OpenAI authenticates with an `api-key` header instead:
//!
//! ```
//! use openai_interface::rest::RequestOptions;
//!
//! let options = RequestOptions::new()
//! .with_header("api-key", "...")
//! .unwrap();
//! ```
//!
//! Anthropic uses `x-api-key` plus a version header:
//!
//! ```
//! use openai_interface::rest::RequestOptions;
//!
//! let options = RequestOptions::new()
//! .with_header("x-api-key", "...")
//! .unwrap()
//! .with_header("anthropic-version", "2023-06-01")
//! .unwrap();
//! ```
//!
//! Extra headers may also be layered on top of bearer auth, e.g. the
//! `OpenAI-Organization` header:
//!
//! ```
//! use openai_interface::rest::RequestOptions;
//!
//! let options = RequestOptions::bearer("sk-...")
//! .with_header("OpenAI-Organization", "org-...")
//! .unwrap();
//! ```
use ;
use crateOapiError;
/// How a request authenticates itself.
/// Per-request authentication and header options.
///
/// Passed to every request method instead of a bare API key. Authentication
/// headers ([`Auth`]) are applied first; [`RequestOptions::extra_headers`]
/// are applied afterwards, so they can supply additional credentials of
/// their own.