Read Feature Template
Returns a single feature template. Archived feature templates are not addressable here and return 404. Restore a template first to read or update it.
Authorization
BasicAuth The username is a Maxio Chargify API key. The password is x.
In: header
Path Parameters
The Advanced Billing id of the feature template.
Response Body
application/json
application/json
curl -X GET "https://example.com/features/0.json"{ "feature": { "id": 0, "key": "string", "name": "string", "description": "string", "kind": "access_right", "unit": "string", "value_type": "text", "default_value": "string", "default_periodicity_interval": 0, "default_periodicity_unit": "hour", "archived_at": "2019-08-24T14:15:22Z", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z", "products_count": 0, "plans_count": 0 }}Create Feature Template POST
Defines a new feature at the site level. Feature templates aren't billable on their own. Attach a template to products or components to grant the feature to subscribers.
Archive Feature Template DELETE
Archives a feature template. Archived feature templates are not addressable via [Read Feature Template](https://maxio-test-wp.pages.dev/api/openapi/feature-templates/readFeatureTemplate) or [Update Feature Template](https://maxio-test-wp.pages.dev/api/openapi/feature-templates/updateFeatureTemplate). Both endpoints return `404` until the template is restored. The feature template record itself is never hard-deleted, and can always be restored with [Restore Feature Template](https://maxio-test-wp.pages.dev/api/openapi/feature-templates/restoreFeatureTemplate). Reversibility does not extend to `remove_from_catalog=true`: the feature catalog items and entitlements that parameter destroys are gone permanently, and restoring the template will not bring subscriber access back.