Yelp Access Token API

openapi: 3.2.0
info:
  title: Respond to Reviews Access Token API
  version: '1.0'
servers:
- url: https://partner-api.yelp.com/
security:
- {}
tags:
- name: Access Token
paths:
  /token/v1:
    post:
      tags:
      - Access Token
      summary: Get Access Token
      operationId: redeem_authorization_code_for_access_token
      description: Using the authorization code assigned to the business user, this endpoint will send back an access token.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - client_id
              - client_secret
              - code
              - grant_type
              properties:
                client_id:
                  description: ID assigned by Yelp for the third-party system that will make user-authorized requests to Yelp.
                  type: string
                client_secret:
                  description: Client secret assigned by Yelp for the third-party system that will make user-authorized requests to Yelp.
                  type: string
                code:
                  description: A unique code that will be used by the client to redeem an access token.
                  type: string
                grant_type:
                  description: The grant being presented in order to exchange for an access token. For example, when redeeming the authorization code for an access token, this value will be authorization_code.
                  type: string
                redirect_uri:
                  description: The client-provided redirect endpoint URL. If no redirect_uri was provided during authorization, it is optional here.
                  type: string
      responses:
        '200':
          description: Successfully redeemed the authorization code for an access token.
          content:
            application/json:
              examples:
                Result:
                  value:
                    access_token: <128_character_long_string>
                    token_type: Bearer
                    Expires_in: 10000,
                    expiration_timestamp: '2016-08-26T15:25:16+00:00'
                    refresh_token: <128_character_long_string>
              schema:
                type: object
                properties:
                  access_token:
                    description: Token issued by the authorization server. The token will be 128 characters long. Tokens will be valid for the R2R api for 7 days.
                    type: string
                  expires_in:
                    description: Seconds until token expires.
                    type: integer
                  expiration_timestamp:
                    description: The expiration time of the access token in ISO8601 format.
                    type: string
                  token_type:
                    description: The type of token issued. Default to ‘Bearer’
                    type: string
                  refresh_token:
                    description: Token code used in refresh endpoint. The token will be 128 characters long.
                    type: string
        '400':
          description: "This error is returned in any of the following scenarios:\n\n| id                     | Description                                                                      | http_code\n| ---------------------- | -------------------------------------------------------------------------------- | --------------\n| INVALID_REQUEST        | Missing a required parameter or includes an unsupported parameter.               | HTTPBadRequest (400)\n| INVALID_GRANT\t       | The provided authorization grant is invalid, expired or revoked.\t              | HTTPBadRequest (400)\n| UNAUTHORIZED_CLIENT    | The authenticated client is not authorized to use this authorization grant type. |\tHTTPBadRequest (400)\n| UNSUPPORTED_GRANT_TYPE | The authorization grant type is not supported by the authorization server.\t      | HTTPBadRequest (400)\n"
          content:
            application/json:
              examples:
                Invalid Request:
                  value:
                    id: INVALID_REQUEST
                    description: Missing a required parameter or includes an unsupported parameter.
                    http_code: HTTPBadRequest (400)
              schema:
                type: object
                properties:
                  id:
                    type: string
                  description:
                    type: string
                  http_code:
                    type: string
        '401':
          description: 'This error is returned in any of the following scenarios:


            | id             | Description                                                                                                                  | http_code

            | -------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------

            | INVALID_CLIENT | Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method. | HTTPUnauthorized (401)

            '
          content:
            application/json:
              $ref: '#/paths/~1token~1v1/post/responses/400/content/application~1json'
              examples:
                Invalid Client:
                  value:
                    id: INVALID_CLIENT
                    description: Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method.
                    http_code: HTTPUnauthorized (401)
        '404':
          description: 'This error is returned in any of the following scenarios:


            | id               | Description                        | http_code

            | ---------------- | ---------------------------------- | --------------

            | CLIENT_NOT_FOUND | Supplied client ID does not exist. | HTTPNotFound (404)

            '
          content:
            application/json:
              $ref: '#/paths/~1token~1v1/post/responses/400/content/application~1json'
              examples:
                Client Not Found:
                  value:
                    id: CLIENT_NOT_FOUND
                    description: Supplied client ID does not exist.
                    http_code: HTTPNotFound (404)
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'To authenticate API calls with the API Key, set the Authorization HTTP header value as `Bearer API_KEY`.


        Example: `Bearer 23813239889e947efd3e787cc41b0b839f442a85c5bfd30bd4b9a85ec3a54d5cae4d52b37ff52e64deb9c83bd04883812a6cebde04f2f25752f31be0ac74b514`.


        You can create or find your API Key at [yelp.com](https://www.yelp.com/developers/v3/manage_app).

        '
x-readme-fauxas: true
x-provenance:
  method: searched
  source: https://docs.developer.yelp.com/reference
  harvested: '2026-11-05'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://docs.developer.yelp.com/reference/create_review_response.md
  - https://docs.developer.yelp.com/reference/get-businesses-associated-with-an-access-token.md
  - https://docs.developer.yelp.com/reference/get_businesses_associated_with_access_token.md
  - https://docs.developer.yelp.com/reference/redeem_authorization_code_for_access_token.md
  - https://docs.developer.yelp.com/reference/retrieve_business_owner_information-1.md
  merge:
    pages: 5
    deduped: 5
    conflicts_kept_first: 2