Skip to main content
Version: 0.20

HTTP API

This page document the HTTP APIs. These APIs are used by websites, servers or mobiles application to produce events.

You may want to take a look at the tracking script to add analytics to your website instead of directly interacting with the HTTP API.

Events API​

Request to events API are rate limited by IP address (max 60 events per minute) and standard 429 Too Many Requests responses are returned if limit is exceeded.

Page view events​

You can create page view events using the following operation: POST /api/v1/events/pageviews.

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • X-Prisme-Referrer or Referer (with single r typo) header MUST contains URL of viewed page.
  • X-Prisme-Document-Referrer header MUST contains client referrer, URL from which viewer comes from, if present.
  • User-Agent header MUST contains client User-Agent. This is used to determine browser and device.
  • X-Forwarded-For or value of PRISME_PROXY_HEADER option header (if PRISME_TRUST_PROXY is true) to determine client IP address. This is used to determine clients location. Typically, reverse proxies (such as Envoy used by Prisme Cloud) adds this header.
  • X-Prisme-Visitor-Id header MUST contains a unique visitor id, if present.

NOTE: Do not use personal information such as an email address as visitor ID.

Server return 400 Bad Request if URLs from headers are invalid or origin is not registered.

Custom events​

Since v0.14.0, Prisme supports custom events. You can create custom events using the following operation: POST /api/v1/events/custom/:name (:name corresponding to the name of your event such as clicks, sign_ups, etc)

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • X-Prisme-Referrer or Referer (with single r typo) header MUST contains URL of page that triggered the event.
  • Content-Type MUST be application/json
  • Request body MUST contains a valid, preferably flat for better query performance, JSON object. This is where you should put you're custom data.

File downloads​

Since v0.18.0, Prisme supports tracking file downloads. You can create file download events using the following operation: POST /api/v1/events/file-downloads

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • X-Prisme-Referrer or Referer (with single r typo) header MUST contains URL of page that triggered the event.
  • Body MUST contains absolute URL of downloaded file.

ping anchor attribute​

Prisme also supports ping anchor attribute that sends a POST request when defined:

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • Ping-From header MUST contains URL from which ping originated. This is automatically added by browsers.
  • Ping-To header MUST contains URL of downloaded file. This is automatically added by browsers.
  • Body MUST be PING. This is automatically added by browsers.

Since v0.18.0, Prisme supports tracking outbound link clicks. You can create file download events using the following operation: POST /api/v1/events/outbound-links

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • X-Prisme-Referrer or Referer (with single r typo) header MUST contains URL of page that triggered the event.
  • Body MUST contains absolute URL of downloaded file.

ping anchor attribute​

Prisme also supports ping anchor attribute that sends a POST request when defined:

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • Ping-From header MUST contains URL from which ping originated. This is automatically added by browsers.
  • Ping-To header MUST contains URL of downloaded file. This is automatically added by browsers.
  • Body MUST be PING. This is automatically added by browsers.

Noscript events API​

Since v0.16.0, Prisme support JavaScript less tracking with /api/v1/noscript/events/* endpoints.

Most noscript endpoints (unless specified otherwise) returns a small (35 bytes), transparent, single pixel GIF image.

This way you can send events using HTML:

<!-- Set position to absolute to not disrupt document layout flow -->
<img src="https://<prisme-instance-hostname>/api/v1/noscript/events/<event>" style="position:absolute;top:-100px;">

file-downloads events doesn't have a noscript endpoint as cross origin downloads are prohibited. Nevertheless, Prisme supports ping anchor attribute so you can send events as follow:

<a href="/movie.mp4" download="true" ping="https://<prisme-instance-hostname>/api/v1/events/file-downloads">
    Download movie
</a>

outbound-links events endpoint has support for both: ping attribute and GET /api/v1/noscript/events/outbound-links endpoint.

Page view events​

You can create page view events using the following operation: GET /api/v1/noscript/events/pageviews.

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • referrer search parameter or Referer (with single r typo) header MUST contains URL of viewed page.
  • document-referrer search parameter MUST contains client referrer, URL from which viewer comes from, if present.
  • User-Agent header MUST contains client User-Agent. This is used to determine browser and device.
  • X-Forwarded-For or value of PRISME_PROXY_HEADER option header (if PRISME_TRUST_PROXY is true) to determine client IP address. This is used to determine clients location. Typically, reverse proxies (such as Envoy used by Prisme Cloud) adds this header.
  • visitor-id search parameter header MUST contains a unique visitor id, if present.

NOTE: Do not use personal information such as an email address as visitor ID.

Server return 400 Bad Request if URLs from headers are invalid or origin is not registered.

Custom events​

You can send custom events using the following operation: GET /api/v1/noscript/events/custom/:name (:name corresponding to the name of your event such as click, sign_up, etc)

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • referrer search parameter or Referer (with single r typo) header MUST contains URL of page that triggered the event.
  • prop-<property-name> search parameters MUST contains valid JSON values (e.g. string property name must be encoded as prop-name="John" with double quotes).

You can send custom events using the following operation: GET /api/v1/noscript/events/outbound-links

  • Origin header MUST contain origin of request. This is automatically added by browsers.
  • referrer search parameter or Referer (with single r typo) header MUST contains URL of page that triggered the event.
  • url search parameters MUST contains absolute outbound URL clicked. User will be redirected to that URL.

This endpoint won't respond a GIF images but instead redirect user to the specified URL.

Health check​

You can check that your instance is running, ready and healthy with the following operation: GET /api/v1/healthcheck.