swag-payments/spec
Natalia Pulina cffbeddab4 HG-236: Temporary separation of PaymentFlow, readOnly should be handl… (#75)
* HG-236: Temporary separation of PaymentFlow, readOnly should be handled in future

* HG-236: Don't define OnHoldExpiration as separate type
2017-07-14 15:31:09 +04:00
..
code_samples ITS-21: Prepare for the release (#31) 2017-02-06 15:09:03 +03:00
definitions HG-236: Temporary separation of PaymentFlow, readOnly should be handl… (#75) 2017-07-14 15:31:09 +04:00
paths CAPI-153: Support of holds added (#70) 2017-06-30 17:39:08 +03:00
wsd general grammar fixes (#36) 2017-02-06 20:15:39 +03:00
README.md ITS-21: Prepare for the release (#31) 2017-02-06 15:09:03 +03:00
swagger.yaml CAPI-141: sync accountID type with damsel (#67) 2017-06-05 20:57:02 +03:00

Global headers

In order to minimize duplications you can use headers global object (similar to definitions, responses). During build process all references to global headers will be inlined and headers will be removed form resulting spec so spec will be valid (global headers is not allowed by Swagger spec):

Example:

...
headers:
  Rate-Limit-Limit:
    description: The number of allowed requests in the current period
    type: integer
...
paths:
  /api-keys:
    get:
      summary: Retrieve a list of api keys
      responses:
        200:
          description: A list of api keys was retrieved successfully
          headers:
            Rate-Limit-Limit:
              $ref: "#/headers/Rate-Limit-Limit"