Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/stripe/openapi
An OpenAPI specification for the Stripe API.
https://github.com/stripe/openapi
Last synced: about 1 month ago
JSON representation
An OpenAPI specification for the Stripe API.
- Host: GitHub
- URL: https://github.com/stripe/openapi
- Owner: stripe
- License: mit
- Created: 2017-03-14T22:53:27.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2024-05-22T18:07:18.000Z (4 months ago)
- Last Synced: 2024-05-22T18:32:41.145Z (4 months ago)
- Size: 278 MB
- Stars: 366
- Watchers: 19
- Forks: 115
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Stripe's OpenAPI Specification
This repository contains [OpenAPI specifications][openapi] for Stripe's API.
[Changelog](https://github.com/stripe/openapi/releases/)
Files can be found in the `openapi/` directory:
* `spec3.{json,yaml}:` OpenAPI 3.0 spec matching the public Stripe API.
* `spec3.sdk.{json,yaml}:` Expanded OpenAPI 3.0 spec intended for Stripe-internal
use.
* Contains special annotations, deprecated endpoints, and pre-release
features specifically intended to support generating Stripe API
libraries. Users should use the `spec3.{json,yaml}` variant instead.
* `fixtures3.{json,yaml}`: Test fixtures for resources in `spec3`. See below
for more information.
We used to support OpenAPI 2.0, but have since deprecated its use, and it's no
longer receiving updates. It is available on
[old versions](https://github.com/stripe/openapi/tree/v83) of this repository.
The specs provided in this repository do not explicity target
[openapi-generator](https://github.com/OpenAPITools/openapi-generator). They are instead generated via a custom closed-source
generator.
## Vendor Extensions
The specification ships with a few vendor-specific fields to help represent
information in ways that are difficult in OpenAPI by default.
### `x-expandableFields`
Resources include an `x-expandableFields` that contains a list of fields that
are expandable by making an API request with an `expand` parameter. See
[expanding objects][expand].
For example:
``` yaml
definitions:
...
charge:
...
x-expandableFields:
- balance_transaction
```
### `x-expansionResources`
Any expandable field within a resource contains a set of references to the
resources that it might be expanded to.
For example:
``` yaml
definitions:
...
charge:
properties:
...
balance_transaction:
description: ID of the balance transaction that describes the impact of this
charge on your account balance (not including refunds or disputes).
type:
- string
x-expansionResources:
oneOf:
- "$ref": "#/definitions/balance_transaction"
```
### `x-resourceId` and Fixtures
Resources include `x-resourceId` which is a canonical name for each resource.
It can be used in conjunction with `openapi/fixtures{2,3}.{json,yaml}` to look
up a sample representation (otherwise known as a "fixture") of the resource.
For example:
``` yaml
# spec.yaml
---
definitions:
...
charge:
...
x-resourceId: charge
# fixtures.yaml
---
invoice_line_item:
...
```
## Updates
Please make updates to the script included in `bin` to help maintain
consistency and commit cleanliness (search JIRA for full instructions):
bin/update
## Development
Run the test suite:
make
[expand]: https://stripe.com/docs/api/#expanding_objects
[openapi]: https://www.openapis.org/