@@ -246,47 +246,47 @@ def ingest(
246
246
Events are the starting point for all usage calculations in the system, and are
247
247
simple at their core:
248
248
249
- ```json
249
+ ```ts
250
250
{
251
- // customer_id and external_customer_id are used to
252
- // attribute usage to a given Customer. Exactly one of these
253
- // should be specified in a given ingestion event.
254
-
255
- // `customer_id` is the Orb generated identifier for the Customer,
256
- // which is returned from the Create customer API call.
257
- customer_id: string,
258
-
259
- // external_customer_id is an alternate identifier which is associated
260
- // with a Customer at creation time. This is treated as an alias for
261
- // customer_id, and is usually set to an identifier native to your system.
262
- external_customer_id: string,
263
-
264
- // A string name identifying the event, usually a usage
265
- // action. By convention, this should not contain any whitespace.
266
- event_name: string,
267
-
268
- // An ISO 8601 format date with no timezone offset.
269
- // This should represent the time that usage occurred
270
- // and is important to attribute usage to a given
271
- // billing period. See the notes below on determining the timestamp.
272
- // e.g. 2020-12-09T16:09:53Z
273
- timestamp: string,
274
-
275
- // A unique value, generated by the client, that is
276
- // used to de-duplicate events.
277
- // Exactly one event with a given
278
- // idempotency key will be ingested, which allows for
279
- // safe request retries.
280
- idempotency_key: string
281
-
282
- // Optional custom metadata to attach to the event.
283
- // This might include a numeric value used for aggregation,
284
- // or a string/boolean value used for filtering.
285
- // The schema of this dictionary need not be pre-declared, and
286
- // properties can be added at any time.
287
- properties: {
288
- [key: string]?: string | number | boolean,
289
- },
251
+ // customer_id and external_customer_id are used to
252
+ // attribute usage to a given Customer. Exactly one of these
253
+ // should be specified in a given ingestion event.
254
+
255
+ // `customer_id` is the Orb generated identifier for the Customer,
256
+ // which is returned from the Create customer API call.
257
+ customer_id: string,
258
+
259
+ // external_customer_id is an alternate identifier which is associated
260
+ // with a Customer at creation time. This is treated as an alias for
261
+ // customer_id, and is usually set to an identifier native to your system.
262
+ external_customer_id: string,
263
+
264
+ // A string name identifying the event, usually a usage
265
+ // action. By convention, this should not contain any whitespace.
266
+ event_name: string,
267
+
268
+ // An ISO 8601 format date with no timezone offset.
269
+ // This should represent the time that usage occurred
270
+ // and is important to attribute usage to a given
271
+ // billing period. See the notes below on determining the timestamp.
272
+ // e.g. 2020-12-09T16:09:53Z
273
+ timestamp: string,
274
+
275
+ // A unique value, generated by the client, that is
276
+ // used to de-duplicate events.
277
+ // Exactly one event with a given
278
+ // idempotency key will be ingested, which allows for
279
+ // safe request retries.
280
+ idempotency_key: string
281
+
282
+ // Optional custom metadata to attach to the event.
283
+ // This might include a numeric value used for aggregation,
284
+ // or a string/boolean value used for filtering.
285
+ // The schema of this dictionary need not be pre-declared, and
286
+ // properties can be added at any time.
287
+ properties: {
288
+ [key: string]?: string | number | boolean,
289
+ },
290
290
}
291
291
```
292
292
@@ -785,47 +785,47 @@ async def ingest(
785
785
Events are the starting point for all usage calculations in the system, and are
786
786
simple at their core:
787
787
788
- ```json
788
+ ```ts
789
789
{
790
- // customer_id and external_customer_id are used to
791
- // attribute usage to a given Customer. Exactly one of these
792
- // should be specified in a given ingestion event.
793
-
794
- // `customer_id` is the Orb generated identifier for the Customer,
795
- // which is returned from the Create customer API call.
796
- customer_id: string,
797
-
798
- // external_customer_id is an alternate identifier which is associated
799
- // with a Customer at creation time. This is treated as an alias for
800
- // customer_id, and is usually set to an identifier native to your system.
801
- external_customer_id: string,
802
-
803
- // A string name identifying the event, usually a usage
804
- // action. By convention, this should not contain any whitespace.
805
- event_name: string,
806
-
807
- // An ISO 8601 format date with no timezone offset.
808
- // This should represent the time that usage occurred
809
- // and is important to attribute usage to a given
810
- // billing period. See the notes below on determining the timestamp.
811
- // e.g. 2020-12-09T16:09:53Z
812
- timestamp: string,
813
-
814
- // A unique value, generated by the client, that is
815
- // used to de-duplicate events.
816
- // Exactly one event with a given
817
- // idempotency key will be ingested, which allows for
818
- // safe request retries.
819
- idempotency_key: string
820
-
821
- // Optional custom metadata to attach to the event.
822
- // This might include a numeric value used for aggregation,
823
- // or a string/boolean value used for filtering.
824
- // The schema of this dictionary need not be pre-declared, and
825
- // properties can be added at any time.
826
- properties: {
827
- [key: string]?: string | number | boolean,
828
- },
790
+ // customer_id and external_customer_id are used to
791
+ // attribute usage to a given Customer. Exactly one of these
792
+ // should be specified in a given ingestion event.
793
+
794
+ // `customer_id` is the Orb generated identifier for the Customer,
795
+ // which is returned from the Create customer API call.
796
+ customer_id: string,
797
+
798
+ // external_customer_id is an alternate identifier which is associated
799
+ // with a Customer at creation time. This is treated as an alias for
800
+ // customer_id, and is usually set to an identifier native to your system.
801
+ external_customer_id: string,
802
+
803
+ // A string name identifying the event, usually a usage
804
+ // action. By convention, this should not contain any whitespace.
805
+ event_name: string,
806
+
807
+ // An ISO 8601 format date with no timezone offset.
808
+ // This should represent the time that usage occurred
809
+ // and is important to attribute usage to a given
810
+ // billing period. See the notes below on determining the timestamp.
811
+ // e.g. 2020-12-09T16:09:53Z
812
+ timestamp: string,
813
+
814
+ // A unique value, generated by the client, that is
815
+ // used to de-duplicate events.
816
+ // Exactly one event with a given
817
+ // idempotency key will be ingested, which allows for
818
+ // safe request retries.
819
+ idempotency_key: string
820
+
821
+ // Optional custom metadata to attach to the event.
822
+ // This might include a numeric value used for aggregation,
823
+ // or a string/boolean value used for filtering.
824
+ // The schema of this dictionary need not be pre-declared, and
825
+ // properties can be added at any time.
826
+ properties: {
827
+ [key: string]?: string | number | boolean,
828
+ },
829
829
}
830
830
```
831
831
0 commit comments