fix: remove x-idempotency-key from api docs
This was never read by the HTTP server.
@@ -67,13 +67,6 @@ paths:
example: "rs4f9915"
schema:
type: string
- - name: X-Idempotency-Key
- in: header
- description: Idempotent key in the header which expires after 24 hours. These strings should contain enough entropy to not collide with each other in your requests.
- example: "a4f88150"
- required: false
- schema:
- type: string
- name: fileID
in: path
description: File ID
@@ -371,13 +364,6 @@ paths:
example: "rs4f9915"
schema:
type: string
- - name: X-Idempotency-Key
- in: header
- description: Idempotent key in the header which expires after 24 hours. These strings should contain enough entropy to not collide with each other in your requests.
- example: "a4f88150"
- required: false
- schema:
- type: string
- name: fileID
in: path
description: File ID
@@ -420,13 +406,6 @@ paths:
example: "rs4f9915"
schema:
type: string
- - name: X-Idempotency-Key
- in: header
- description: Idempotent key in the header which expires after 24 hours. These strings should contain enough entropy to not collide with each other in your requests.
- example: "a4f88150"
- required: false
- schema:
- type: string
- name: fileID
in: path
description: File ID
@@ -493,13 +472,6 @@ paths:
example: "rs4f9915"
schema:
type: string
- - name: X-Idempotency-Key
- in: header
- description: Idempotent key in the header which expires after 24 hours. These strings should contain enough entropy to not collide with each other in your requests.
- example: "a4f88150"
- required: false
- schema:
- type: string
- name: fileID
in: path
description: File ID
@@ -604,13 +576,6 @@ paths:
example: "rs4f9915"
schema:
type: string
- - name: X-Idempotency-Key
- in: header
- description: Idempotent key in the header which expires after 24 hours. These strings should contain enough entropy to not collide with each other in your requests.
- example: "a4f88150"
- required: false
- schema:
- type: string
requestBody:
description: ACH file (in Nacha or JSON formatting) along with optional segment configuration
required: false
