GET
/
v1
/
reporting
/
{data_table_key}
/
records
curl --request GET \
  --url https://api.qobra.co/v1/reporting/{data_table_key}/records \
  --header 'X-API-Key: <api-key>'
{
  "count": 457,
  "data": [
    {
      "id": "6545110915808dbcc34531ee",
      "date": "2023-11-30",
      "plan": "Great plan",
      "user": {
        "id": "5537a5b05d6e4824940e9e1bb9a5ebb8",
        "email": "john-doe@company.com",
        "name": "John Doe",
        "role": "Sales Rep",
        "currency": "EUR",
        "country": "France",
        "code": "AO32ND56",
        "...": "..."
      },
      "record": {
        "id": "6545110915808eecc34531ee",
        "name": "Great opportunity"
      },
      "commission": 3500,
      "commission_currency": "EUR"
    },
    "..."
  ],
  "next": "https://api.qobra.co/v1/reporting/opportunity/records?limit=200&offset=200"
}

​
Pagination

This endpoint is paginated using parameters offset and limit The “next” key in the response allow you to easily follow pagination to get the next batch of users

​
Variable api keys

This endpoint is based on dynamic fields. This mean that all annotations that look like <variable-key>, will have to or will be replaced by their actual API keys.

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
data_table_key
string
required

Used to identify the data table

Query Parameters

​
offset
integer
default:0

Optional (minimum:0 - maximum:9223372036854775807)

Required range: 0 <= x <= 9223372036854776000
​
limit
integer
default:200

Optional (minimum:0 - maximum:200): if set to 0 return total count only

Required range: 0 <= x <= 200

Response

200 - application/json
Success operation
​
count
integer
required

Number of records in the response

​
data
object[]
required
​
next
string

Next page of the response

Was this page helpful?

Raise issue