# Get Profile's own events - Operation ID: `GetClientOwnEvents` - HTTP method: `GET` - Path: `/v4/events` - [Human-readable API reference](https://hub.synerise.com/api-reference/data-management#tag/Events/operation/GetClientOwnEvents) ## Self-contained OpenAPI method The fenced document below contains this method's documentation and all of its local references. It is self-contained; no category or master specification fetch is required. ```yaml openapi: 3.0.0 info: title: Synerise Public API version: 1.9.1 paths: /v4/events: get: deprecated: true summary: Get Profile's own events description: | **This endpoint is deprecated. Use [/activities-api/events](https://developers.synerise.com/DataManagement/DataManagement.html#operation/getEvents) instead.** A Profile can retrieve a list of its own events saved in the database. --- **API consumer:** Profile (Client) operationId: GetClientOwnEvents parameters: - name: Content-Type in: header required: true style: simple explode: false schema: type: string enum: - application/json - name: Api-Version in: header required: true style: simple explode: false schema: type: string enum: - "4.4" - in: query name: time[from] description: Start of the time range to query. UTC time in ISO 8601 (for example, `2020-10-19T13:47:53Z`). If no value is provided, the results are returned starting with the oldest entry in the database. required: false schema: type: string format: date-time - in: query name: time[to] description: End of the time range to query. UTC time in ISO 8601 (for example, `2020-10-19T13:47:53Z`). If no value is provided, the current time applies. required: false schema: type: string format: date-time - in: query name: action description: Filter events by action type. For example, to retrieve completed transactions, enter `transaction.charge` required: false schema: type: string example: transaction.charge - in: query name: limit description: The number of events to retrieve required: false schema: type: integer minimum: 1 maximum: 500 responses: "200": description: A list of events content: application/json: schema: type: array items: type: object properties: time: type: string description: | Time when the event occurred. This is the time that: - is sent as `recordedAt` to **v4/transactions/** endpoints - is sent as `time` to **v4/events/** endpoints - is the occurrence time of system events If the event had no time provided when sending, the time of saving in the database is used. If the event had a future time when sending, it was rejected and the time of saving in the database is used. This is the value that needs to be used as `time` (`recordedAt` in v4/transactions endpoints) when overwriting events by using eventSalt. action: type: string example: client.updateData description: The system name for the action label: type: string example: Human-readable label minLength: 1 description: This parameter is required, but not saved in the database. It can't be used in Analytics, Automations, and so on. client: type: object description: | You must provide at least one of those profile identifiers. **Upcoming breaking change (effective July 6, 2026):** Synerise is introducing changes to how user identifiers and UUIDs are handled. These changes may affect profiles with accented or diacritical characters in identifiers, profiles with leading or trailing whitespace in identifiers, and profiles with duplicate UUIDs. For details and recommended actions, see [Upcoming changes to identifier and UUID handling](https://hub.synerise.com/docs/settings/configuration/identifier-standardization/). properties: customId: type: string description: | A custom ID for the Profile. It is a unique identifier. The value can't include any characters that match the pattern (ECMA flavor): `/([\uD800-\uDBFF][\uDC00-\uDFFF])|([\r\n\u2028\u2029\u00AD]|[\uFE00-\uFE0F]|[\u0000])/` **Upcoming breaking change (effective July 6, 2026):** Synerise is introducing changes to how user identifiers and UUIDs are handled. These changes may affect profiles with accented or diacritical characters in identifiers, profiles with leading or trailing whitespace in identifiers, and profiles with duplicate UUIDs. For details and recommended actions, see [Upcoming changes to identifier and UUID handling](https://hub.synerise.com/docs/settings/configuration/identifier-standardization/). id: description: | Unique ID. This ID is generated by the system during profile creation. **Upcoming breaking change (effective July 6, 2026):** Synerise is introducing changes to how user identifiers and UUIDs are handled. These changes may affect profiles with accented or diacritical characters in identifiers, profiles with leading or trailing whitespace in identifiers, and profiles with duplicate UUIDs. For details and recommended actions, see [Upcoming changes to identifier and UUID handling](https://hub.synerise.com/docs/settings/configuration/identifier-standardization/). type: integer format: int64 example: 433230297 uuid: type: string description: | UUID of the Profile. It is a unique identifier. The value can't include any characters that match the pattern (ECMA flavor): `/([\uD800-\uDBFF][\uDC00-\uDFFF])|([\r\n\u2028\u2029\u00AD]|[\uFE00-\uFE0F]|[\u0000])/` **Upcoming breaking change (effective July 6, 2026):** Synerise is introducing changes to how user identifiers and UUIDs are handled. These changes may affect profiles with accented or diacritical characters in identifiers, profiles with leading or trailing whitespace in identifiers, and profiles with duplicate UUIDs. For details and recommended actions, see [Upcoming changes to identifier and UUID handling](https://hub.synerise.com/docs/settings/configuration/identifier-standardization/). example: 07243772-008a-42e1-ba37-c3807cebde8f email: type: string description: | The profile's e-mail address. - Must match the pattern (ECMA flavor): `/^(([^<>()[\]\\.,;:\s@\\"]+(\.[^<>()[\]\\.,;:\s@\\"]+)*)|(\\".+\\"))@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\])|(([a-zA-Z\-0-9]+\.)+[a-zA-Z]{2,}))$/` - The value can't include any characters that match the pattern (ECMA flavor): `/([\uD800-\uDBFF][\uDC00-\uDFFF])|([\r\n\u2028\u2029\u00AD]|[\uFE00-\uFE0F]|[\u0000])/` By default, email is a unique identifier. If [non-unique emails](https://hub.synerise.com/docs/settings/configuration/non-unique-emails/) are enabled, this field should not be used. It is no longer an identifier. The configuration of non-unique emails includes creating an email parameter for communication. **Upcoming breaking change (effective July 6, 2026):** Synerise is introducing changes to how user identifiers and UUIDs are handled. These changes may affect profiles with accented or diacritical characters in identifiers, profiles with leading or trailing whitespace in identifiers, and profiles with duplicate UUIDs. For details and recommended actions, see [Upcoming changes to identifier and UUID handling](https://hub.synerise.com/docs/settings/configuration/identifier-standardization/). params: type: object properties: eventCreateTime: type: string description: | Time when the event was received. If the event had no time or a future time, this value is used as the time when the event occurred. This parameter does not exist in system events. When you overwrite an event with eventSalt, this value changes to the time of overwriting. format: date-time example: 2022-11-23T18:39:26.789Z ip: description: IP of the source device. This parameter does not exist in system events. additionalProperties: description: Additional properties depending on event type and custom parameters. description: | Details of the event, depending on event type and the requirements of your own system. This can be almost any type of data. WARNING: - If you want to send the `email` param, it must be exactly the same as the email of the profile which generated the event. - Some params are reserved for system use. If you send them in the `params` object, they are ignored or overwritten with system-assigned values:
Click to expand the list of reserved params modifiedBy
apiKey
eventUUID
ip
time
businessProfileId
"401": description: "Unauthorized: wrong consumer scope; token missing/expired/invalid; invalid API key; etc." content: application/json: schema: type: object properties: error: type: string description: Summary of the error status: type: integer format: int32 description: Status code timestamp: type: string description: Time when the message was sent path: type: string description: URL of the requested resource message: type: string description: Description of the problem errors: type: array description: Additional details of the errors, if applicable items: type: object properties: code: type: integer format: int32 example: 12082 description: A numeric identifier of the error type field: type: string example: countryCode description: Field in the request body that caused the error message: type: string example: Country Code must have 0 or 3 characters as per ISO format. description: A detailed description of the problem rejectedValue: type: string example: Poland description: The value that caused the error example: error: Bad Request status: 400 timestamp: 2020-10-29T13:08:16.235Z path: /exampleEndpoint message: Some fields did not pass validation errors: - code: 120 field: exampleField message: "120" rejectedValue: exampleValue "403": description: Forbidden; insufficient permissions (when PII protection is enabled, PII permissions are required in addition to the permissions listed in the method description) content: application/json: schema: type: object properties: error: type: string description: Summary of the error status: type: integer format: int32 description: Status code timestamp: type: string description: Time when the message was sent path: type: string description: URL of the requested resource message: type: string description: Description of the problem errors: type: array description: Additional details of the errors, if applicable items: type: object properties: code: type: integer format: int32 example: 12082 description: A numeric identifier of the error type field: type: string example: countryCode description: Field in the request body that caused the error message: type: string example: Country Code must have 0 or 3 characters as per ISO format. description: A detailed description of the problem rejectedValue: type: string example: Poland description: The value that caused the error example: timestamp: 2018-06-07T07:29:27.489+00:00 status: 403 error: Forbidden message: Forbidden path: /path_of_the_endpoint "415": description: Unsupported Media Type content: application/json: schema: type: object properties: error: type: string description: Summary of the error status: type: integer format: int32 description: Status code timestamp: type: string description: Time when the message was sent path: type: string description: URL of the requested resource message: type: string description: Description of the problem errors: type: array description: Additional details of the errors, if applicable items: type: object properties: code: type: integer format: int32 example: 12082 description: A numeric identifier of the error type field: type: string example: countryCode description: Field in the request body that caused the error message: type: string example: Country Code must have 0 or 3 characters as per ISO format. description: A detailed description of the problem rejectedValue: type: string example: Poland description: The value that caused the error example: timestamp: 2018-06-07T07:27:23.136+00:00 status: 415 error: Unsupported Media Type message: Content type 'application/xml' not supported path: /path_of_the_endpoint "500": description: Internal Server Error content: application/json: schema: type: object properties: error: type: string description: Summary of the error status: type: integer format: int32 description: Status code timestamp: type: string description: Time when the message was sent path: type: string description: URL of the requested resource message: type: string description: Description of the problem errors: type: array description: Additional details of the errors, if applicable items: type: object properties: code: type: integer format: int32 example: 12082 description: A numeric identifier of the error type field: type: string example: countryCode description: Field in the request body that caused the error message: type: string example: Country Code must have 0 or 3 characters as per ISO format. description: A detailed description of the problem rejectedValue: type: string example: Poland description: The value that caused the error example: timestamp: 2018-06-07T09:50:43.947+00:00 status: 500 error: Internal Server Error message: Duration between time[from] and time[to] cannot be greater than 7 days path: /events/by-client/525446574 security: - JWT: [] tags: - Events x-snr-doc-urls: - /api-reference/data-management#tag/Events/operation/GetClientOwnEvents x-codeSamples: - lang: cURL label: cURL source: |- curl --request GET \ --url 'https://api.synerise.com/v4/events?time%5Bfrom%5D=SOME_STRING_VALUE&time%5Bto%5D=SOME_STRING_VALUE&action=transaction.charge&limit=SOME_INTEGER_VALUE' \ --header 'Api-Version: SOME_STRING_VALUE' \ --header 'Authorization: Bearer REPLACE_BEARER_TOKEN' \ --header 'Content-Type: SOME_STRING_VALUE' - lang: Python label: Python source: |- import http.client conn = http.client.HTTPSConnection("api.synerise.com") headers = { 'Content-Type': "SOME_STRING_VALUE", 'Api-Version': "SOME_STRING_VALUE", 'Authorization': "Bearer REPLACE_BEARER_TOKEN" } conn.request("GET", "/v4/events?time%5Bfrom%5D=SOME_STRING_VALUE&time%5Bto%5D=SOME_STRING_VALUE&action=transaction.charge&limit=SOME_INTEGER_VALUE", headers=headers) res = conn.getresponse() data = res.read() print(data.decode("utf-8")) - lang: JavaScript label: JavaScript source: |- const data = null; const xhr = new XMLHttpRequest(); xhr.withCredentials = true; xhr.addEventListener("readystatechange", function () { if (this.readyState === this.DONE) { console.log(this.responseText); } }); xhr.open("GET", "https://api.synerise.com/v4/events?time%5Bfrom%5D=SOME_STRING_VALUE&time%5Bto%5D=SOME_STRING_VALUE&action=transaction.charge&limit=SOME_INTEGER_VALUE"); xhr.setRequestHeader("Content-Type", "SOME_STRING_VALUE"); xhr.setRequestHeader("Api-Version", "SOME_STRING_VALUE"); xhr.setRequestHeader("Authorization", "Bearer REPLACE_BEARER_TOKEN"); xhr.send(data); - lang: Node.js label: Node.js source: |- const http = require("https"); const options = { "method": "GET", "hostname": "api.synerise.com", "port": null, "path": "/v4/events?time%5Bfrom%5D=SOME_STRING_VALUE&time%5Bto%5D=SOME_STRING_VALUE&action=transaction.charge&limit=SOME_INTEGER_VALUE", "headers": { "Content-Type": "SOME_STRING_VALUE", "Api-Version": "SOME_STRING_VALUE", "Authorization": "Bearer REPLACE_BEARER_TOKEN" } }; const req = http.request(options, function (res) { const chunks = []; res.on("data", function (chunk) { chunks.push(chunk); }); res.on("end", function () { const body = Buffer.concat(chunks); console.log(body.toString()); }); }); req.end(); - lang: PHP label: PHP source: |- setUrl('https://api.synerise.com/v4/events'); $request->setMethod(HTTP_METH_GET); $request->setQueryData([ 'time[from]' => 'SOME_STRING_VALUE', 'time[to]' => 'SOME_STRING_VALUE', 'action' => 'transaction.charge', 'limit' => 'SOME_INTEGER_VALUE' ]); $request->setHeaders([ 'Content-Type' => 'SOME_STRING_VALUE', 'Api-Version' => 'SOME_STRING_VALUE', 'Authorization' => 'Bearer REPLACE_BEARER_TOKEN' ]); try { $response = $request->send(); echo $response->getBody(); } catch (HttpException $ex) { echo $ex; } - lang: Java label: Java source: |- HttpResponse response = Unirest.get("https://api.synerise.com/v4/events?time%5Bfrom%5D=SOME_STRING_VALUE&time%5Bto%5D=SOME_STRING_VALUE&action=transaction.charge&limit=SOME_INTEGER_VALUE") .header("Content-Type", "SOME_STRING_VALUE") .header("Api-Version", "SOME_STRING_VALUE") .header("Authorization", "Bearer REPLACE_BEARER_TOKEN") .asString(); servers: - description: Microsoft Azure EU url: https://api.synerise.com - description: Microsoft Azure USA url: https://api.azu.synerise.com - description: Google Cloud Platform url: https://api.geb.synerise.com tags: - name: Events components: securitySchemes: JWT: type: http scheme: bearer description: |- JWT Bearer token. The header looks like this: `Bearer {JWT}` Remember to include the space between 'Bearer' and the token. Generate a token via the **Authorization** endpoints. ```