| Field | Type | Required | Description | Example |
|---|---|---|---|---|
raw |
Optional<Boolean> | ➖ | Include raw response. Mostly used for debugging purposes | |
consumerId |
Optional<String> | ➖ | ID of the consumer which you want to get or push data from | test-consumer |
appId |
Optional<String> | ➖ | The ID of your Unify application | dSBdXd2H6Mqwfg0atXHXYcysLJE9qyn1VwBtXHX |
serviceId |
Optional<String> | ➖ | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | salesforce |
cursor |
JsonNullable<String> | ➖ | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
limit |
Optional<Long> | ➖ | Number of results to return. Minimum 1, Maximum 200, Default 20 | |
filter |
Optional<SuppliersFilter> | ➖ | Apply filters | { "company_name": "SpaceX", "display_name": "Elon Musk", "first_name": "Elon", "last_name": "Musk", "email": "[email protected]", "updated_since": "2020-09-30T07:43:32.000Z" } |
sort |
Optional<SuppliersSort> | ➖ | Apply sorting | { "by": "updated_at", "direction": "desc" } |
passThrough |
Map<String, Object> | ➖ | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | { "search": "San Francisco" } |
fields |
JsonNullable<String> | ➖ | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: fields=name,email,addresses.cityIn the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
id,updated_at |