Get all items from the cart record

get

/fscmRestApi/resources/11.13.18.05/publicSectorRecordCarts

Request

Query Parameters
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format: ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables:

    • PrimaryKey: Finds an application that matches the primary key specified.
      Finder Variables:
      • LnpRecordKey; integer; The unique identifier for an application such as a permit application or planning application.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • Address1; string; The first line of the applicant address.
    • Address2; string; The second line of the applicant address.
    • Address3; string; The third line of the applicant address.
    • Address4; string; The fourth line of the applicant address.
    • Amount; number; The total fees from the source record.
    • Applicant; integer; The user who submitted the application.
    • City; string; The city of the applicant address.
    • Country; string; The applicant country.
    • County; string; The country of the applicant address.
    • EmailAddress1; string; The applicant first email address.
    • EmailAddress2; string; The applicant second email address.
    • LnpRecordId; string; The unique identifier for an application record. This identifier is automatically generated based on the rules configured for the record type.
    • LnpRecordKey; integer; The unique identifier for the record key, such as the key for a permit.
    • PersonFirstName; string; The applicant first name.
    • PersonLastName; string; The applicant last name.
    • PersonMiddleName; string; The applicant middle name.
    • PersonName; string; The applicant full name.
    • PhoneNumber; string; The applicant phone number.
    • PostalCode; string; The postal code of the applicant address.
    • PostalPlus4Code; string; The postal plus code of the applicant address.
    • ProjectKey; integer; The project key associated with this record.
    • Province; string; The province of the applicant address.
    • RecordType; string; The record type, such as a permit, business license, professional license, or planning and zoning record.
    • RecordTypeId; string; The unique identifier for the record type associated with this item.
    • State; string; The state of the applicant address.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorRecordCarts
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : publicSectorRecordCarts-item-response
Type: object
Show Source
  • Title: Address Line 1
    Read Only: true
    Maximum Length: 240
    The first line of the applicant address.
  • Title: Address Line 2
    Read Only: true
    Maximum Length: 240
    The second line of the applicant address.
  • Title: Address Line 3
    Read Only: true
    Maximum Length: 240
    The third line of the applicant address.
  • Title: Address Line 4
    Read Only: true
    Maximum Length: 240
    The fourth line of the applicant address.
  • Title: Amount
    Read Only: true
    The total fees from the source record.
  • Title: Applicant
    Read Only: true
    The user who submitted the application.
  • Title: City
    Read Only: true
    Maximum Length: 60
    The city of the applicant address.
  • Title: Country
    Read Only: true
    Maximum Length: 3
    The applicant country.
  • Title: County
    Read Only: true
    Maximum Length: 60
    The country of the applicant address.
  • Title: Email 1
    Read Only: true
    Maximum Length: 320
    The applicant first email address.
  • Title: Email 2
    Read Only: true
    Maximum Length: 320
    The applicant second email address.
  • Links
  • Title: Application
    Read Only: true
    Maximum Length: 50
    The unique identifier for an application record. This identifier is automatically generated based on the rules configured for the record type.
  • Title: Record
    Read Only: true
    The unique identifier for the record key, such as the key for a permit.
  • Title: First Name
    Read Only: true
    Maximum Length: 150
    The applicant first name.
  • Title: Last Name
    Read Only: true
    Maximum Length: 150
    The applicant last name.
  • Title: Middle Name
    Read Only: true
    Maximum Length: 60
    The applicant middle name.
  • Title: Name
    Read Only: true
    Maximum Length: 450
    The applicant full name.
  • Title: Phone
    Read Only: true
    Maximum Length: 60
    The applicant phone number.
  • Title: Postal Code
    Read Only: true
    Maximum Length: 60
    The postal code of the applicant address.
  • Title: Postal Plus 4 Code
    Read Only: true
    Maximum Length: 10
    The postal plus code of the applicant address.
  • Title: Project
    Read Only: true
    The project key associated with this record.
  • Title: Province
    Read Only: true
    Maximum Length: 60
    The province of the applicant address.
  • Title: Application Type
    Read Only: true
    Maximum Length: 100
    The record type, such as a permit, business license, professional license, or planning and zoning record.
  • Read Only: true
    Maximum Length: 30
    The unique identifier for the record type associated with this item.
  • Title: State
    Read Only: true
    Maximum Length: 60
    The state of the applicant address.
Back to Top