> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tranthor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tranthor's REST API

> Send data directly to Tranthor's API.

You can send events straight to Tranthor’s Segment-compatible HTTP API. This is handy when you’d prefer to skip an external connector such as our [Segment source](/integrations/sources/segment).

## Endpoints

Tranthor’s REST interface uses the same schema as [Segment’s HTTP API](https://segment.com/docs/connections/sources/catalog/libraries/server/http-api/).

* [`/api/public/apps/identify`](/api-reference/endpoints/apps/identify)
* [`/api/public/apps/track`](/api-reference/endpoints/apps/track)
* [`/api/public/apps/page`](/api-reference/endpoints/apps/page)
* [`/api/public/apps/screen`](/api-reference/endpoints/apps/screen)

## Authentication

Tranthor’s REST API authenticates using Write Keys. Find yours in the dashboard at [`/dashboard/settings#write-key-title`](https://app.tranthor.com/dashboard/settings#write-key-title).

Include write keys as an HTTP `Authorization: Basic ...` header in your requests. It's safe to include this write key in your
client (e.g. your web client javascript payload).

For example, you can use the following to submit an identify request to our demo workspace:

```bash theme={null}
curl -H 'Content-Type:application/json' \
     -H 'Authorization: Basic trn_abcdef...' \
     -X POST \
     -d '{
         "userId": "'$(uuidgen)'",
         "messageId": "'$(uuidgen)'",
         "traits": {
             "email": "email@example.com"
         }
     }' \
    https://app.tranthor.com/api/public/apps/identify
```

## SDK's

Prefer using a client library? Tranthor offers platform-specific [SDKs](/integrations/sdks) for added convenience.

<Snippet file="available-sdks.mdx" />