/
model_inbox_preview.go
39 lines (38 loc) · 3.54 KB
/
model_inbox_preview.go
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
/*
* MailSlurp API
*
* MailSlurp is an API for sending and receiving emails from dynamically allocated email addresses. It's designed for developers and QA teams to test applications, process inbound emails, send templated notifications, attachments, and more. ## Resources - [Homepage](https://www.mailslurp.com) - Get an [API KEY](https://app.mailslurp.com/sign-up/) - Generated [SDK Clients](https://docs.mailslurp.com/) - [Examples](https://github.com/mailslurp/examples) repository
*
* API version: 6.5.2
* Contact: contact@mailslurp.dev
* Generated by: OpenAPI Generator (https://openapi-generator.tech)
*/
package MailSlurpClient
import (
"time"
)
// InboxPreview Inbox data preview element.
type InboxPreview struct {
// ID of the inbox. The ID is a UUID-V4 format string. Use the inboxId for calls to Inbox and Email Controller endpoints. See the emailAddress property for the email address or the inbox. To get emails in an inbox use the WaitFor and Inbox Controller methods `waitForLatestEmail` and `getEmails` methods respectively. Inboxes can be used with aliases to forward emails automatically.
Id string `json:"id"`
// ID of custom domain used by the inbox if any
DomainId *string `json:"domainId,omitempty"`
// The inbox's email address. Inbox projections and previews may not include the email address. To view the email address fetch the inbox entity directly. Send an email to this address and the inbox will receive and store it for you. Note the email address in MailSlurp match characters exactly and are case sensitive so `+123` additions are considered different addresses. To retrieve the email use the Inbox and Email Controller endpoints with the inbox ID.
EmailAddress *string `json:"emailAddress,omitempty"`
// When the inbox was created. Time stamps are in ISO DateTime Format `yyyy-MM-dd'T'HH:mm:ss.SSSXXX` e.g. `2000-10-31T01:30:00.000-05:00`.
CreatedAt time.Time `json:"createdAt"`
// Is the inbox a favorite inbox. Make an inbox a favorite is typically done in the dashboard for quick access or filtering
Favourite bool `json:"favourite"`
// Name of the inbox and used as the sender name when sending emails .Displayed in the dashboard for easier search
Name *string `json:"name,omitempty"`
// Tags that inbox has been tagged with. Tags can be added to inboxes to group different inboxes within an account. You can also search for inboxes by tag in the dashboard UI.
Tags *[]string `json:"tags,omitempty"`
// Does inbox permit team access for organization team members. If so team users can use inbox and emails associated with it. See the team access guide at https://www.mailslurp.com/guides/team-email-account-sharing/
TeamAccess bool `json:"teamAccess"`
// Type of inbox. HTTP inboxes are faster and better for most cases. SMTP inboxes are more suited for public facing inbound messages (but cannot send).
InboxType *string `json:"inboxType,omitempty"`
// Virtual inbox can receive email but will not send emails to real recipients. Will save sent email record but never send an actual email. Perfect for testing mail server actions.
VirtualInbox bool `json:"virtualInbox"`
// Inbox expiration time. When, if ever, the inbox should expire and be deleted. If null then this inbox is permanent and the emails in it won't be deleted. This is the default behavior unless expiration date is set. If an expiration date is set and the time is reached MailSlurp will expire the inbox and move it to an expired inbox entity. You can still access the emails belonging to it but it can no longer send or receive email.
ExpiresAt *string `json:"expiresAt,omitempty"`
}