Section

Section Service

REST endpoints for interacting with Sections and Section Entries. Sections are used to partition a Support Center page (or other solution page) into regions.

Refer to Sections for examples and additional information.

Since: 3.12

Create Section

POST /sections

Create a new section owned by the caller, based on the information in the specified Section. Then, return a 201 with a Section reflecting the new section configuration.

The following fields are processed from the incoming section entity:

  • name - the name of the new section (must be unique per user)
  • solutionKey - the name of the solution with which this section should be associated; specify "supportcenter" for the Support Center
  • displayOrder - the ordinal to display this section within it's solution key group
  • sectionType - the type of the section, one of "header", "block", or "footer"; These types can be used to change the display of the section for a UI
  • sectionEntries - the list of section entries to include in this section
Query Parameters:
NameTypeRequiredDescription
fieldsStringfalseFields to be returned on the newly created entity (defaults to @all)
Takes:
  • Configuration information to construct the new section
    • Retrieves:
  • Section describing the newly created section
    • Return Status:
    HTTP Status CodeDescription
    201 (Created)Request was successful
    400 (Bad Request)One or more input values is malformed
    409 (Conflict)Requesting to create a section with a name that already exists
    403 (Forbidden)Requester is not allowed to manage sections

    Destroy Section

    DELETE /sections/{sectionID}

    Delete an existing section.

    Path Parameters:
    NameTypeRequiredDescription
    sectionIDStringtrueID of the section to be deleted
    Return Status:
    HTTP Status CodeDescription
    204 (No Content)Request was successful
    403 (Forbidden)The requester is not allowed to manage section
    404 (Not Found)The specified section cannot be found
    400 (Bad Request)BadRequestException

    Get Avatar

    GET /sections/{sectionEntryID}/avatar

    Return the binary content of the avatar image for the specified section entry.

    Path Parameters:
    NameTypeRequiredDescription
    sectionEntryIDStringtrueID of the section entry for which to retrieve the avatar image
    Query Parameters:
    NameTypeRequiredDescription
    sizeStringfalseRequested size ("small", "medium", "large"), default is "large"
    Retrieves:
  • The binary content of the avatar image for the specified section entry
    • Return Status:
    HTTP Status CodeDescription
    200 (OK)Request was successful
    400 (Bad Request)An input field is malformed
    403 (Forbidden)You are not allowed to retrieve this image
    404 (Not Found)The specified section entry or image does not exist

    Get Section

    GET /sections/{sectionID}

    Return a Section representation of the specified section.

    Path Parameters:
    NameTypeRequiredDescription
    sectionIDStringtrueID of the section to be returned
    Query Parameters:
    NameTypeRequiredDescription
    fieldsStringfalseFields to be returned (default is "@all")
    Retrieves:
  • Section representation of the specified section
    • Return Status:
    HTTP Status CodeDescription
    200 (OK)Request was successful
    400 (Bad Request)One or more input values is malformed
    403 (Forbidden)The requester is not allowed to view sections for the owning user
    404 (Not Found)The specified section cannot be found

    Get Sections

    GET /sections
    Get a list of sections.
    Query Parameters:
    NameTypeRequiredDescription
    fieldsStringfalseFields to be returned for each section(default value is @summary)
    Retrieves:
  • Section[]
    • Return Status:
    HTTP Status CodeDescription
    200 (OK)Request was successful
    400 (Bad Request)Any of the input fields are malformed
    403 (Forbidden)The requesting user is not authorized to retrieve sections

    Update Section

    PUT /sections/{sectionID}

    Update an existing section, based on the information in the specified Section. Then, return a Section reflecting the updated section configuration.

    The following fields are processed from the incoming Section:

    • name - the name of the new section (must be unique per user)
    • displayOrder - the ordinal to display this section within it's solution key group
    • sectionEntries - the list of section entries to include in this section

    solutionKey and sectionType cannot be modified

    Path Parameters:
    NameTypeRequiredDescription
    sectionIDStringtrueID of the section to be updated
    Query Parameters:
    NameTypeRequiredDescription
    fieldsStringfalseFields to be included in the response (default is @all)
    Takes:
  • Section containing the configuration information to construct the new section
    • Retrieves:
  • A Section reflecting the updated section configuration
    • Return Status:
    HTTP Status CodeDescription
    200 (OK)Request was successful
    400 (Bad Request)An input value is missing or malformed
    409 (Conflict)Requesting to create a section with a name that already exists
    403 (Forbidden)The requester is not allowed to manage sections
    404 (Not Found)The specified user cannot be found