Updated python API Client

Author: detain

.openapi-generator/FILES

@@ -32,6 +32,7 @@ docs/SendMailTo.md
 docs/SendingApi.md
 docs/ServicesApi.md
 docs/StatusApi.md
+docs/ViewMailLogStartDateParameter.md
 git_push.sh
 openapi_client/__init__.py
 openapi_client/api/__init__.py
@@ -68,6 +69,7 @@ openapi_client/models/send_mail.py
 openapi_client/models/send_mail_adv.py
 openapi_client/models/send_mail_raw.py
 openapi_client/models/send_mail_to.py
+openapi_client/models/view_mail_log_start_date_parameter.py
 openapi_client/py.typed
 openapi_client/rest.py
 pyproject.toml
@@ -104,4 +106,5 @@ test/test_send_mail_to.py
 test/test_sending_api.py
 test/test_services_api.py
 test/test_status_api.py
+test/test_view_mail_log_start_date_parameter.py
 tox.ini

README.md

@@ -18,7 +18,7 @@ After a successful send each endpoint returns a `GenericResponse` whose `text` f
 
 # Filtering & Logs
 
-`GET /mail/log` provides paginated access to every message accepted by the relay for your account.  Combine any of the query parameters to narrow results — e.g. `from`, `to`, `subject`, `messageId`, `origin`, `mx`, `startDate`/`endDate`, and `delivered`.
+`GET /mail/log` provides paginated access to every message accepted by the relay for your account. Combine any of the query parameters to narrow results — e.g. `from`, `to`, `subject`, `messageId`, `origin`, `mx`, `startDate`/`endDate`, and `delivered`.
 
 # Blocking
 
@@ -114,7 +114,7 @@ configuration.api_key['apiKeyAuth'] = os.environ["API_KEY"]
 with openapi_client.ApiClient(configuration) as api_client:
     # Create an instance of the API class
     api_instance = openapi_client.BlockingApi(api_client)
-    type = 'type_example' # str | The type of deny rule.
+    type = 'type_example' # str | The matching strategy for this rule.  `email` blocks an exact sender address, `domain` blocks all senders at a domain, `destination` blocks an exact recipient address, and `startswith` blocks any sender whose local-part begins with the given prefix.
     data = 'data_example' # str | The value to match against, interpreted according to `type`: a full email address for `email`/`destination`, a domain name for `domain`, or an alphanumeric prefix string for `startswith`.
     user = 'user_example' # str | Optional SMTP username of the mail order to associate this rule with (e.g. `mb20682`).  If omitted the first active order is used.  Valid usernames are the `username` values returned by `GET /mail`. (optional)
 
@@ -174,6 +174,7 @@ Class | Method | HTTP request | Description
  - [SendMailAdv](docs/SendMailAdv.md)
  - [SendMailRaw](docs/SendMailRaw.md)
  - [SendMailTo](docs/SendMailTo.md)
+ - [ViewMailLogStartDateParameter](docs/ViewMailLogStartDateParameter.md)
 
 
 <a id="documentation-for-authorization"></a>

docs/BlockingApi.md

@@ -60,7 +60,7 @@ configuration.api_key['apiKeyAuth'] = os.environ["API_KEY"]
 with openapi_client.ApiClient(configuration) as api_client:
     # Create an instance of the API class
     api_instance = openapi_client.BlockingApi(api_client)
-    type = 'type_example' # str | The type of deny rule.
+    type = 'type_example' # str | The matching strategy for this rule.  `email` blocks an exact sender address, `domain` blocks all senders at a domain, `destination` blocks an exact recipient address, and `startswith` blocks any sender whose local-part begins with the given prefix.
     data = 'data_example' # str | The value to match against, interpreted according to `type`: a full email address for `email`/`destination`, a domain name for `domain`, or an alphanumeric prefix string for `startswith`.
     user = 'user_example' # str | Optional SMTP username of the mail order to associate this rule with (e.g. `mb20682`).  If omitted the first active order is used.  Valid usernames are the `username` values returned by `GET /mail`. (optional)
 
@@ -80,7 +80,7 @@ with openapi_client.ApiClient(configuration) as api_client:
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **type** | **str**| The type of deny rule. | 
+ **type** | **str**| The matching strategy for this rule.  `email` blocks an exact sender address, `domain` blocks all senders at a domain, `destination` blocks an exact recipient address, and `startswith` blocks any sender whose local-part begins with the given prefix. | 
  **data** | **str**| The value to match against, interpreted according to `type`: a full email address for `email`/`destination`, a domain name for `domain`, or an alphanumeric prefix string for `startswith`. | 
  **user** | **str**| Optional SMTP username of the mail order to associate this rule with (e.g. `mb20682`).  If omitted the first active order is used.  Valid usernames are the `username` values returned by `GET /mail`. | [optional] 
 
@@ -270,7 +270,7 @@ Name | Type | Description  | Notes
 
 ### HTTP request headers
 
- - **Content-Type**: application/json, multipart/form-data
+ - **Content-Type**: application/json, application/x-www-form-urlencoded
  - **Accept**: application/json
 
 ### HTTP response details

docs/DenyRuleNew.md

@@ -7,7 +7,7 @@ The fields required to create a new email deny rule via `POST /mail/rules`. The
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **user** | **str** | Optional SMTP username of the mail order to associate this rule with (e.g. `mb20682`).  If omitted the first active order is used.  Valid usernames are the `username` values returned by `GET /mail`. | [optional] 
-**type** | **str** | The type of deny rule. | 
+**type** | **str** | The matching strategy for this rule.  `email` blocks an exact sender address, `domain` blocks all senders at a domain, `destination` blocks an exact recipient address, and `startswith` blocks any sender whose local-part begins with the given prefix. | 
 **data** | **str** | The value to match against, interpreted according to `type`: a full email address for `email`/`destination`, a domain name for `domain`, or an alphanumeric prefix string for `startswith`. | 
 
 ## Example

docs/DenyRuleRecord.md

@@ -7,7 +7,7 @@ A complete deny rule record as returned by `GET /mail/rules`.  Combines the rule
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **user** | **str** | Optional SMTP username of the mail order to associate this rule with (e.g. `mb20682`).  If omitted the first active order is used.  Valid usernames are the `username` values returned by `GET /mail`. | [optional] 
-**type** | **str** | The type of deny rule. | 
+**type** | **str** | The matching strategy for this rule.  `email` blocks an exact sender address, `domain` blocks all senders at a domain, `destination` blocks an exact recipient address, and `startswith` blocks any sender whose local-part begins with the given prefix. | 
 **data** | **str** | The value to match against, interpreted according to `type`: a full email address for `email`/`destination`, a domain name for `domain`, or an alphanumeric prefix string for `startswith`. | 
 **id** | **str** | The numeric ID of the deny rule, as a string.  Pass this as `ruleId` to `DELETE /mail/rules/{ruleId}` to remove the rule. | 
 **created** | **datetime** | The timestamp when the rule was created. | 

docs/GenericResponse.md

@@ -6,8 +6,8 @@ Standard success response returned by write operations (send, add rule, delete,
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**status** | **str** | Always `\"ok\"` on success. | [optional] 
-**text** | **str** | Operation-specific result string.  For send operations this is the relay transaction ID (e.g. `185caa69ff7000f47c`) which can be used as the `mailid` parameter in `GET /mail/log`.  For create operations this is the new record's numeric ID.  For delete operations this is a human-readable confirmation. | [optional] 
+**status** | **str** | Always `\"ok\"` on success. | 
+**text** | **str** | Operation-specific result string.  For send operations this is the relay transaction ID (e.g. `185caa69ff7000f47c`) which can be used as the `mailid` parameter in `GET /mail/log`.  For create operations this is the new record's numeric ID.  For delete operations this is a human-readable confirmation. | 
 
 ## Example