import { BaseClient, RequestOptions } from './base-client';
import { EmailProviderListResponse, EmailProviderResponse, EmailProviderUpdateRequest, EmailProviderCreateRequest } from './model';
/**
 * Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the
API and offers examples of usage.

The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice.

The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json)
 * @class EmailProvidersClient
 * @param {(string)} [url] - The URL of the API endpoint.
 */
export declare class EmailProvidersClient extends BaseClient {
    /**
     * Retrieve a list of email providers.
     * @method
     * @name EmailProvidersClient#listEmailProviders
     * @param {string} owner - The owner id you are requesting data for
     * @param {number} offset - An offset into the result set, useful for pagination
     * @param {number} limit - Limit the number of results to this value.
     * @param {string} sort - Sorting column or attribute name with an optional direction, e.g. `sort=name:desc`
     * @param {string} filter - A filter to apply to the data in RQL format.
     */
    listEmailProviders(owner: string, offset?: number, limit?: number, sort?: string, filter?: string, $options?: RequestOptions): Promise<EmailProviderListResponse>;
    /**
    * Creates a new email provider entity
    * @method
    * @name EmailProvidersClient#createEmailProvider
         * @param {object} request - Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the
    API and offers examples of usage.

    The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice.

    The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json)
    */
    createEmailProvider(request: EmailProviderCreateRequest, $options?: RequestOptions): Promise<EmailProviderResponse>;
    /**
     * Returns email provider details for the specified id
     * @method
     * @name EmailProvidersClient#getEmailProvider
     * @param {string} id - The UUID of the email provider
     */
    getEmailProvider(id: string, $options?: RequestOptions): Promise<EmailProviderResponse>;
    /**
    * Updates an existing email provider entity
    * @method
    * @name EmailProvidersClient#updateEmailProvider
         * @param {string} id - The UUID of the email provider
         * @param {object} request - Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the
    API and offers examples of usage.

    The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice.

    The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json)
    */
    updateEmailProvider(id: string, request: EmailProviderUpdateRequest, $options?: RequestOptions): Promise<EmailProviderResponse>;
}