client.go

// Code generated by `generate`. DO NOT EDIT.

package kittycad

import "net/http"

// Client which conforms to the OpenAPI v3 specification for this service.
type Client struct {
	// The endpoint of the server conforming to this interface, with scheme,
	// https://api.example.com for example.
	server string

	// Client is the *http.Client for performing requests.
	client *http.Client

	// token is the API token used for authentication.
	token string

	// APICall: API calls that have been performed by users can be queried by the API. This is helpful for debugging as well as billing.
	APICall *APICallService
	// APIToken: API tokens allow users to call the API outside of their session token that is used as a cookie in the user interface. Users can create, delete, and list their API tokens. But, of course, you need an API token to do this, so first be sure to generate one in the account UI.
	APIToken *APITokenService
	// App: Endpoints for third party app grant flows.
	App *AppService
	// Beta: Beta API endpoints. We will not charge for these endpoints while they are in beta.
	Beta *BetaService
	// Constant: Constants. These are helpful as helpers.
	Constant *ConstantService
	// Executor: Endpoints that allow for code execution or creation of code execution environments.
	Executor *ExecutorService
	// File: CAD file operations. Create, get, and list CAD file conversions. More endpoints will be added here in the future as we build out transforms, etc on CAD models.
	File *FileService
	// Hidden: Hidden API endpoints that should not show up in the docs.
	Hidden *HiddenService
	// Meta: Meta information about the API.
	Meta *MetaService
	// Ml: Machine learning to generate CAD models and other things.
	Ml *MlService
	// Modeling: Modeling API for updating your 3D files using the Zoo engine.
	Modeling *ModelingService
	// Oauth2: Endpoints that implement OAuth 2.0 grant flows.
	Oauth2 *Oauth2Service
	// Org: An organization is a group of users of the Zoo API. Here, we can add users to an org and perform operations on orgs.
	Org *OrgService
	// Payment: Operations around payments and billing.
	Payment *PaymentService
	// ServiceAccount: Service accounts allow organizations to call the API. Organization admins can create, delete, and list the service accounts for their org. Service accounts are scoped to an organization not individual users, these are better to use for automations than individual API tokens, since they won't stop working when an individual leaves the company.
	ServiceAccount *ServiceAccountService
	// Shortlink: Shortlinks are a way to create a short URL that redirects to a longer URL. This is useful for sharing links that are long and unwieldy.
	Shortlink *ShortlinkService
	// Store: Operations involving our swag store.
	Store *StoreService
	// Unit: Unit conversion operations.
	Unit *UnitService
	// User: A user is someone who uses the Zoo API. Here, we can create, delete, and list users. We can also get information about a user. Operations will only be authorized if the user is requesting information about themselves.
	User *UserService
}

// APICallService: API calls that have been performed by users can be queried by the API. This is helpful for debugging as well as billing.
type APICallService service

// APITokenService: API tokens allow users to call the API outside of their session token that is used as a cookie in the user interface. Users can create, delete, and list their API tokens. But, of course, you need an API token to do this, so first be sure to generate one in the account UI.
type APITokenService service

// AppService: Endpoints for third party app grant flows.
type AppService service

// BetaService: Beta API endpoints. We will not charge for these endpoints while they are in beta.
type BetaService service

// ConstantService: Constants. These are helpful as helpers.
type ConstantService service

// ExecutorService: Endpoints that allow for code execution or creation of code execution environments.
type ExecutorService service

// FileService: CAD file operations. Create, get, and list CAD file conversions. More endpoints will be added here in the future as we build out transforms, etc on CAD models.
type FileService service

// HiddenService: Hidden API endpoints that should not show up in the docs.
type HiddenService service

// MetaService: Meta information about the API.
type MetaService service

// MlService: Machine learning to generate CAD models and other things.
type MlService service

// ModelingService: Modeling API for updating your 3D files using the Zoo engine.
type ModelingService service

// Oauth2Service: Endpoints that implement OAuth 2.0 grant flows.
type Oauth2Service service

// OrgService: An organization is a group of users of the Zoo API. Here, we can add users to an org and perform operations on orgs.
type OrgService service

// PaymentService: Operations around payments and billing.
type PaymentService service

// ServiceAccountService: Service accounts allow organizations to call the API. Organization admins can create, delete, and list the service accounts for their org. Service accounts are scoped to an organization not individual users, these are better to use for automations than individual API tokens, since they won't stop working when an individual leaves the company.
type ServiceAccountService service

// ShortlinkService: Shortlinks are a way to create a short URL that redirects to a longer URL. This is useful for sharing links that are long and unwieldy.
type ShortlinkService service

// StoreService: Operations involving our swag store.
type StoreService service

// UnitService: Unit conversion operations.
type UnitService service

// UserService: A user is someone who uses the Zoo API. Here, we can create, delete, and list users. We can also get information about a user. Operations will only be authorized if the user is requesting information about themselves.
type UserService service