List of Operations
Purpose: Entry point of the API Reference. |
Contents of the API Reference
As explained in the Migration page, all the service resources are now part of GMS and all the information related to contact information stays in UCS. As a result, the CS API is divided between UCS and GMS.
Operations
Services API Reference
This icon identifies all the queries related to data managed on the GMS side. |
- Maintenance Operations
- 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}/by/unique
- PUT /services/${service id}/extensions/${ext name}/delete/by/unique
- State Operations
- Task Operations
- Service Resources
Important
Because the extensions are now handled as JSON data, all the queries related to service, state, and task extensions are now deprecated.
Customer Profile API Reference
This icon identifies all the queries related to data managed on the UCS side. These queries cover interactions, identification and profile management. |
- Profile Operations
- Schema and Identification Key Operations
- Interaction Operations
This page was last edited on December 2, 2014, at 10:23.
Comments or questions about this documentation? Contact us for support!