Salable API | Salable

# Salable API Salable is a comprehensive solution tailored for SaaS businesses, streamlining the design and management of pricing models, subscriptions, and licensing. This documentation is designed to guide you through integrating with Salable's features via our REST API. ## HTTP Endpoints - Use HTTP endpoints to access different features. - Send requests using JSON and receive JSON responses. ## Authentication Secure your requests by sending your api key on the `x-api-key` request header for authentication. The API Key can be created in the Salable dashboard. Select only the scopes you need will to access. If you're using this in combination with our SDKs be sure to only select read only scopes. > NOTE: If you'd like to use test mode via the API, make sure to use an API key generated in test mode (prefixed with `test_`). ## Quick Start To get up and running, you need to work through the following steps. - Set up a Salable Account and Organization - Connect Stripe to Salable (You can skip this for a free product) - Build your products and plans - Generate your API key - Make your first API call with the request header "version" set to "v2" ## HTTP Status Codes We use standard HTTP status codes for both success and failure responses. | HTTP Code | What it means | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | 200 | The request was successful and the action has been completed. | | 201 | This will be sent for the successful completion of POST requests and indicates that the new item was created, eg. a new license. | | 204 | The request was successful, no content to returned. | | 206 | The request was partially successful. | | 400 | There was a request validation error and the request couldn't be completed. | | 401 | There was an authentication problem. If you get this error you should make sure your API key is included in the `x-api-key` header. | | 403 | There was an authorisation issue. If you get this error you should check your API key has the correct scopes and that you're in the right organisation | | 404 | The request couldn't be completed as the requested resource(s) doesn't exist. | | 500 | A problem on our side. If you experience one of these errors, reach out to us and we will help. |