> ## Documentation Index
> Fetch the complete documentation index at: https://gcore.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a single Addendum

> Retrieve a single `Addendum` by ID.



## OpenAPI

````yaml /api-reference/services_documented/billing_reseller_api.yaml get /billing/org/v1/addendums/{id}
openapi: 3.1.0
info:
  title: Gcore OpenAPI – Billing Reseller API
  description: >-
    This OpenAPI is an aggregated OpenAPI specification that unifies all Gcore
    products into a single file. It covers Cloud, CDN, DNS, WAAP, DDoS
    Protection, Object Storage, Streaming, and FastEdge services.
  version: '2026-05-14T07:00:22.640261+00:00'
servers:
  - url: https://api.gcore.com
security:
  - APIKey: []
tags:
  - name: addendums
    description: Operations on client addendums
    x-displayName: addendums
  - name: calc_rules
    x-displayName: calc_rules
  - name: currencies
    x-displayName: currencies
  - name: erp-invoices
    x-displayName: erp-invoices
  - name: expenses
    description: Operations on expenses
    x-displayName: expenses
  - name: plans
    description: Operations on tariff plans and their contents
    x-displayName: plans
  - name: products
    x-displayName: products
  - name: reports
    description: >-
      Operations involving reports and the associated background tasks that
      handle their processing
    x-displayName: reports
  - name: trials
    x-displayName: trials
paths:
  /billing/org/v1/addendums/{id}:
    get:
      tags:
        - addendums
      summary: Get a single Addendum
      description: Retrieve a single `Addendum` by ID.
      operationId: v1_addendums_retrieve
      parameters:
        - in: path
          name: id
          schema:
            type: integer
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AddendumForOrgSerializerV1'
          description: Request successful.
        '401':
          description: Authentication credentials were not provided or are invalid.
        '403':
          description: You do not have permission to perform this action.
        '404':
          description: The requested resource was not found.
components:
  schemas:
    AddendumForOrgSerializerV1:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        client_id:
          type: integer
          readOnly: true
          description: The ID of the client associated with the addendum.
        client:
          allOf:
            - $ref: '#/components/schemas/CustomerPayerCommonShort'
          readOnly: true
          description: The client associated with the addendum.
        status:
          enum:
            - upcoming
            - active
            - paused
            - stopped
          type: string
          x-spec-enum-id: a6691db649b8bdef
          readOnly: true
          description: |-
            Addendum status

            - `upcoming` - upcoming
            - `active` - active
            - `paused` - paused
            - `stopped` - stopped
        active_range:
          allOf:
            - $ref: '#/components/schemas/DateTimeTZRange'
          readOnly: true
          description: The time range during which the addendum is active.
        created_at:
          type: string
          format: date-time
          readOnly: true
          description: Date of current addendum creation
        currency:
          allOf:
            - $ref: '#/components/schemas/CurrencyCommonShort'
          readOnly: true
          description: The currency used in the addendum.
        plan:
          allOf:
            - $ref: '#/components/schemas/PlanCommonShort'
          readOnly: true
          description: The plan associated with the addendum.
        product:
          allOf:
            - $ref: '#/components/schemas/ProductCommonShort'
          readOnly: true
          description: The product associated with the addendum.
        status_at_active_at:
          type: string
          nullable: true
          readOnly: true
          description: >-
            Status of the addendum at the requested `active_at` time.


            This field is not present by default, but it can be requested by
            passing the `active_at` query parameter.
      required:
        - active_range
        - client
        - client_id
        - created_at
        - currency
        - id
        - plan
        - product
        - status
        - status_at_active_at
    CustomerPayerCommonShort:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        company_name:
          type: string
          readOnly: true
      required:
        - company_name
        - id
    DateTimeTZRange:
      type: object
      description: Date-time range with start and end fields.
      properties:
        start:
          type: string
          format: date-time
          nullable: true
        end:
          type: string
          format: date-time
          nullable: true
    CurrencyCommonShort:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        char_code:
          type: string
          description: Currency iso4217 char code
          pattern: ^[A-Z]{3}$
          maxLength: 3
        symbol:
          type: string
          nullable: true
          description: Currency symbol, for example '$'
          maxLength: 10
      required:
        - char_code
        - id
    PlanCommonShort:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        name:
          type: string
          readOnly: true
      required:
        - id
        - name
    ProductCommonShort:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        name:
          type: string
          readOnly: true
        internal_name:
          type: string
          maxLength: 25
      required:
        - id
        - internal_name
        - name
  securitySchemes:
    APIKey:
      description: >-
        API key for authentication. Make sure to include the word `apikey`,
        followed by a single space and then your token.

        Example: `apikey 1234$abcdef`
      type: apiKey
      in: header
      name: Authorization

````