Get my inspection-ready permit

get

/fscmRestApi/resources/11.13.18.05/publicSectorMyInspectionsPermits/{publicSectorMyInspectionsPermitsUniqID}

Request

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

    For example: publicSectorMyInspectionsPermits?q=LnpRecordKey=<value1>;LnpRecordId=<value2>
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields 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 fields 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 fields. 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 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
  • 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
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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 : publicSectorMyInspectionsPermits-item-response
Type: object
Show Source
  • Title: Applicant
    Read Only: true
    The party ID of the person applying for the application.
  • Read Only: true
    Maximum Length: 100
    The doing business as (DBA) name for the business entity.
  • Read Only: true
    Maximum Length: 3
    The classification of the permit type.
  • Read Only: true
    Maximum Length: 1000
    The description of the applicant record.
  • Read Only: true
    Maximum Length: 320
    The primary contact's email address.
  • Read Only: true
    Maximum Length: 544
    The primary address and city of the primary parcel or address associated with the permit.
  • Read Only: true
    Maximum Length: 15
    The unique alphanumeric code or short name for the inspection group associated with the permit type.
  • Links
  • Read Only: true
    Maximum Length: 50
    The unique identifier of the application record.
  • Read Only: true
    The unique identifier of the record associated with the permit.
  • Read Only: true
    Maximum Length: 450
    The primary contact's name.
  • Read Only: true
    Maximum Length: 10
    The primary contact's phone area code.
  • Read Only: true
    Maximum Length: 10
    The primary contact's phone country code.
  • Read Only: true
    Maximum Length: 20
    The primary contact's phone extension.
  • Read Only: true
    Maximum Length: 40
    The primary contact's phone number.
  • Read Only: true
    Maximum Length: 1
    Indicates whether the record is a primary application that has one or more subapplications. When a permit is created, the default value is N or no.
  • Read Only: true
    The unique identifier of the primary record.
  • Read Only: true
    Maximum Length: 100
    The unique alphanumeric code or short name for the permit type.
  • Read Only: true
    Maximum Length: 20
    The description of the permit type.
  • Read Only: true
    Maximum Length: 15
    The status of the applicant record.
  • Read Only: true
    Maximum Length: 1
    Indicates whether the record is a subapplication or child of a primary application. When a permit is created, the default value is N or no.
  • Read Only: true
    Maximum Length: 10
    The subclassification for the transaction type, which indicates that the preapplication process is included in addition to the hearing process.
  • Read Only: true
    Maximum Length: 15
    The predefined system status to which the record status maps.
  • Read Only: true
    Maximum Length: 1
    The version of the permit. Values are origination, amendment, and renewal.
Back to Top