Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/workarea-commerce/workarea-api
Adds JSON REST APIs to the Workarea Commerce Platform
https://github.com/workarea-commerce/workarea-api
ecommerce json-api rest-api workarea workarea-commerce
Last synced: about 1 month ago
JSON representation
Adds JSON REST APIs to the Workarea Commerce Platform
- Host: GitHub
- URL: https://github.com/workarea-commerce/workarea-api
- Owner: workarea-commerce
- License: other
- Created: 2019-08-21T21:44:20.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2020-12-02T13:48:32.000Z (about 4 years ago)
- Last Synced: 2024-10-31T13:45:30.273Z (about 2 months ago)
- Topics: ecommerce, json-api, rest-api, workarea, workarea-commerce
- Language: Ruby
- Homepage: https://www.workarea.com
- Size: 1.04 MB
- Stars: 7
- Watchers: 4
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Workarea API
[![CI Status](https://github.com/workarea-commerce/workarea-api/workflows/CI/badge.svg)](https://github.com/workarea-commerce/workarea-api/actions)**workarea-api** defines an HTTP API, using JSON as a data format, for
programmatic access to your Workarea application. The Workarea API is
used for many purposes, such as integration with external services, or
providing an alternative user interface to your web store (like an
on-premises kiosk or mobile application). As such, Workarea provides two
separate APIs for different purposes:- The [Admin API][] is only available to admin users with the necessary
"API Access" permissions, and provides CRUD operations on all data models
in the application. It's primarily used for integration with external
service providers, such as an OMS or ERP.
- The [Storefront API][] has a slightly more complex authentication
scheme, because it's used by end-users to browse and purchase items on
the storefront. This API is suitable for building alternative user
interfaces to Workarea## Getting Started
To begin using the Workarea API, add the following to your **Gemfile**:
```ruby
gem 'workarea-api'
```Next, mount the API engines into **config/routes.rb**.
You can either use a path prefix:
```ruby
Rails.application.routes.draw do
# ...all your other absolutely fabulous Workarea routes...
mount Workarea::Api::Engine => '/api', as: :api# ...except this one. Make sure it's last to correctly handle errors and redirects.
mount Workarea::Storefront::Engine => '/', as: :storefront
end
```Or, a subdomain. To use a subdomain for your API, create a file at
**app/routing_constraints/api_subdomain_constraint.rb** with the
following contents:```ruby
class ApiSubdomainConstraint
def self.matches?(request)
request.subdomain =~ /^api/
end
end
```Then, wrap your `mount` statement with a `constraints` block:
```ruby
constraints ApiSubdomainConstraint do
mount Workarea::Api::Engine => '/', as: :api
end
```That will allow clients to access your API at https://api.yourtotallyamazingstore.com
If you use a routing constraint for your API, be sure to add the
following to **test/test_helper.rb** in your application to use the
correct domain for API requests:```ruby
class Workarea::IntegrationTest
setup do
host! host.gsub(/www/, 'api') if self.class.name.include?('Api::')
end
end
```## Configuration
This plugin provides a number of options for configuring its usage...
- **config.api_product_image_jobs_blacklist** configures the Dragonfly
processor jobs whose URLs are omitted from image JSON responses in the
Storefront API. Default is `:convert`, `:encode`, `:rotate`, `:optim`,
`:avatar`, and `:thumb`.
- **config.authentication_token_expiration** sets how long Storefront API auth
tokens last before they are expired. Default is `1.week`
- **config.max_api_bulk_data_size** configures the max amount of items which
may be included in a `Workarea::Api::Admin::BulkUpsert`
- **config.api_admin_ignore_definitions** prevents certain models from
being considered when Swagger JSON is being generated## Documentation
Documentation for API endpoints is available wherever the
`Workarea::Api::Engine` has been mounted, at the relative path `/docs`.
By default, this path is `/api/docs`. This documentation is loaded from
the gem source by default, but if you customize API endpoints, you'll
need to generate customized documentation with the following command:```bash
GENERATE_API_DOCS=true bin/rails workarea:test
```Documentation for the API is built using [documentation tests][], which
describe how each controller and action is to be documented. Look in the
aforementioned link to see some examples of documentation built using
the documentation tests.License
--------------------------------------------------------------------------------
Workarea Commerce Platform is released under the [Business Software License](https://github.com/workarea-commerce/workarea/blob/master/LICENSE)[Admin API]: https://github.com/workarea-commerce/workarea-api/tree/master/admin
[Storefront API]: https://github.com/workarea-commerce/workarea-api/tree/master/storefront
[documentation tests]: https://github.com/workarea-commerce/workarea-api/blob/master/storefront/test/documentation/workarea/api/storefront/products_documentation_test.rb