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

# Drop approved CO file at SFTP path

> Virtual operation representing Tango writing the CO outbound file to
`/outbound/CO` on the SFTP server. Each file contains header + detail rows,
one line per CO line item, pipe-delimited. Files are produced only when
there is data; zero-dollar lines are excluded, negative COs are included.
After successful generation all exported COs are flagged as `Exported` in
Tango. The prior file is moved to the `Processed` subfolder with a
timestamp suffix before the new file is written.




## OpenAPI

````yaml /tango_projects/integrations/guides/co-outbound.yaml post /outbound/CO
openapi: 3.1.0
info:
  title: Tango CO Outbound
  version: '0.5'
  description: >
    SFTP file-based outbound integration. Tango exports approved Change Order
    (CO)

    records to the client target system as a pipe-delimited text file dropped to

    Tango's SFTP server. One-way batch.


    The OpenAPI document models this non-HTTP delivery as a single virtual POST

    operation against the SFTP path. The row-level field definitions live in the

    `COOutboundRecord` schema.
  contact:
    name: Tango Analytics
  x-direction: outbound
  x-source: Tango
  x-destination: Client System
  x-transport: sftp
  x-file-format: pipe-delimited text (.txt)
  x-file-naming-convention: '{ClientName}_coout_MMDDYYYYHHMMSS.txt'
  x-frequency: pre-agreed batch schedule (not stated in design doc)
servers:
  - url: sftp://sftp.tangoanalytics.com
    description: Production SFTP host
    x-environment: production
    x-path: /outbound/CO
  - url: sftp://sftpdev.tangoanalytics.com
    description: Test SFTP host (SIT/UAT)
    x-environment: test
    x-path: /outbound/CO
security:
  - sftpUserPassword: []
tags:
  - name: CO Outbound
    description: Change Order outbound file delivery.
paths:
  /outbound/CO:
    post:
      tags:
        - CO Outbound
      summary: Drop approved CO file at SFTP path
      description: >
        Virtual operation representing Tango writing the CO outbound file to

        `/outbound/CO` on the SFTP server. Each file contains header + detail
        rows,

        one line per CO line item, pipe-delimited. Files are produced only when

        there is data; zero-dollar lines are excluded, negative COs are
        included.

        After successful generation all exported COs are flagged as `Exported`
        in

        Tango. The prior file is moved to the `Processed` subfolder with a

        timestamp suffix before the new file is written.
      operationId: deliverCOOutboundFile
      requestBody:
        required: true
        content:
          text/plain:
            schema:
              type: string
              format: binary
              description: Pipe-delimited rows; one CO line item per row.
              x-record-schema:
                $ref: '#/components/schemas/COOutboundRecord'
      responses:
        '200':
          description: File delivered (SFTP put succeeded).
components:
  securitySchemes:
    sftpUserPassword:
      type: http
      scheme: basic
      description: |
        SFTP user/password credentials. Concrete values are <TBD> in the source
        design doc — provided per environment via secure channel.

````