Service Groups Create API

Route

POST

Purpose

RESTful API for inserting new rows into service_groups table.


Parameters


token string 1 required
Authentication token for either an application or session.
slug string 1 required
unique slug of service_group that is being created.
name string 3 required
Name of service_group that is being created.
pricing_metric string 4
Pricing Metric of service_group that is being created.
Possible values
  • sq_ft
  • list_price

service_type string 5
service type of service_group that is being created.
Possible values
  • primary
  • add_on

quantity_required boolean 6
Quantity required boolean of service_group that is being created.
designation_id array 7
Designation ID's of service_group that is being created.
Possible values
  • 1
  • 2

available_occupied boolean 8
Designation if the service_group is available_occupied
online_name string 9
Online Order Name of service_group that is being created.
sort_order integer 10
Sort order of the service group.
online boolean 11
Boolean indicating if the service group is online.
Possible values
  • true
  • false

active boolean 12
Boolean indicating if the service group is active.
Possible values
  • true
  • false

order_api boolean 13
Boolean indicating if the service group is available in the order_api.
Possible values
  • true
  • false

appointment_needed boolean 14
Possible values
  • true
  • false

production_needed boolean 15
Possible values
  • true
  • false

tour_needed boolean 16
Possible values
  • true
  • false

session_view string 100
View of session object you would like returned.
application_view string 110
View of application object you would like returned.

Request Body Example: application/json

Responses

action-successful 200

This status indicates that the request was successful. If the request returns data, it can be found in the data key.

invalid-token 401

This status is returned when the authentication token passed is invalid.

session-expired 401

This status is returned a session is older than seven days or hasn't been used in 72 hours. The user will need to reauthenticate. We allow our users to save a remember_me preference which will make there sessions last indefinitely.

client-required 401

This status is returned when the user makeing the request doesn't have a client, employee or liaison record. This means that they don't have any roles or permissions. Because we only allow our clients to register as a client, the user should be redirected to the PlanoAuth clients registration page where they can use the `/api/v1/users/client_register` API to register as a client. Eventhough the request will not be successful, this status will still return a `session` object because a session token is needed to register as a user.

missing-param 400

This status is returned when a required param was not passed with the request.

invalid-param 400

This status is returned when a param was invalid when passed. For example, passing an id that doesn't exist or passing an invalid email address.

application-crash 500

This status is returned when there is an internal server error. Please try again later.

mandrill-email-failed 500

This status is returned when there was an issue using Mandrill to send an email. Any time this response is returned, there will be a notification in the production notifications tab so the dev team will be away of the failure. These errors will most likely correlate with a data issue and will need to be invesigated.

invalid-content-type 400

This status is returned if the request was made with the incorrect content-type so the request params could not be read. For more infromation on content-type, please refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type.

route-non-existent 500

Response returned when HTTP route does not exist.

Uncommon Responses

The responses below are not very common.

no-params-decoded Uncommon

This status is returned the request body was decoded, but no params where found.

invalid-encoded-params Uncommon

This status is returned when the request body could not be decoded properly. This generally means that you are requesting a sensative_params API and your request body was not base64 encoded.

route-not-found Uncommon

This status is returned when the route record being requested hasn't been deployed yet.

identify-request-error Uncommon

This status is returned when there is an internal server error before the route could be identified. Please try again later.

service-not-found Uncommon

This status is returned when the route's API service record being requested hasn't been deployed yet.