Drata · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Drata Procurement Connection Mappings API

3 actions 3 updates phrasing extends openapi/drata-procurement-connection-mappings-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Drata's API. It is a proposal applied on top of the contract, not a document Drata publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/connections/{connectionId}/vendor-mapping'].get
$.paths['/connections/{connectionId}/vendor-mapping'].put

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Drata Procurement Connection Mappings API
  version: 1.0.0
extends: openapi/drata-procurement-connection-mappings-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/connections/{connectionId}/vendor-mapping'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a procurement vendor mapping
      effect: read
      questions:
      - How is our Ironclad or Tropic data mapped into vendors?
      - Is dry run mode on for a procurement connection's vendor mapping?
      instructions:
      - text: Get the vendor mapping for procurement connection {connectionId}.
        slots:
          connectionId: path.connectionId
      - text: Show the JSONata vendor mapping and filters for connection {connectionId}.
        slots:
          connectionId: path.connectionId
      method: generated
      generated: '2026-09-26'
- target: $.paths['/connections/{connectionId}/vendor-mapping'].put
  update:
    x-apievangelist-phrasing:
      intent: Update a procurement vendor mapping
      effect: write
      questions:
      - Can I change how procurement records map to vendor fields?
      - How do I turn off dry run so the procurement sync creates vendors?
      instructions:
      - text: Set the vendor mapping for connection {connectionId} to {vendorMapping}.
        slots:
          connectionId: path.connectionId
          vendorMapping: requestBody.vendorMapping
      - text: Set dry run to {dryRun} on procurement connection {connectionId}.
        slots:
          connectionId: path.connectionId
          dryRun: requestBody.dryRun
      - text: Only import vendor types {vendorTypes} from procurement connection {connectionId}.
        slots:
          connectionId: path.connectionId
          vendorTypes: requestBody.vendorTypes
      method: generated
      generated: '2026-09-26'