> ## Documentation Index
> Fetch the complete documentation index at: https://help.airbridge.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Attribution Result

Get attributed results by Device UUID.

The Attribution Result API can receive `AIRBRIDGE-API-KEY` and `AIRBRIDGE-SDK-TOKEN` as authorization headers. When using `AIRBRIDGE-API-KEY`, use the API Token, and when using `AIRBRIDGE-SDK-TOKEN`, use the `SDK Token`.

An example of the call is shown below.

```zsh lines theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
curl -H "Authorization: AIRBRIDGE-API-KEY {API-TOKEN}" https://api.airbridge.io
```

Get attribution results for mobile devices using `device_uuid`

<Card title="Try API Request" icon="rectangle-api" horizontal href="https://www.postman.com/airbridge-engineering/workspace/airbridge-api/request/22395869-f0035cf5-05ca-4d43-86f5-e2730371ab93" />

```text GET theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
https://api.airbridge.io/attribution-result/v1/apps/{app_name}/mobile-app
```

<h2 id="get-attribution-result-request">
  Request
</h2>

***

<h3 id="get-attribution-result-headers">
  Headers
</h3>

<ParamField header="Accept-Language" type="string">
  You can specify the language to use for API requests and responses. It follows the ISO-639-1 format.
</ParamField>

<ParamField header="Content-Type" type="string">
  Represents the media type of the resource. Defaults to `application/json`.
</ParamField>

<ParamField header="Authorization" type="string">
  The key value to use for API requests. Instructions for getting API keys are in "[how to generate API Keys](/en/references/introduction#authorization)".
</ParamField>

<h3 id="get-attribution-result-path-params">
  Path Params
</h3>

<ParamField path="app_name" type="string" required>
  Airbridge App Name. (Unique ID)
</ParamField>

<h3 id="get-attribution-result-query-params">
  Query Params
</h3>

<ParamField query="device_uuid" type="string" required>
  Device UUID from Android or iOS.
  This is the device UUID obtained through the app SDK. Please refer to the guides below to learn how to get it for each OS.

  * [Android SDK Device UUID Fetching Guide](https://developers.airbridge.io/docs/data-fetching-guide-for-android-sdk#airbridge-device-id)
  * [iOS SDK Device UUID Fetching Guide](https://developers.airbridge.io/docs/data-fetching-guide-for-ios-sdk#airbridge-device-id)
</ParamField>

<RequestExample>
  ```shellscript Request theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
  curl -X GET 'https://api.airbridge.io/attribution-result/v1/apps/{app_name}/mobile-app?device_uuid=f3fab994-baea-4b52-b190-5f023b6ae638' \
    -H 'Accept-Language: ko' \
    -H 'Content-Type: application/json' \
    -H 'Authorization: Bearer {AIRBRIDGE-API-TOKEN}'
  ```
</RequestExample>

<h2 id="get-attribution-result-response">
  Response
</h2>

***

### 200

### 204

If no attribution result is found, the API returns a 204 No Content response. This indicates that the request was valid, but no matching attribution data exists.

### 400

### 401

<ResponseExample>
  ```json 200 theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
  {
    "at": "2023-01-01T09:30:00.123Z",
    "data": {
      "attributedTerm": null,
      "attributedAdGroup": "TEST_ADGROUP",
      "attributedChannel": "website",
      "attributedContent": null,
      "attributedCampaign": "TEST_CAMPAIGN",
      "attributedAdCreative": "TEST_ADCREATIVE",
      "attributedSubPublisher": null,
      "attributedSubSubPublisher1": null,
      "attributedSubSubPublisher2": null,
      "attributedSubSubPublisher3": null
    }
  }
  ```

  ```json 204 theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
  {}
  ```

  ```json 400 theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
  {
    "result": "Invalid device_uuid"
  }
  ```

  ```json 401 theme={"theme":{"light":"github-dark-dimmed","dark":"github-dark-dimmed"}}
  {
    "result": "invalid authorization header"
  }
  ```
</ResponseExample>