# Initiate Google OAuth login flow

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /webhook/partner-google-oauth-url:
    post:
      summary: Initiate Google OAuth login flow
      deprecated: false
      description: >-
        These endpoints allow email infrastructure provider partners to
        programmatically initiate the Google/Microsoft OAuth login flow to add
        an account to PlusVibe.

        ***Infrastructure provider is required to have its own browser
        automation***
      operationId: >-
        For Email Infra Provider
        Partner_pipl-partner-google-oauth-url-api/initiate-google-oauth-login-flow
      tags:
        - For Email Infra Provider Partner
        - For Email Infra Provider Partner
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                flow:
                  type: string
                pipl_username:
                  type: string
                pipl_password:
                  type: string
                workspace_id:
                  type: string
                min_interval:
                  type: integer
                  description: ' the minimum sending interval per account'
                daily_limit:
                  type: integer
                  description: daily campaign limit
                enable_camp_rampup:
                  type: string
                  description: >-
                    enables or disables campaign ramp-up (yes = enable, no =
                    disable)
                camp_ramup_start:
                  type: integer
                  description: the initial campaign ramp-up value
                camp_rampup_increment:
                  type: integer
                  description: the daily campaign ramp-up increment
                enable_warmup:
                  type: string
                  description: enables or disables warm-up (yes = enable, no = disable)
                warmup_daily_limit:
                  type: integer
                  description: daily warm-up email limit
                enable_warmup_rampup:
                  type: string
                  description: >-
                    enables or disables warm-up ramp-up (yes = enable, no =
                    disable)
                warmup_rampup_start:
                  type: integer
                  description: the initial warm-up ramp-up value
                warmup_rampup_increment:
                  type: integer
              required:
                - flow
                - pipl_username
                - pipl_password
                - workspace_id
              x-apidog-orders:
                - flow
                - pipl_username
                - pipl_password
                - workspace_id
                - min_interval
                - daily_limit
                - enable_camp_rampup
                - camp_ramup_start
                - camp_rampup_increment
                - enable_warmup
                - warmup_daily_limit
                - enable_warmup_rampup
                - warmup_rampup_start
                - warmup_rampup_increment
            example:
              flow: app_user
              pipl_username: pv@username.com
              pipl_password: fuibrn567
              workspace_id: 65099a0dd96fae8ab61120c0
              min_interval: 4
              daily_limit: 30
              enable_camp_rampup: 'yes'
              camp_ramup_start: 4
              camp_rampup_increment: 2
              enable_warmup: 'yes'
              warmup_daily_limit: 20
              enable_warmup_rampup: 'yes'
              warmup_rampup_start: 5
              warmup_rampup_increment: 1
      responses:
        '200':
          description: Successfully generated redirect URL for OAuth
          content:
            application/json:
              schema:
                type: object
                properties:
                  code:
                    type: integer
                    description: ''
                    examples:
                      - 1
                  message:
                    type: string
                    description: ''
                    examples:
                      - success
                  data:
                    type: object
                    description: ''
                    properties:
                      redirect_url:
                        type: string
                        description: ''
                        format: uri
                        examples:
                          - >-
                            https://accounts.google.com/o/oauth2/v2/auth?access_type=offline&prompt=consent&include_granted_scopes=true&scope=profile%20email%20https%3A%2F%2Fmail.google.com&state=...&response_type=code&client_id=...&redirect_uri=...
                      client_id:
                        type: string
                        examples:
                          - >-
                            550255402234-v3e4mu3ugkvrl2ngaai0nnsv5nll1nm7.apps.googleusercontent.com
                    x-apidog-orders:
                      - redirect_url
                      - client_id
                x-apidog-orders:
                  - code
                  - message
                  - data
          headers: {}
          x-apidog-name: OK
      security:
        - ApiKeyAuth: []
          x-apidog:
            schemeGroups:
              - id: uS5KiuC4wfZHK42AzOfA_
                schemeIds:
                  - ApiKeyAuth
            required: true
            use:
              id: uS5KiuC4wfZHK42AzOfA_
            scopes:
              uS5KiuC4wfZHK42AzOfA_:
                ApiKeyAuth: []
      x-apidog-folder: For Email Infra Provider Partner
      x-apidog-status: released
      x-run-in-apidog: https://app.apidog.com/web/project/929054/apis/api-17238038-run
components:
  schemas: {}
  securitySchemes:
    ApiKeyAuth:
      type: apikey
      in: header
      name: x-api-key
      description: |
        API key issued in the PlusVibe dashboard. The server reads it
        from the `x-api-key` header and injects it into the request as
        the `api_key` query parameter, which is why you will see
        `api_key` referenced in validation errors.
    apiKey:
      type: apikey
      in: body
      name: api_key
      description: API key passed in request body
servers:
  - url: https://api.plusvibe.ai/api/v1
    description: Prod Env
security:
  - ApiKeyAuth: []
    x-apidog:
      schemeGroups:
        - id: uS5KiuC4wfZHK42AzOfA_
          schemeIds:
            - ApiKeyAuth
      required: true
      use:
        id: uS5KiuC4wfZHK42AzOfA_
      scopes:
        uS5KiuC4wfZHK42AzOfA_:
          ApiKeyAuth: []

```