responses¶
EntryInfoResponse
¶
Bases: Success
Source code in optimade/models/responses.py
61 62 63 64 65 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
EntryResponseMany
¶
Bases: Success
Source code in optimade/models/responses.py
92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
EntryResponseOne
¶
Bases: Success
Source code in optimade/models/responses.py
74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | |
data = None
class-attribute
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
ErrorResponse
¶
Bases: Response
errors MUST be present and data MUST be skipped
Source code in optimade/models/responses.py
33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 | |
data = None
class-attribute
instance-attribute
¶
errors
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
data_must_be_skipped()
¶
Source code in optimade/models/responses.py
48 49 50 51 52 | |
either_data_meta_or_errors_must_be_set()
¶
Source code in optimade/models/jsonapi.py
403 404 405 406 407 408 409 410 411 412 | |
FileResponseMany
¶
Bases: EntryResponseMany
Source code in optimade/models/responses.py
153 154 155 156 157 158 159 160 161 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
FileResponseOne
¶
Bases: EntryResponseOne
Source code in optimade/models/responses.py
143 144 145 146 147 148 149 150 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
IndexInfoResponse
¶
Bases: Success
Source code in optimade/models/responses.py
55 56 57 58 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
InfoResponse
¶
Bases: Success
Source code in optimade/models/responses.py
68 69 70 71 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
LinksResponse
¶
Bases: EntryResponseMany
Source code in optimade/models/responses.py
111 112 113 114 115 116 117 118 119 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
ReferenceResponseMany
¶
Bases: EntryResponseMany
Source code in optimade/models/responses.py
174 175 176 177 178 179 180 181 182 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
ReferenceResponseOne
¶
Bases: EntryResponseOne
Source code in optimade/models/responses.py
164 165 166 167 168 169 170 171 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
StructureResponseMany
¶
Bases: EntryResponseMany
Source code in optimade/models/responses.py
132 133 134 135 136 137 138 139 140 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |
StructureResponseOne
¶
Bases: EntryResponseOne
Source code in optimade/models/responses.py
122 123 124 125 126 127 128 129 | |
data
instance-attribute
¶
errors = None
class-attribute
instance-attribute
¶
included = None
class-attribute
instance-attribute
¶
jsonapi = None
class-attribute
instance-attribute
¶
links = None
class-attribute
instance-attribute
¶
meta
instance-attribute
¶
model_config = ConfigDict(json_encoders={datetime: lambda v: v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
405 406 407 408 409 410 411 412 413 414 415 416 417 418 | |