openapi: 3.1.0
security:
- BearerAuth: []
info:
  title: Twilio SendGrid Partner API
  summary: The Twilio SendGrid Partner Settings API allows you to integrate your SendGrid
    account with our partners to increase your SendGrid experience and functionality.
  description: The Twilio SendGrid Partner Settings API allows you to integrate your
    SendGrid account with our partners to increase your SendGrid experience and functionality.
    For more information about our partners and how you can begin integrating with
    them, please visit our [Partners page](https://sendgrid.com/partners/marketplace/).
  termsOfService: https://www.twilio.com/legal/tos
  contact:
    name: Twilio SendGrid Support
    url: https://support.sendgrid.com/hc/en-us
  license:
    name: MIT
    url: https://code.hq.twilio.com/twilio/sendgrid-oas/blob/main/LICENSE
  version: 1.0.0
  x-sendgrid:
    libraryPackage: partner
servers:
- url: https://api.sendgrid.com
  description: for global users and subusers
- url: https://api.eu.sendgrid.com
  description: for EU regional subusers
paths:
  /v3/partner_settings:
    get:
      operationId: ListPartnerSetting
      summary: Returns a list of all partner settings.
      tags:
      - Partner Settings
      description: '**This endpoint allows you to retrieve a paginated list of all
        partner settings that you can enable.**


        You can use the `limit` query parameter to set the page size. If your list
        contains more items than the page size permits, you can make multiple requests.


        Use the `offset` query parameter to control the position in the list from
        which to start retrieving additional items.''

        '
      parameters:
      - name: limit
        in: query
        description: '`limit` sets the page size, i.e. maximum number of items from
          the list to be returned for a single API request. If omitted, the default
          page size is used.'
        schema:
          type: integer
      - $ref: '#/components/parameters/PaginationCommonOffset'
      - $ref: '#/components/parameters/OnBehalfOf'
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  result:
                    type: array
                    items:
                      type: object
                      properties:
                        title:
                          type: string
                          description: The title of the partner.
                        enabled:
                          type: boolean
                          description: Indicates if this partner setting has been
                            enabled.
                        name:
                          type: string
                          description: The name of the partner setting.
                        description:
                          type: string
                          description: A description of this partner setting.
                      required:
                      - title
                      - enabled
                      - name
                      - description
              examples:
                response:
                  value:
                    result:
                    - title: Partner title
                      enabled: true
                      name: partner_name
                      description: A description of a partner.
components:
  schemas: {}
  responses: {}
  parameters:
    OnBehalfOf:
      name: on-behalf-of
      in: header
      description: 'The `on-behalf-of` header allows you to make API calls from a
        parent account on behalf of the parent''s Subusers or customer accounts. You
        will use the parent account''s API key when using this header. When making
        a call on behalf of a customer account, the property value should be "account-id"
        followed by the customer account''s ID (e.g., `on-behalf-of: account-id <account-id>`).
        When making a call on behalf of a Subuser, the property value should be the
        Subuser''s username (e.g., `on-behalf-of: <subuser-username>`). See [**On
        Behalf Of**](https://docs.sendgrid.com/api-reference/how-to-use-the-sendgrid-v3-api/on-behalf-of)
        for more information.'
      required: false
      schema:
        type: string
    PaginationCommonOffset:
      name: offset
      in: query
      required: false
      description: The number of items in the list to skip over before starting to
        retrieve the items for the requested page. The default `offset` of `0` represents
        the beginning of the list, i.e. the start of the first page. To request the
        second page of the list, set the `offset` to the page size as determined by
        `limit`. Use multiples of the page size as your `offset` to request further
        consecutive pages. E.g. assume your page size is set to `10`. An `offset`
        of `10` requests the second page, an `offset` of `20` requests the third page
        and so on, provided there are sufficiently many items in your list.
      schema:
        type: integer
        minimum: 0
        default: 0
  examples: {}
  requestBodies: {}
  headers: {}
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: Twilio SendGrid requires you to authenticate with its APIs using
        an API key. The API key must be sent as a bearer token in the Authorization
        header.
tags:
- name: Partner Settings
  description: Twilio SendGrid Partner Settings API
externalDocs:
  description: Twilio SendGrid's official developer documentation.
  url: https://www.twilio.com/docs/sendgrid