PUT
/
v2
/
browse
/
property
/
{flxId}
/
_issue
curl --request PUT \
  --url https://api.f6o.co/v2/browse/property/{flxId}/_issue \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "comments": [
    "<string>"
  ],
  "hits": 123,
  "raisedAt": "2023-11-07T05:31:56Z",
  "type": [
    "ISSUE_TYPE_UNKNOWN"
  ],
  "userId": [
    "<string>"
  ]
}'
{
  "status": {
    "code": 123,
    "details": [
      {
        "@type": "<string>"
      }
    ],
    "message": "<string>"
  }
}

Authorizations

x-api-key
string
headerrequired

API Key used to be authentified to these APIs. Please contact Fluximmo to get one

Path Parameters

flxId
string
required

Body

application/json
comments
string[]
hits
integer
raisedAt
string
type
enum<string>[]
Available options:
ISSUE_TYPE_UNKNOWN,
ISSUE_TYPE_PRICE,
ISSUE_TYPE_OFFLINE,
ISSUE_TYPE_LOCATION,
ISSUE_TYPE_WRONG_LINK,
ISSUE_TYPE_WRONG_MERGE,
ISSUE_TYPE_OTHER
userId
string[]

Response

200 - application/json
status
object

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

Was this page helpful?