1. REST API for Oracle Public Sector Compliance and Regulation Cloud
  2. Tasks
  3. RecordParcelAddressSearchQueries

Get a permit

get

/fscmRestApi/resources/11.13.18.05/publicSectorRecordParcelAddressSearchQueries/{publicSectorRecordParcelAddressSearchQueriesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- LnpRecordKey, ParcelKey and AddressKey ---for the RecordParcelAddressSearchQueries resource and used to uniquely identify an instance of RecordParcelAddressSearchQueries. The client should not generate the hash key value. Instead, the client should query on the RecordParcelAddressSearchQueries collection resource with a filter on the primary key values in order to navigate to a specific instance of RecordParcelAddressSearchQueries.

    For example: publicSectorRecordParcelAddressSearchQueries?q=LnpRecordKey=<value1>;ParcelKey=<value2>;AddressKey=<value3>
Query Parameters
  • This parameter specifies dependencies which are attributes that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The attributes specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the attributes will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency attributes. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • 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 attributes. Only the specified attributes are returned, which means that if no attributes are specified, no attributes 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 attributes. 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
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Body ()
Root Schema : publicSectorRecordParcelAddressSearchQueries-item
Type: object
Show Source
Back to Top