Ping back URL - Revision history

Admin at 14:20, 24 June 2026

2026-06-24T14:20:02Z

← Older revision		Revision as of 14:20, 24 June 2026
Line 39:		Line 39:

	<!--T:17-->		<!--T:17-->
	~~<syntaxhighlight lang="bash">~~
	curl -v -X POST -k 'https://example.com/ping-back' \		curl -v -X POST -k 'https://example.com/ping-back' \
	-H 'content-type: application/json' \		-H 'content-type: application/json' \
	--data-raw '{"kmnrId":"50d9ecc6-402b-4a74-9397-fc20f2980567","kmnrKey":111111111,"fraud":1,"block":0,"reason":"Spoofing","sub1":"sub1 value","sub2":"sub2 value","sub3":"sub3 value","sub4":"","sub5":"","sub6":"","sub7":""}'		--data-raw '{"kmnrId":"50d9ecc6-402b-4a74-9397-fc20f2980567","kmnrKey":111111111,"fraud":1,"block":0,"reason":"Spoofing","sub1":"sub1 value","sub2":"sub2 value","sub3":"sub3 value","sub4":"","sub5":"","sub6":"","sub7":""}'
	~~</syntaxhighlight>~~

	<!--T:18-->		<!--T:18-->

Admin: Marked this version for translation

2026-06-24T14:15:49Z

Marked this version for translation

← Older revision		Revision as of 14:15, 24 June 2026
Line 33:		Line 33:
	Acceptable characters: [A-Za-z0-9_] Latin letters, Arabic numerals, underscore. Maximum length is 200 characters.		Acceptable characters: [A-Za-z0-9_] Latin letters, Arabic numerals, underscore. Maximum length is 200 characters.

	<!--T:4-->		== Testing your endpoint == <!--T:4-->
	~~== Testing your endpoint ==~~

			<!--T:16-->
	You can verify that your ping-back endpoint is working with the following curl command:		You can verify that your ping-back endpoint is working with the following curl command:

			<!--T:17-->
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	curl -v -X POST -k 'https://example.com/ping-back' \		curl -v -X POST -k 'https://example.com/ping-back' \
Line 44:		Line 45:
	</syntaxhighlight>		</syntaxhighlight>

			<!--T:18-->
	Replace:		Replace:

			<!--T:19-->
	* <code>https://example.com/ping-back</code> — your ping-back URL		* <code>https://example.com/ping-back</code> — your ping-back URL
	* <code>111111111</code> — your kmnrKey		* <code>111111111</code> — your kmnrKey
	* <code>50d9ecc6-402b-4a74-9397-fc20f2980567</code> — any random kmnrId		* <code>50d9ecc6-402b-4a74-9397-fc20f2980567</code> — any random kmnrId

			<!--T:20-->
	The request should return HTTP 200.		The request should return HTTP 200.

			<!--T:21-->
	= Response format =		= Response format =
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.

Admin: /* Option activation */

2026-06-24T14:11:14Z

Option activation

@@ Line 34: / Line 34: @@
 <!--T:4-->
 = Response format =
 After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.

Admin at 09:30, 5 May 2026

2026-05-05T09:30:18Z

← Older revision		Revision as of 09:30, 5 May 2026
Line 62:		Line 62:
	\| kmnrKey \|\| Integration identifier		\| kmnrKey \|\| Integration identifier
	\|-		\|-
	\| fraud \|\| 1 if the hit is fraudulent, 0 if the hit is non-fraudulent, ~~-1 if the hit could not be verified~~		\| fraud \|\| 1 if the hit is fraudulent, 0 if the hit is non-fraudulent,
	\|-		\|-
	\| block \|\| 1 if the hit was blocked according to the integration settings, 0 if the hit wasn't blocked		\| block \|\| 1 if the hit was blocked according to the integration settings, 0 if the hit wasn't blocked

Admin at 09:05, 21 November 2025

2025-11-21T09:05:14Z

← Older revision		Revision as of 09:05, 21 November 2025
Line 82:		Line 82:

	<!--T:15-->		<!--T:15-->
	If the ping-back still cannot be delivered, you can always retrieve the status for any click via our API, which serves as the reliable source of truth regardless of delivery success.		If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If the ping-back still cannot be delivered, you can always retrieve the status for any click via our API, which serves as the reliable source of truth regardless of delivery success.

	<!--T:6-->		<!--T:6-->

Admin: t15 Убрал упоминание логов заменив API

2025-11-19T11:24:12Z

t15 Убрал упоминание логов заменив API

← Older revision		Revision as of 11:24, 19 November 2025
Line 82:		Line 82:

	<!--T:15-->		<!--T:15-->
	If ~~you receive a~~ ping-back, ~~your server should respond with a~~ status ~~200. Otherwise~~, ~~we make three more attempts to send~~ the ~~request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request~~.		If the ping-back still cannot be delivered, you can always retrieve the status for any click via our API, which serves as the reliable source of truth regardless of delivery success.

	<!--T:6-->		<!--T:6-->

Admin: Marked this version for translation

2024-01-26T12:23:30Z

Marked this version for translation

← Older revision		Revision as of 12:23, 26 January 2024
Line 18:		Line 18:
	To understand which impression we've checked, you need to mark it.		To understand which impression we've checked, you need to mark it.

			<!--T:14-->
	If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.		If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.

Line 80:		Line 81:
	\|}		\|}

			<!--T:15-->
	If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request.		If you receive a ping-back, your server should respond with a status 200. Otherwise, we make three more attempts to send the request. If it was not possible to send a ping-back, we save it in an internal log and can provide it to you upon request.

Admin at 12:22, 26 January 2024

2024-01-26T12:22:59Z

← Older revision		Revision as of 12:22, 26 January 2024
Line 36:		Line 36:
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.
	<pre>{		<pre>{
	"kmnrId":"50d9ecc6-402b-4a74-9397-fc20f2980567",		"kmnrId": "50d9ecc6-402b-4a74-9397-fc20f2980567",
	"kmnrKey":111111111,		"kmnrKey": 111111111,
	"fraud":1,		"fraud": 1,
	"block":1,		"block": 1,
	"sub1":"sub1 value",		"sub1": "sub1 value",
	"sub2":"sub2 value",		"sub2": "sub2 value",
	"sub3":"sub3 value",		"sub3": "sub3 value",
	"sub4":444,		"sub4": 444,
	"sub5":555,		"sub5": 555,
	"sub6":"~~foo-bar~~",		"sub6": "",
	"sub7":"~~true~~"		"sub7": ""
	}</pre>		}</pre>

Admin at 12:21, 26 January 2024

2024-01-26T12:21:43Z

← Older revision		Revision as of 12:21, 26 January 2024
Line 16:		Line 16:
	<!--T:8-->		<!--T:8-->
	== kmnrId ==		== kmnrId ==
	To understand which impression we've checked, you need to mark it. If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.		To understand which impression we've checked, you need to mark it.

			If you have an '''JS check'''-type integration, add the <code>kmnrId</code> key to <code>window.kmnr</code> with any unique identifier convenient for you. By this identifier you can later recognize the impression.

	<!--T:9-->		<!--T:9-->
Line 32:		Line 34:
	<!--T:4-->		<!--T:4-->
	= Response format =		= Response format =
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format. <~~code~~>{ kmnrId: '50d9ecc6-402b-4a74-9397-fc20f2980567', kmnrKey: 111111111, fraud: 1, block: 1, sub1: 'sub1 value', sub2: 'sub2 value', sub3: 'sub3 value', sub4: 444, sub5: 555, sub6: 'foo-bar', sub7: 'true' }</~~code~~>		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format.
			<pre>{
			"kmnrId":"50d9ecc6-402b-4a74-9397-fc20f2980567",
			"kmnrKey":111111111,
			"fraud":1,
			"block":1,
			"sub1":"sub1 value",
			"sub2":"sub2 value",
			"sub3":"sub3 value",
			"sub4":444,
			"sub5":555,
			"sub6":"foo-bar",
			"sub7":"true"
			}</pre>

	<!--T:13-->		<!--T:13-->

Admin at 12:19, 26 January 2024

2024-01-26T12:19:43Z

← Older revision		Revision as of 12:19, 26 January 2024
Line 32:		Line 32:
	<!--T:4-->		<!--T:4-->
	= Response format =		= Response format =
	After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format. <code>{ kmnrId: 111111111, fraud: 1, block: 1 }</code>		After receiving, processing the data, and making a decision about the bot status of the click, we send the decision to you in JSON POST format. <code>{ kmnrId: '50d9ecc6-402b-4a74-9397-fc20f2980567', kmnrKey: 111111111, fraud: 1, block: 1, sub1: 'sub1 value', sub2: 'sub2 value', sub3: 'sub3 value', sub4: 444, sub5: 555, sub6: 'foo-bar', sub7: 'true' }</code>

	<!--T:13-->		<!--T:13-->