/** * AdvancedBilling * * This file was automatically generated for Maxio by APIMATIC v3.0 ( https://www.apimatic.io ). */ import { ApiResponse, RequestOptions } from '../core.js'; import { BasicDateField } from '../models/basicDateField.js'; import { CreateMetadataRequest } from '../models/createMetadataRequest.js'; import { CreateMetafieldsRequest } from '../models/createMetafieldsRequest.js'; import { ListMetafieldsResponse } from '../models/listMetafieldsResponse.js'; import { Metadata } from '../models/metadata.js'; import { Metafield } from '../models/metafield.js'; import { PaginatedMetadata } from '../models/paginatedMetadata.js'; import { ResourceType } from '../models/resourceType.js'; import { SortingDirection } from '../models/sortingDirection.js'; import { UpdateMetadataRequest } from '../models/updateMetadataRequest.js'; import { UpdateMetafieldsRequest } from '../models/updateMetafieldsRequest.js'; import { BaseController } from './baseController.js'; export declare class CustomFieldsController extends BaseController { /** * Creates metafields on a Site for either the Subscriptions or Customers resource. * * Metafields and their metadata are created in the Custom Fields configuration page on your Site. * Metafields can be populated with metadata when you create them or later with the [Update * Metafield]($e/Custom%20Fields/updateMetafield), [Create Metadata]($e/Custom%20Fields/createMetadata), * or [Update Metadata]($e/Custom%20Fields/updateMetadata) endpoints. The Create Metadata and Update * Metadata endpoints allow you to add metafields and metadata values to a specific subscription or * customer. * * Each site is limited to 100 unique metafields per resource. This means you can have 100 metafields * for Subscriptions and another 100 for Customers. * * > Note: After creating a metafield, the resource type cannot be modified. * * In the UI and product documentation, metafields and metadata are called Custom Fields. * * - Metafield is the custom field * - Metadata is the data populating the custom field. * * See [Custom Fields Reference](https://docs.maxio.com/hc/en-us/articles/24266140850573-Custom-Fields- * Reference) and [Custom Fields Tab](https://maxio.zendesk.com/hc/en-us/articles/24251701302925- * Subscription-Summary-Custom-Fields-Tab) for information on using Custom Fields in the Advanced * Billing UI. * * @param resourceType The resource type to which the metafields belong. * @param body * @return Response from the API call */ createMetafields(resourceType: ResourceType, body?: CreateMetafieldsRequest, requestOptions?: RequestOptions): Promise>; /** * Lists the metafields and their associated details for a Site and resource type. You can filter the * request to a specific metafield. * * @param resourceType The resource type to which the metafields belong. * @param name Filter by the name of the metafield. * @param page Result records are organized in pages. By default, the first page of * results is displayed. The page parameter specifies a page number of * results to fetch. You can start navigating through the pages to consume * the results. You do this by passing in a page parameter. Retrieve the * next page by adding ?page=2 to the query string. If there are no results * to return, then an empty result set will be returned. Use in query * `page=1`. * @param perPage This parameter indicates how many records to fetch in each request. * Default value is 20. The maximum allowed values is 200; any per_page * value over 200 will be changed to 200. Use in query `per_page=200`. * @param direction Controls the order in which results are returned. Use in query * `direction=asc`. * @return Response from the API call */ listMetafields({ resourceType, name, page, perPage, direction, }: { resourceType: ResourceType; name?: string; page?: number; perPage?: number; direction?: SortingDirection; }, requestOptions?: RequestOptions): Promise>; /** * Updates metafields on your Site for a resource type. Depending on the request structure, you can * update or add metafields and metadata to the Subscriptions or Customers resource. * * With this endpoint, you can: * * - Add metafields. If the metafield specified in current_name does not exist, a new metafield is * added. * >Note: Each site is limited to 100 unique metafields per resource. This means you can have 100 * metafields for Subscriptions and another 100 for Customers. * * - Change the name of a metafield. * >Note: To keep the metafield name the same and only update the metadata for the metafield, you * must use the current metafield name in both the `current_name` and `name` parameters. * * - Change the input type for the metafield. For example, you can change a metafield input type from * text to a dropdown. If you change the input type from text to a dropdown or radio, you must update * the specific subscriptions or customers where the metafield was used to reflect the updated * metafield and metadata. * * - Add metadata values to the existing metadata for a dropdown or radio metafield. * >Note: Updates to metadata overwrite. To add one or more values, you must specify all metadata * values including the new value you want to add. * * - Add new metadata to a dropdown or radio for a metafield that was created without metadata. * * - Remove metadata for a dropdown or radio for a metafield. * >Note: Updates to metadata overwrite existing values. To remove one or more values, specify all * metadata values except those you want to remove. * * - Add or update scope settings for a metafield. * >Note: Scope changes overwrite existing settings. You must specify the complete scope, including * the changes you want to make. * * @param resourceType The resource type to which the metafields belong. * @param body * @return Response from the API call */ updateMetafield(resourceType: ResourceType, body?: UpdateMetafieldsRequest, requestOptions?: RequestOptions): Promise>; /** * Deletes a metafield from your Site. Removes the metafield and associated metadata from all * Subscriptions or Customers resources on the Site. * * @param resourceType The resource type to which the metafields belong. * @param name The name of the metafield to be deleted * @return Response from the API call */ deleteMetafield(resourceType: ResourceType, name?: string, requestOptions?: RequestOptions): Promise>; /** * Creates metadata and metafields for a specific subscription or customer, or updates metadata values * of existing metafields for a subscription or customer. Metadata values are limited to 2 KB in size. * * If you create metadata on a subscription or customer with a metafield that does not already exist, * the metafield is created with the metadata you specify and it is always added as a text field. You * can update the input_type for the metafield with the [Update * Metafield]($e/Custom%20Fields/updateMetafield) endpoint. * * >Note: Each site is limited to 100 unique metafields per resource. This means you can have 100 * metafields for Subscriptions and another 100 for Customers. * * @param resourceType The resource type to which the metafields belong. * @param resourceId The Advanced Billing id of the customer or the subscription * for which the metadata applies * @param body * @return Response from the API call */ createMetadata(resourceType: ResourceType, resourceId: number, body?: CreateMetadataRequest, requestOptions?: RequestOptions): Promise>; /** * Lists metadata and metafields for a specific customer or subscription. * * @param resourceType The resource type to which the metafields belong. * @param resourceId The Advanced Billing id of the customer or the subscription for which the * metadata applies * @param page Result records are organized in pages. By default, the first page of results * is displayed. The page parameter specifies a page number of results to fetch. * You can start navigating through the pages to consume the results. You do * this by passing in a page parameter. Retrieve the next page by adding ?page=2 * to the query string. If there are no results to return, then an empty result * set will be returned. Use in query `page=1`. * @param perPage This parameter indicates how many records to fetch in each request. Default * value is 20. The maximum allowed values is 200; any per_page value over 200 * will be changed to 200. Use in query `per_page=200`. * @return Response from the API call */ listMetadata({ resourceType, resourceId, page, perPage, }: { resourceType: ResourceType; resourceId: number; page?: number; perPage?: number; }, requestOptions?: RequestOptions): Promise>; /** * Updates metadata and metafields on the Site and the customer or subscription specified, and updates * the metadata value on a subscription or customer. * * If you update metadata on a subscription or customer with a metafield that does not already exist, * the metafield is created with the metadata you specify and it is always added as a text field to the * Site and to the subscription or customer you specify. You can update the input_type for the * metafield with the Update Metafield endpoint. * * Each site is limited to 100 unique metafields per resource. This means you can have 100 metafields * for the Subscription resource and another 100 for the Customer resource. * * @param resourceType The resource type to which the metafields belong. * @param resourceId The Advanced Billing id of the customer or the subscription * for which the metadata applies * @param body * @return Response from the API call */ updateMetadata(resourceType: ResourceType, resourceId: number, body?: UpdateMetadataRequest, requestOptions?: RequestOptions): Promise>; /** * Deletes one or more metafields (and associated metadata) from the specified subscription or customer. * * @param resourceType The resource type to which the metafields belong. * @param resourceId The Advanced Billing id of the customer or the subscription for which the * metadata applies * @param name Name of field to be removed. * @param names Names of fields to be removed. Use in query: `names[]=field1&names[]=my- * field&names[]=another-field`. * @return Response from the API call */ deleteMetadata(resourceType: ResourceType, resourceId: number, name?: string, names?: string[], requestOptions?: RequestOptions): Promise>; /** * Lists metadata for a specified array of subscriptions or customers. * * @param resourceType The resource type to which the metafields belong. * @param page Result records are organized in pages. By default, the first page of * results is displayed. The page parameter specifies a page number of * results to fetch. You can start navigating through the pages to consume * the results. You do this by passing in a page parameter. Retrieve the * next page by adding ?page=2 to the query string. If there are no results * to return, then an empty result set will be returned. Use in query * `page=1`. * @param perPage This parameter indicates how many records to fetch in each request. * Default value is 20. The maximum allowed values is 200; any per_page * value over 200 will be changed to 200. Use in query `per_page=200`. * @param dateField The type of filter you would like to apply to your search. * @param startDate The start date (format YYYY-MM-DD) with which to filter the date_field. * Returns metadata with a timestamp at or after midnight (12:00:00 AM) in * your site’s time zone on the date specified. * @param endDate The end date (format YYYY-MM-DD) with which to filter the date_field. * Returns metadata with a timestamp up to and including 11:59:59PM in your * site’s time zone on the date specified. * @param startDatetime The start date and time (format YYYY-MM-DD HH:MM:SS) with which to * filter the date_field. Returns metadata with a timestamp at or after * exact time provided in query. You can specify timezone in query - * otherwise your site's time zone will be used. If provided, this * parameter will be used instead of start_date. * @param endDatetime The end date and time (format YYYY-MM-DD HH:MM:SS) with which to filter * the date_field. Returns metadata with a timestamp at or before exact * time provided in query. You can specify timezone in query - otherwise * your site's time zone will be used. If provided, this parameter will be * used instead of end_date. * @param withDeleted Allow to fetch deleted metadata. * @param resourceIds Allow to fetch metadata for multiple records based on provided ids. Use * in query: `resource_ids[]=122&resource_ids[]=123&resource_ids[]=124`. * @param direction Controls the order in which results are returned. Use in query * `direction=asc`. * @return Response from the API call */ listMetadataForResourceType({ resourceType, page, perPage, dateField, startDate, endDate, startDatetime, endDatetime, withDeleted, resourceIds, direction, }: { resourceType: ResourceType; page?: number; perPage?: number; dateField?: BasicDateField; startDate?: string; endDate?: string; startDatetime?: string; endDatetime?: string; withDeleted?: boolean; resourceIds?: number[]; direction?: SortingDirection; }, requestOptions?: RequestOptions): Promise>; } //# sourceMappingURL=customFieldsController.d.ts.map