Service Operations

Purpose: Groups the operations that your application can create for both services, states, tasks, and interaction resources.

• Maintenance Operations
  • GET /maintenance/services/stream
  • POST /maintenance/services/files
  • POST /maintenance/purge
• Service Operations
  • POST /services/start
  • POST /customers/${customer id}/services/${service id}
  • POST /services/${service id}/end
  • GET /services/${service id}
  • DELETE /services/${service id}
  • GET /services/anonymous/${contact key}/active
  • GET /services/anonymous/${contact key}/completed
  • GET /services/anonymous/${contact key}
  • GET /customers/${customer id}/services/active
  • GET /customers/${customer id}/services/completed
  • GET /customers/${customer id}/services
  • PUT /services/${service id}/extensions/${ext name}
• State Operations
  • POST /services/${service id}/states/${state id}/end
  • POST /services/${service id}/states/transition
  • GET /services/${service id}/states
  • GET /services/${service id}/states/${state id}
  • POST /services/${service id}/states/start
  • PUT /services/${service id}/states/${state id}/extensions/${ext name}
• Task Operations
  • POST /services/${service id}/tasks/${task id}/end
  • GET /services/${service id}/tasks
  • GET /services/${service id}/tasks/${task id}
  • POST /services/${service id}/tasks/start
  • PUT /services/${service id}/tasks/${task id}/extensions/${extension name}

Important

Because extensions are replaced with flexible JSON data on the GMS side, all resources and requests specific to extensions are deprecated for services, states, and tasks.