---
title: "Kerko klient sipas NIPT"
operation_id: "api.v1.client.search"
method: GET
path: "/api/v1/client/search"
group: "Klienti"
api_version: "v1"
authenticated: true
canonical: "https://fature.al/api-reference/endpoints/api-v1-client-search.html"
---

# Kerko klient sipas NIPT

Part of the [fature.al API](/api-reference/index.html) documentation.

## GET /api/v1/client/search

Kerkon nje kompani ne **regjistrin fiskal** me NIPT/NUIS dhe kthen te dhenat e saj.

Perdoreni per te mbushur vete formularin e nje klienti te ri: kerkoni nje fushe te vetme nga
perdoruesi dhe merrni emrin, adresen dhe qytetin nga regjistri. Nje NIPT i gabuar kapet ketu,
para se te dale ne nje fature.

Fusha `verified` thote nese kompania u gjet e konfirmuar ne regjister.

Dalloni dy pergjigjet qe duken te ngjashme:

- `404`, NIPT-i nuk ekziston ne regjister;
- `503`, regjistri nuk u arrit, pra NIPT-i mbeti i pakontrolluar. Provoni perseri.

Full URL: `https://fature.al/api/v1/client/search`

API version: `v1`.

Authentication: required (bearer token).

### Query parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `nuis` | string | yes | NIPT/NUIS i kompanise per te kerkuar, ne formatin X00000000X. |

### Example request

```bash
curl -X GET 'https://fature.al/api/v1/client/search?nuis=L91806031A' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'X-Client-Id: YOUR_CLIENT_ID' \
  -H 'X-Client-Secret: YOUR_CLIENT_SECRET' \
  -H 'Accept: application/json'
```

### Responses

**200** — OK

| Field | Type | Description |
| --- | --- | --- |
| `status` | boolean |  |
| `data` | object |  |
| `data.client` | object |  |
| `data.client.nuis` | string |  |
| `data.client.name` | string |  |
| `data.client.address` | string |  |
| `data.client.city` | string |  |
| `data.client.country` | integer |  |
| `data.client.country_code` | string |  |
| `data.client.verified` | boolean |  |

```json
{
    "status": true,
    "data": {
        "client": {
            "nuis": "nuis",
            "name": "Jane Doe",
            "address": "1 Example Street",
            "city": "Berlin",
            "country": 1,
            "country_code": "US",
            "verified": true
        }
    }
}
```

**404** — NIPT-i nuk gjendet ne regjistrin fiskal.

| Field | Type | Description |
| --- | --- | --- |
| `status` | boolean | Always false. A successful response carries `status: true` and a `data` object instead |
| `message` | string | The exception message. Empty when the failure carries no exception of its own |
| `errors` | array | Messages to show the operator or to log. Absent when the failure has nothing to add beyond `message` |

```json
{
    "status": true,
    "message": "Hello there",
    "errors": [
        "errors"
    ]
}
```

**422** — NIPT-i mungon ose nuk eshte ne formatin X00000000X. Kjo pergjigje perdor fushen `success`, jo `status`.

| Field | Type | Description |
| --- | --- | --- |
| `success` | boolean | Always false |
| `message` | string | A single summary line, the same for every validation failure |
| `errors` | object | The failing fields, each with the messages for it. Dotted keys point into nested objects and array items, e.g. `lines.0.quantity` |

```json
{
    "success": true,
    "message": "Hello there",
    "errors": []
}
```

**503** — Regjistri fiskal nuk u arrit, keshtu qe NIPT-i mbeti i pakontrolluar. Provoni perseri.

| Field | Type | Description |
| --- | --- | --- |
| `status` | boolean | Always false. A successful response carries `status: true` and a `data` object instead |
| `message` | string | The exception message. Empty when the failure carries no exception of its own |
| `errors` | array | Messages to show the operator or to log. Absent when the failure has nothing to add beyond `message` |

```json
{
    "status": true,
    "message": "Hello there",
    "errors": [
        "errors"
    ]
}
```