Skip to main content
POST
/
v2
/
events
Ingest billable event
curl --request POST \
  --url https://ingest.hyperline.co/v2/events \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "customer_id": "cus_CrqwefTRWBWRT",
  "event_type": "api_call",
  "timestamp": "2024-12-20T16:04:11Z",
  "record": {
    "id": "D32NAA8",
    "durationInMs": 32,
    "isVerified": true
  }
}
'

Documentation Index

Fetch the complete documentation index at: https://docs.hyperline.co/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

​
with_price_calculation
boolean | null

Whether to calculate prices for the event

Example:

true

Body

application/json

Event payload

​
customer_id
string
required

Hyperline ID or external ID of the existing customer.

Example:

"cus_CrqwefTRWBWRT"

​
event_type
string
required

Type corresponding to the event. When creating a dynamic product, this type will be used to map the related events to specific prices.

Minimum string length: 1
Example:

"api_call"

​
timestamp
string<date-time>
required

UTC date time string in the ISO 8601 format, or milliseconds since the epoch. The event timestamp is used to retrieve the events related to a specific billing period.

Example:

"2024-12-20T16:04:11Z"

​
record
object
required

Payload of the event containing an ID and any additional metadata.

Example:
{
  "id": "D32NAA8",
  "durationInMs": 32,
  "isVerified": true
}

Response

202

Event ingested