Api >

Service Portal REST API

PUT updates existing Frontdesk Target
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/18 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": [{
    "name": "context",
    "value": "some another random context for skill service for update"
  }]
}
Then I should receive HTTP/1.1 204 No Content
Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/42
Then I should receive HTTP/1.1 200 OK
with following body:
{
  "href": "/api/customers/K0002/targets/frontdesk-services/17/target/42",
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": [{
    "name": "context",
    "value": "some another random context for skill service for update"
  }]
}
PUT cannot update Frontdesk Target with a targetService of another customer
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002
And there is a skill service belonging to K0003 is created with name other skill name and service number 95.
A Frontdesk Target is created with context my random context for skill service. When I send /api/customers/K0002/targets/frontdesk-services/17/target/95 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0003/targets/skill-services/95"
  }],
  "data": [{
    "name": "context",
    "value": "some another random context for skill service for update"
  }]
}
Then I should receive HTTP/1.1 403 Forbidden With following body
{
  "detail": "Access denied to [Customer] with id [K0003]",
  "title": "Access forbidden",
  "described_by": "http://api.nfon.net/probs/invalid-authorization"
}
PUT updates existing Frontdesk Target with no data
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/18 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }]
}
Then I should receive HTTP/1.1 204 No Content
PUT updates existing Frontdesk Target with no context in data
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/18 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": []
}
Then I should receive HTTP/1.1 204 No Content
PUT updates existing Frontdesk Target with empty context
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/18 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": [{
    "name": "context",
    "value": ""
  }]
}
Then I should receive HTTP/1.1 400 Bad Request with following body:
{
  "detail": "Could not create or update resource due to constraint violations",
  "title": "Validation error",
  "errors": [{
    "message": "Context must not be empty",
    "path": "context",
    "value": null
  }],
  "described_by": "http://api.nfon.net/probs/validation-error"
}
PUT updates existing Frontdesk Target with exceeding context
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/18 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": [{
    "name": "context",
    "value": "Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo. Nullam dictum felis eu pede mollis pretium. Integer tincidunt. Cras dapibus. Vivamus elementum semper nisi. Aenean vulputate eleifend tellus. Aenean leo ligula, porttitor eu, consequat vitae, eleifend ac, enim. Aliquam lorem ante, dapibus in, viverra quis, feugiat a, tellus. Phasellus viverra nulla ut metus varius laoreet. Quisque rutrum. Aenean imperdiet. Etiam ultricies nisi vel augue. Curabitur ullamcorper ultricies nisi. Nam eget dui. Etiam rhoncus. Maecenas tempus, tellus eget condimentum rhoncus, sem quam semper libero, sit amet adipiscing sem neque sed ipsum. Nam quam nunc, blandit vel, luctus pulvinar, hendrerit id, lorem. Maecenas nec odio et ante tincidunt tempus. Donec vitae sapien ut libero venenatis faucibus. Nullam quis ante. Etiam sit amet orci eget eros faucibus tincidunt. Duis leo. Sed fringilla mauris sit amet nibh. Donec sodales sagittis magna. Sed consequat, leo eget bibendum sodales, augue velit cursus nunc, quis gravida magna mi a libero. Fusce vulputate eleifend sapien. Vestibulum purus quam, scelerisque ut, mollis sed, nonummy id, metus. Nullam accumsan lorem in dui. Cras ultricies mi eu turpis hendrerit fringilla. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; In ac dui quis mi consectetuer lacinia. Nam pretium turpis et arcu. Duis arcu tortor, suscipit eget, imperdiet nec, imperdiet iaculis, ipsum. Sed aliquam ultrices mauris. Integer ante arcu, accumsan a, consectetuer eget, posuere ut, mauris. Praesent adipiscing. Phasellus ullamcorper ipsum rutrum nunc. Nunc nonummy metus. Vestibs"
  }]
}
Then I should receive HTTP/1.1 400 Bad Request with following body:
{
  "detail": "Could not create or update resource due to constraint violations",
  "title": "Validation error",
  "errors": [{
    "message": "Context must not exceed 2000 characters.",
    "path": "context",
    "value": 2001
  }],
  "described_by": "http://api.nfon.net/probs/validation-error"
}
PUT returns error for non-existing Frontdesk Target update
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/17/target/2 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": [{
    "name": "context",
    "value": "some another random context for skill service for update"
  }]
}
Then I should receive HTTP/1.1 404 Not Found
with following body:
{
  "detail": "Frontdesk Target with Service Number 2 not found",
  "title": "Frontdesk Target not found",
  "described_by": "http://api.nfon.net/probs/frontdesk-target-not-found"
}
PUT returns error for non-existing Frontdesk Service update
Test setup
A skill service is created with name skill name and service number 18.

Another skill service is created with name skill name 2 and service number 42, intended to be assigned to an existing target.

A Frontdesk Service is created with service number 17.

A Frontdesk Target is created with context my random context for skill service.

Given I am authenticated as customer K0002

When I send /api/customers/K0002/targets/frontdesk-services/33/target/2 as application/json; charset=UTF-8 with following body:
{
  "links": [{
    "rel": "targetService",
    "href": "/api/customers/K0002/targets/skill-services/42"
  }],
  "data": [{
    "name": "context",
    "value": "some another random context for skill service for update"
  }]
}
Then I should receive HTTP/1.1 404 Not Found
with following body:
{
  "detail": "Frontdesk Service with service number 33 not found",
  "title": "Frontdesk Service not found",
  "described_by": "http://api.nfon.net/probs/frontdesk-service-not-found"
}