From 22e41cafacda215746c1e6415069f0484f1b6b5a Mon Sep 17 00:00:00 2001 From: Ben Tranter Date: Mon, 25 Jul 2022 14:09:12 -0400 Subject: [PATCH] billing/pdf: add content type header The response for `/v2/customers/my/invoices/{uuid}/pdf` contains a `content-type` header in the response, so we should include that in the spec. --- specification/resources/billing/responses/invoice_pdf.yml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/specification/resources/billing/responses/invoice_pdf.yml b/specification/resources/billing/responses/invoice_pdf.yml index 77755f939..e911dec42 100644 --- a/specification/resources/billing/responses/invoice_pdf.yml +++ b/specification/resources/billing/responses/invoice_pdf.yml @@ -1,7 +1,9 @@ -description: >- +description: >- The response will be a PDF file. headers: + content-type: + $ref: '../../../shared/headers.yml#/content-type' content-disposition: $ref: '../../../shared/headers.yml#/content-disposition' ratelimit-limit: @@ -12,7 +14,7 @@ headers: $ref: '../../../shared/headers.yml#/ratelimit-reset' content: - application/pdf: + application/pdf: schema: type: string - format: binary \ No newline at end of file + format: binary