BokaMera.API.Host

<back to all web services

UpdateSupportCase

Requires Authentication
Requires any of the roles:bookingsupplier-administrator-write, superadmin
The following routes are available for this service:
PUT/support/cases/{Id}Update a support caseUpdate a support case to the company of the currently logged in user, only administrators are allowed to add support cases.
UpdateSupportCase Parameters:
NameParameterData TypeRequiredDescription
CompanyIdbodyGuid?YesEnter the company id, if blank company id and you are an admin, your company id will be used.
IdpathintNoThe support case id
TitlebodystringYesThe case title.
DescriptionbodystringYesThe case description.
CaseTypeIdbodyint?NoIf the case type id.
CaseAreaIdbodyint?NoIf the case area id.
SupportCaseQueryResponse Parameters:
NameParameterData TypeRequiredDescription
IdformintNoThe support case id
CompanyUserIdformGuidNoThe company user id
TitleformstringYesThe case title.
DescriptionformstringYesThe case description.
CaseStatusIdformintNoThe case status id.
CaseTypeIdformintNoIf the case type id.
CaseAreaIdformintNoIf the case area id.
CreatedByformstringYesThe case created by.
UpdatedByformstringYesThe case updated by.
SolvedByformstringYesThe case solved by.
UpdatedformDateTimeNoIf case updated date.
CreatedformDateTimeNoIf case created date.
CaseOwnerformstringYesWho owns the support case.
CaseStatusformSupportCaseStatusResponseYesThe case status information.
CaseTypeformSupportCaseTypeResponseYesThe case type information.
CaseAreaformSupportCaseAreaResponseYesThe case area information.
CommentsformList<SupportCaseCommentsResponse>YesThe case comments.
AttachmentsformList<SupportCaseAttachmentResponse>YesThe case attachments.
CaseStatusOptionsformList<SupportCaseStatusResponse>YesThe case status options to select from.
CaseTypeOptionsformList<SupportCaseTypeResponse>YesThe case type options to select from.
CaseAreaOptionsformList<SupportCaseAreaResponse>YesThe case area options to select from.
SupportCaseStatusResponse Parameters:
NameParameterData TypeRequiredDescription
IdformintNoThe status id
NameformstringYesThe status name
DescriptionformstringYesThe status description
IconformstringYesThe status icon
ColorformstringYesThe status color
SupportCaseTypeResponse Parameters:
NameParameterData TypeRequiredDescription
IdformintNoThe type id
NameformstringYesThe type name
DescriptionformstringYesThe type description
SupportCaseAreaResponse Parameters:
NameParameterData TypeRequiredDescription
IdformintNoThe area id
NameformstringYesThe area name
DescriptionformstringYesThe area description
SupportCaseCommentsResponse Parameters:
NameParameterData TypeRequiredDescription
SupportCaseIdformintNoThe case id
IdformintNoThe comments id
CommentformstringYesThe case comment
CreatedByformstringYesThe case comment created by
CreatedformDateTimeNoThe case comment created date
SupportCaseAttachmentResponse Parameters:
NameParameterData TypeRequiredDescription
IdformintNoThe attachment id
FileUrlformstringYesThe attachment file url

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

PUT /support/cases/{Id} HTTP/1.1 
Host: api.bokamera.se 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<UpdateSupportCase xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BokaMera.API.ServiceModel.Dtos">
  <CaseAreaId>0</CaseAreaId>
  <CaseTypeId>0</CaseTypeId>
  <CompanyId>00000000-0000-0000-0000-000000000000</CompanyId>
  <Description>String</Description>
  <Id>0</Id>
  <Title>String</Title>
</UpdateSupportCase>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<SupportCaseQueryResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BokaMera.API.ServiceModel.Dtos">
  <Attachments>
    <SupportCaseAttachmentResponse>
      <FileUrl>String</FileUrl>
      <Id>0</Id>
    </SupportCaseAttachmentResponse>
  </Attachments>
  <CaseArea>
    <Description>String</Description>
    <Id>0</Id>
    <Name>String</Name>
  </CaseArea>
  <CaseAreaId>0</CaseAreaId>
  <CaseAreaOptions>
    <SupportCaseAreaResponse>
      <Description>String</Description>
      <Id>0</Id>
      <Name>String</Name>
    </SupportCaseAreaResponse>
  </CaseAreaOptions>
  <CaseOwner>String</CaseOwner>
  <CaseStatus>
    <Color>String</Color>
    <Description>String</Description>
    <Icon>String</Icon>
    <Id>0</Id>
    <Name>String</Name>
  </CaseStatus>
  <CaseStatusId>0</CaseStatusId>
  <CaseStatusOptions>
    <SupportCaseStatusResponse>
      <Color>String</Color>
      <Description>String</Description>
      <Icon>String</Icon>
      <Id>0</Id>
      <Name>String</Name>
    </SupportCaseStatusResponse>
  </CaseStatusOptions>
  <CaseType>
    <Description>String</Description>
    <Id>0</Id>
    <Name>String</Name>
  </CaseType>
  <CaseTypeId>0</CaseTypeId>
  <CaseTypeOptions>
    <SupportCaseTypeResponse>
      <Description>String</Description>
      <Id>0</Id>
      <Name>String</Name>
    </SupportCaseTypeResponse>
  </CaseTypeOptions>
  <Comments>
    <SupportCaseCommentsResponse>
      <Comment>String</Comment>
      <Created>0001-01-01T00:00:00</Created>
      <CreatedBy>String</CreatedBy>
      <Id>0</Id>
      <SupportCaseId>0</SupportCaseId>
    </SupportCaseCommentsResponse>
  </Comments>
  <CompanyUserId>00000000-0000-0000-0000-000000000000</CompanyUserId>
  <Created>0001-01-01T00:00:00</Created>
  <CreatedBy>String</CreatedBy>
  <Description>String</Description>
  <Id>0</Id>
  <SolvedBy>String</SolvedBy>
  <Title>String</Title>
  <Updated>0001-01-01T00:00:00</Updated>
  <UpdatedBy>String</UpdatedBy>
</SupportCaseQueryResponse>