Files
zeekay 189ce08e51 Regenerate against the document the deployment answers for
The projection these were generated from was a month old and predated the
compute migration, so every one of them described /v1/visor — which the API
serves at zero paths now. That is why a hand-written console client and a
generated one had drifted the same way at the same time.

No /v1/visor path survives here. The word still appears as a source-plane
value and inside gvisor and supervisor, which are not this rename.
2026-09-05 18:07:13 -07:00

152 lines
4.5 KiB
C++

/**
* Hanzo Cloud API
* The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
*
* The version of the OpenAPI document: v1
*
* NOTE: This class is auto generated by OpenAPI-Generator 7.14.0.
* https://openapi-generator.tech
* Do not edit the class manually.
*/
/*
* Subject.h
*
*
*/
#ifndef HANZO_MODEL_Subject_H_
#define HANZO_MODEL_Subject_H_
#include <boost/optional.hpp>
#include "hanzo/ModelBase.h"
#include <cpprest/details/basic_types.h>
namespace hanzo {
namespace model {
class Subject
: public ModelBase
{
public:
Subject();
virtual ~Subject();
/////////////////////////////////////////////
/// ModelBase overrides
void validate() override;
web::json::value toJson() const override;
bool fromJson(const web::json::value& json) override;
void toMultipart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) const override;
bool fromMultiPart(std::shared_ptr<MultipartFormData> multipart, const utility::string_t& namePrefix) override;
/////////////////////////////////////////////
/// Subject members
/// <summary>
/// CreatedAt is when the subject was first recorded, Unix SECONDS.
/// </summary>
int64_t getCreatedAt() const;
bool createdAtIsSet() const;
void unsetCreatedAt();
void setCreatedAt(int64_t value);
/// <summary>
/// Email is the party&#39;s address, when the org supplied one. It is PII: sealed at rest, returned only to the owning org, and never copied into a check record.
/// </summary>
utility::string_t getEmail() const;
bool emailIsSet() const;
void unsetEmail();
void setEmail(const utility::string_t& value);
/// <summary>
/// ID is the opaque handle every other record uses to point at this party. It is the only reference that leaves this type, which is what keeps the PII in one place: a check, an accreditation and an audit row all carry the id and none of them carry the name.
/// </summary>
utility::string_t getId() const;
bool idIsSet() const;
void unsetId();
void setId(const utility::string_t& value);
/// <summary>
/// Kind is what is being verified: \&quot;individual\&quot; (a natural person, so KYC) or \&quot;business\&quot; (a legal entity, so KYB). It decides which provider flow runs.
/// </summary>
utility::string_t getKind() const;
bool kindIsSet() const;
void unsetKind();
void setKind(const utility::string_t& value);
/// <summary>
/// Name is the party&#39;s name, under the same PII rule as Email. For a business it is the legal entity name rather than a trading name, since that is what a provider verifies against.
/// </summary>
utility::string_t getName() const;
bool nameIsSet() const;
void unsetName();
void setName(const utility::string_t& value);
/// <summary>
/// Org is the tenant that is doing the verifying — the party who must answer for this record, not the party being verified. A subject is returned only to it.
/// </summary>
utility::string_t getOrg() const;
bool orgIsSet() const;
void unsetOrg();
void setOrg(const utility::string_t& value);
/// <summary>
/// Ref is the org&#39;s OWN identifier for this party, carried so a caller can match a subject back to their system without keeping a second mapping. Opaque here: nothing in this plane parses or enforces it.
/// </summary>
utility::string_t getRef() const;
bool refIsSet() const;
void unsetRef();
void setRef(const utility::string_t& value);
/// <summary>
/// UpdatedAt is when the subject&#39;s own fields last changed, Unix seconds. A check moving to a new status does not touch it — that history lives on the check.
/// </summary>
int64_t getUpdatedAt() const;
bool updatedAtIsSet() const;
void unsetUpdatedAt();
void setUpdatedAt(int64_t value);
protected:
int64_t m_CreatedAt;
bool m_CreatedAtIsSet;
utility::string_t m_Email;
bool m_EmailIsSet;
utility::string_t m_Id;
bool m_IdIsSet;
utility::string_t m_Kind;
bool m_KindIsSet;
utility::string_t m_Name;
bool m_NameIsSet;
utility::string_t m_Org;
bool m_OrgIsSet;
utility::string_t m_Ref;
bool m_RefIsSet;
int64_t m_UpdatedAt;
bool m_UpdatedAtIsSet;
};
}
}
#endif /* HANZO_MODEL_Subject_H_ */