---
title: "Check if data exists for the supplied properties"
method: GET
path: "/rest/devinfo/0.10/existsByProperties"
tags: ["Development Information"]
---

# Check if data exists for the supplied properties

`GET /rest/devinfo/0.10/existsByProperties`

Checks if repositories which have all the provided properties exists. For example, if request is `GET existsByProperties?accountId=123&projectId=ABC` then result will be positive only if there is at least one repository with both properties `accountId=123` and `projectId=ABC`. Special property `_updateSequenceId` can be used to filter all entities with updateSequenceId less or equal than the value specified. In addition to the optional `_updateSequenceId`, one or more query params must be supplied to specify properties to search by.

## Query parameters

- `_updateSequenceId` integer

## Headers

- `Authorization` string, required

## Response `200`

Returns whether data exists for the specified properties.

- object — Whether there is data for the properties supplied in a query
  - `hasDataMatchingProperties` boolean — Whether there is data matching the query

## Other responses

- `400` — Request has incorrect format. It will fail in the following cases: If no query properties are specified. If `_updateSequenceId` is not a numeric value. If multiple values of the same property key are specified.
- `401` — Missing a JWT token, or token is invalid.
- `403` — The JWT token used does not correspond to an app that defines the jiraDevelopmentTool module, or the app does not define the 'READ' scope
- `429` — API rate limit has been exceeded.
- `500` — An unknown error has occurred.
- `503` — Service is unavailable due to maintenance or other reasons.

---

[API](https://skmtc.net/atlassian/apis/jira-software-cloud-api.md) · [All operations](https://skmtc.net/atlassian/apis/jira-software-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/atlassian/jira-software-cloud-api/revisions/4e108d54b990/schema)