All Collections
Data Integration
Sending Events from the Server
Sending Events from the Server

You can send events from your server using our low-latency tracking infrastructure, avoiding REST API limitations.

D Clay Smith avatar
Written by D Clay Smith
Updated over a week ago

Note: This is an experimental feature currently under development. While it is considered stable, we are working to improve this integration. We are currently working on language-specific SDKs to make the developer experience more pleasant. If you would like early access to a language-specific SDK (or would like to contribute one!) please email us at

In addition to tracking user behavior via our Javascript SDK, you may want to send user events from your server.

You may send events to the same endpoint we use with our Javascript SDK. This low-latency, highly scalable infrastructure will allow you to avoid the rate limits applied to our REST API and should perform fast enough so to not degrade your applications performance.

Below is a sample call in cURL:

-H 'authorization: Bearer [ Your ApiKey ] \

-H 'content-type: text/json; charset=UTF-8' \

--data-raw '{"person_id":"2","organization_id":"2","timestamp":"2023-03-07T13:01:08.089Z","type":"track","event":"navigation"}'

Please note the following:

  • You must substitute [ Your ApiKey ] for the value available in the Javascript SDK section of Settings in Akita.

  • person_id. This is the unique identifier you use to identify individual users or contacts. It may be the id field in a Users table or an email address.

  • organization_id. This is the unique identifier you use to identify customers or accounts. It may be the id field in a Customers table.

  • timestamp. This should be a ISO-8601 timestamp the event occurred. Will default to the current timestamp.

  • type. This must be left as "track".

  • event. This is your user-defined event name.

Did this answer your question?