No-code usage based with Hyperline connectors and automatic data pulling
15.188.105.163
, 15.188.215.105
and 35.181.129.14
postgres://username:password@host.com/database
)api_calls
or active_users
for instancetimestamp
will represent the date we use to calculate if a record should be included in an invoice. For instance, if you bill on monthly API calls, we’ll bill all events with a timestamp within the last 30 days. It’s less important if you don’t have periodic meteringcustomerId
is the customer unique identifier ON YOUR SIDE. We’ll use it to associate a record with a subscription.id
is the identifier of the record ON YOUR SIDE. We’ll use it to de-duplicate and update records later, so make sure it really represents the record uniquely.automatically_created
that won’t be displayed by default in your customers list to avoid spam (but you can access them using the pending customers
table).
Optionally, you can also return a customerName
property so we had a name to the customer when creating it, which will make it easier for you to find them later.
To to summarise, the minimum acceptable request looks like this
id
and customerId
and always keep the latest version. We don’t update customer names in Hyperline even if the name has changed, you’ll need to change in the interface.
deletedAt
fields in the query that you set to something when the record is deleted. You’ll then be able to filter these records out in our pricing engine.